Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.
Business Processes describe the Activities that are carried out by an organization to deliver a product or service. They are typically represented as a series of sequential steps and are decomposed into hierarchies that often start at the highest level with the value chain and go down to the level just above the task level. When used with Enterprise Architecture it is important to keep these diagrams simple and descriptive. They are a useful view of how an organization goes about achieving its desired business goals and objectives. They are typically represented as a series of diagrams organized in a hierarchy reflecting the way the business sees its operation.
These provide an alternative view of what the business does and can be compared to both Business Functions and Business Capabilities, both of which are represented by hierarchies of elements. The Business Functions typically deliver business value and are organized by required skill and organizational structure. Capabilities are more abstract and focus on what abilities are required and as a result they tend to be less volatile. One of the issues with Businesses Process modeling is that by the time the task is complete the processes are likely to have changed. Even though it is more common to pin architectural effort to a well developed capability model, the Businesses Process Model still has its purpose and helps the architect understand how the business value is achieved and the flow of activities that creates it.
Enterprise Architect has a wide range of tools that can be used to create these models of the business activities. The three main languages that can be used to model the Business Processes are:
- ArchiMate Business Layer - Business Process
- Unified Modeling Language - Activity Diagram
- Business Process model and Notation - Business Process Diagram
The Activity that is the behavioral unit in each of the notations can be organized into a hierarchy using the Project Browser, which provides a way of rolling up from low level activities and a method to decompose a higher level activity into more granular Activities. This provides a usual mechanism for viewing the hierarchy and also acts as a paradigm for communication with the appropriate stakeholders - executives will typically be interested in the Value Chain or highest level Activities, line of business managers with the next level down, and operation managers will be interested in the lower level diagrams.
An alternative way of visualizing the hierarchy of activities that make up a business process is to create a Business Process Hierarchy diagram that shows the hierarchy in a structural diagram. This provides a compelling view but care must be taken as this diagram must be updated manually if the structure of the hierarchy is changed.