2.3.1 Business Architecture Models

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Catalogue

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Actor/Role Matrix

admin — Tue, 02 May 2023 01:34:23 +0000

Actor/Role Matrix admin Tue, 05/02/2023 - 01:34

Mandatory

Yes

Security related?

Yes

The purpose of this matrix is to show which actors perform which roles, supporting definition of security and skills requirements. Understanding Actor-to-Role relationships is a key supporting tool in definition of training needs, user security settings, and organizational change management. The Actor/Role matrix shows the following metamodel entities and relationships: Actor Role Actor performs Role relationships

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Matrix

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Process Flow Diagram

admin — Tue, 02 May 2023 01:34:23 +0000

Process Flow Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Business Process View

Mandatory

Security related?

Yes

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.

In addition to showing a sequence of activity, process flows can also be used to detail the controls that apply to a process, the events that trigger or result from completion of a process, and also the products that are generated from process execution.

Process Flow diagrams are useful in elaborating the architecture with subject specialists, as they allow the specialist to describe "how the job is done" for a particular function. Through this process, each process step can become a more fine-grained function and can then in turn be elaborated as a process.

Deliverable Section

Examples

Business Process View

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Diagram

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Process/Event/Control/Product Catalog

admin — Tue, 02 May 2023 01:34:23 +0000

Process/Event/Control/Product Catalog admin Tue, 05/02/2023 - 01:34

Archimate

n/a

Mandatory

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. This catalog provides a supplement to any Process Flow diagrams that are created and allows an enterprise to filter, report, and query across organizations and processes to identify scope, commonality, or impact. For example, the Process/Event/Control/Product catalog allows an enterprise to see relationships of processes to sub-processes in order to identify the full chain of impacts resulting from changing a high-level process. The Process/Event/Control/Product catalog contains the following metamodel entities: Process Event Control Product

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Physical

Artefact type

Catalogue

TOGAF Phase

Project Phase

Physical Architecture (Master Solution Architecture)

Related workpackage

Organization/Actor Catalog

admin — Tue, 02 May 2023 01:34:23 +0000

Organization/Actor Catalog admin Tue, 05/02/2023 - 01:34

Archimate

n/a

Mandatory

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 entities: Organization Unit Actor Location (may be included in this catalog if an independent Location catalog is not maintained)

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Physical

Artefact type

Catalogue

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Business Interaction Matrix

admin — Tue, 02 May 2023 01:34:23 +0000

Business Interaction Matrix admin Tue, 05/02/2023 - 01:34

Archimate

n/a

Mandatory

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

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Matrix

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Business Event Diagram

admin — Tue, 02 May 2023 01:34:23 +0000

Business Event Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Business Process Cooperation View

Mandatory

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.

Deliverable Section

Business Process Cooperation View

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Diagram

TOGAF Phase

Project Phase

Logical Architecture (Master Solution Architecture)

Related workpackage

Product Lifecycle Diagram

admin — Tue, 02 May 2023 01:34:23 +0000

Product Lifecycle Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Product Lifecycle Viewpoint

Mandatory

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).

Deliverable Section

Product Lifecycle Viewpoint

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Diagram

TOGAF Phase

Project Phase