1.3.6 Architecture Summary

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Catalogue

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

Functional Decomposition Diagram

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

Functional Decomposition Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Business Function Viewpoint

Mandatory

Yes

Security related?

The purpose of the Functional Decomposition diagram is to show on a single page the capabilities of an organization that are relevant to the consideration of an architecture. By examining the capabilities of an organization from a functional perspective, it is possible to quickly develop models of what the organization does without being dragged into extended debate on how the organization does it. Once a basic Functional Decomposition diagram has been developed, it becomes possible to layer heat maps on top of this diagram to show scope and decisions. For example, the capabilities to be implemented in different phases of a change program.

Deliverable Section

Business Function Viewpoint

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

example view

Example Functional Decomposition Diagram

Role Catalog

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

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

Archimate

n/a

Mandatory

Yes

Security related?

Yes

The purpose of the Role catalog is to provide a listing of all authorization levels or zones within an enterprise. Frequently, application security or behavior is defined against locally understood concepts of authorization that create complex and unexpected consequences when combined on the user desktop. If roles are defined, understood, and aligned across organizations and applications, this allows for a more seamless user experience and generally more secure applications, as administrators do not need to resort to workarounds in order to enable users to carry out their jobs In addition to supporting security definition for the enterprise, the Role catalog also forms a key input to identifying organizational change management impacts, defining job functions, and executing end-user training. As each role implies access to a number of business functions, if any of these business functions are impacted then change management will be required, organizational responsibilities may need to be redefined, and retraining may be needed. The Role catalog contains the following metamodel entities: Role

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Catalogue

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

Conceptual Data Diagram

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

Conceptual Data Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Information Structure View

Mandatory

Yes

Security related?

Yes

The key purpose of the Conceptual Data diagram/Information Structure View is to depict the relationships between critical data entities within the enterprise. This diagram is developed to address the concerns of business stakeholders. Refer to DoE Conceptual Information Asset Model (16/489129) and develop project specific view. This view also needs to be included as part of the Information Security Assessment (ISA)

Deliverable Section

Information Structure View

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Phase C - Information Architecture

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

Business Service/Information Diagram

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

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

Archimate

Business Process View

Mandatory

Yes

Security related?

Yes

The Business Service/Information diagram shows the information needed to support one or more business services. The Business Service/Information diagram shows what data is consumed by or produced by a business service and may also show the source of information. The Business Service/Information diagram shows an initial representation of the information present within the architecture and therefore forms a basis for elaboration and refinement within Phase C (Data Architecture). TOGAF ref

Deliverable Section

Examples

Business Process View

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

example view

Example Business process view

Business Service/Function Catalog

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

Business Service/Function Catalog admin Tue, 05/02/2023 - 01:34

Mandatory

Yes

Security related?

Yes

The purpose of the Business Service/Function catalog is to provide a functional decomposition in a form that can be filtered, reported on, and queried, as a supplement to graphical Functional Decomposition diagrams. The Business Service/Function catalog can be used to identify capabilities of an organization and to understand the level that governance is applied to the functions of an organization. This functional decomposition can be used to identify new capabilities required to support business change or may be used to determine the scope of change initiatives, applications, or technology components. The Business Service/Function catalog contains the following metamodel entities: Organization Unit Business Function Business Service Application Service (may optionally be included here)

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

Catalogue

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

Data Entity/Business Function Matrix

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

Data Entity/Business Function Matrix admin Tue, 05/02/2023 - 01:34

Archimate

n/a

Mandatory

Security related?

Yes

The purpose of the Data Entity/Business Function matrix is to depict the relationship between data entities and business functions within the enterprise. Business functions are supported by business services with explicitly defined boundaries and will be supported and realized by business processes. The mapping of the Data Entity-Business Function relationship enables the following to take place: Assign ownership of data entities to organizations Understand the data and information exchange requirements business services Support the gap analysis and determine whether any data entities are missing and need to be created Define application of origin, application of record, and application of reference for data entities Enable development of data governance programs across the enterprise (establish data steward, develop data standards pertinent to the business function, etc.) The Data Entity/Business Function matrix shows the following entities and relationships: Data Entity Business Function Data Entity relationship to owning Organization Unit

Deliverable Section

Effort small

Effort medium

Effort large

Architecture Phase

Phase C - Information Architecture

Artefact type

Matrix

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

Organization Decomposition Diagram

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

Organization Decomposition Diagram admin Tue, 05/02/2023 - 01:34

Archimate

Organisation Viewpoint

Mandatory

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.

Deliverable Section

Examples

Organisation Viewpoint

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase

Conceptual Architecture (Master Solution Architecture)

Related workpackage

Business Use-Case Diagram

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

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

Archimate

Business Process Cooperation View

Mandatory

A Business Use-Case diagram displays the relationships between consumers and providers of business services. Business services are consumed by actors or other business services and the Business Use-Case diagram provides added richness in describing business capability by illustrating how and when that capability is used. The purpose of the Business Use-Case diagram is to help to describe and validate the interaction between actors and their roles to processes and functions. As the architecture progresses, the use-case can evolve from the business level to include data, application, and technology details. Architectural business use-cases can also be re-used in systems design work.

Deliverable Section

Business Process Cooperation View

Examples

Effort small

Effort medium

Effort large

Architecture Phase

Artefact type

TOGAF Phase

Project Phase