While processes and activities are often defined together, the primary purpose of processes is to specify how activities are to be carried out if and when activities have to be executed separately.
Given the focus on execution, definitions of processes should be aligned with the classification of events and time, namely the nature of flows and coupling:
- No flows (computation).
- Information flows between activities.
- Actual flows between activities, asynchronous coupling.
- Actual flows, synchronous coupling.
That taxonomy could be used to define execution units in line with activities and the states of objects and expectations.
FURTHER READING
- Iterative Processes
- Value Chains & EA
- Squaring Software To Value Chains
- Agile Architectures: Versatility Meet Plasticity
- Feasibility & Capabilities
- Requirements and Architecture Capabilities
- From Processes to Services
- Models Transformation & Agile Development
- EA: Work Units & Workflows