Conceptual

WHAT to Implement Transform the context into concepts, such as products and services and how they relate to one another and the Operations. Note: When every set of connected concepts are connected together, an overall vision for the enterprise emerges.

Principles Catalog

Mandatory
No
Security related?
Yes
The Principles catalog captures principles of the Business and Architecture Principles that describe what a "good" solution or architecture should look like. Principles are used to evaluate and agree an outcome for architecture decision points. Principles are also used as a tool to assist in architectural governance of change initiatives. The Principles catalog contains the following metamodel entities: Principle

Technology Portfolio Catalog

Mandatory
Yes
The purpose of this catalog is to identify and maintain a list of all the technology in use across the enterprise, including hardware, infrastructure software, and application software. An agreed technology portfolio supports the lifecycle management of technology products and versions and also forms the basis for the definition of technology standards. The Technology Portfolio catalog provides a foundation on which to base the remaining matrices and diagrams.

Organization Decomposition Diagram

Mandatory
No
An Organization Decomposition diagram describes the links between actor, roles, and location within an organization tree. An organization map should provide a chain of command of owners and decision-makers in the organization. Although it is not the intent of the Organization Decomposition diagram to link goal to organization, it should be possible to intuitively link the goals to the stakeholders from the Organization Decomposition diagram.

Business Footprint Diagram

Mandatory
No
A Business Footprint diagram describes the links between business goals, organizational units, business functions, and services, and maps these functions to the technical components delivering the required capability. A Business Footprint diagram provides a clear traceability between a technical component and the business goal that it satisfies, while also demonstrating ownership of the services identified. A Business Footprint diagram demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (C
example view

Value Stream Map

Mandatory
No
A diagram representing an end-to-end collection of value-adding activities that create an overall result for a customer, stakeholder, or end user. The value stream map includes the following metamodel entities: Business Capability Value Stream
example view

Driver/Goal/Objective Catalog

Mandatory
No
The purpose of the Driver/Goal/Objective catalog is to provide a cross-organizational reference of how an organization meets its drivers in practical terms through goals, objectives, and (optionally) measures. Publishing a definitive breakdown of drivers, goals, and objectives allows change initiatives within the enterprise to identify synergies across the organization (e.g., multiple organizations attempting to achieve similar objectives), which in turn allow stakeholders to be identified and related change initiatives to be aligned or consolidated. The Driver/Goal/Objective catalog c

Value Stream Stages Catalog

Mandatory
No
A listing of end-to-end collections of the different stages for the value-adding activities that create an overall result for customer, stakeholder, or end user. The Value Stream Stages catalog includes the following metamodel entities: Business Capability Value Stream