1.3.6 Architecture Summary

A set of architecture views that represent the scope of architecture development. Views are contained within the relevant Architecture development target sections 2.x.x and referenced or copied here. Views to be created are tailored by the EA assigned to the project and approved by the Core EA.
Value
Provides architecture requirements for the PLAN phase of architecture development. Provides a checklist of views to be used by the Core EA when reviewing architecture at Check-in step.
Entry Criteria
Architecture scope analysis
mandatory section
Yes
risk type
Cost
Time
Quality
Security
Risk owner
Architecture
Dependent Section

Location Catalogue

Mandatory
Yes
Security related?
Yes
The Location catalogue provides a listing of all locations where an enterprise carries out business operations or houses architecturally relevant assets, such as data centers or end-user computing equipment. Maintaining a definitive list of locations allows change initiatives to quickly define a location scope and to test for completeness when assessing current landscapes or proposed target solutions.

Functional Decomposition Diagram

Mandatory
Yes
Security related?
No
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.
example view

Conceptual Data Diagram

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)

Business Service/Function Catalog

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.

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 Use-Case Diagram

Mandatory
No
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.