Plan

The purpose of the Process Flow diagram is to depict all models and mappings related to the process metamodel entity.

Process Flow diagrams show sequential flow of control between activities and may utilize swim-lane techniques to represent ownership and realization of process steps. For example, the application that supports a process step may be shown as a swim-lane.

The Process/Event/Control/Product catalog provides a hierarchy of processes, events that trigger processes, outputs from processes, and controls applied to the execution of processes.

The purpose of the Organization/Actor catalog is to capture a definitive listing of all participants that interact with IT, including users and owners of IT systems. The Organization/Actor catalog can be referenced when developing requirements in order to test for completeness. For example, requirements for an application that services customers can be tested for completeness by verifying exactly which customer types need to be supported and whether there are any particular requirements or restrictions for user types. The Organization/Actor catalog contains the following metamodel

The purpose of this matrix is to depict the relationship interactions between organizations and business functions across the enterprise. Understanding business interaction of an enterprise is important as it helps to highlight value chain and dependencies across organizations. The Business Interaction matrix shows the following metamodel entities and relationships: Organization Business Function Business Service Business Service communicates with Business Service relationships Business Service is dependent on Business Service relationships

This catalog identifies and maintains a list of the data used across the enterprise, relating data entities to data components showing how data entities are structured. Its purpose is to: Identify all data used in the enterprise Encourage effective data use The Data Entity/Data Component catalog contains the following metamodel entities: Data Entity Logical Data Component Physical Data Component

The purpose of the Business Event diagram is to depict the relationship between events and process. Certain events — such as arrival of certain information (e.g., customer submits sales order) or a certain point in time (e.g., end of fiscal quarter) — cause work and certain actions need to be undertaken within the business. These are often referred to as "business events" or simply "events" and are considered as triggers for a process. It is important to note that the event has to trigger a process and generate a business response or result.

This diagram shows the possible state transitions of a business product, from its creation or receipt to its sale, disposal, or destruction. The product may be a product of any kind (physical, software, or service).