Requirements
(Physical) Architecture Requirements analysis/capture
Mandatory
Yes
Security related?
No
Update of Architecture requirements at end of Physical architecture development to support creation of solution implementation work packages.
(Logical) Architecture Requirements analysis/capture
Mandatory
Yes
Security related?
No
Update of Architecture requirements at end of Logical architecture development
(Conceptual) Architecture Requirements analysis/capture
Mandatory
Yes
Security related?
No
Analysis / capture requirements from conceptual phase of architecture development
Solution Options Report
Mandatory
No
The purpose of this section is to define the gap between the current (as-is) and target (to-be) state business architectures.
Mandatory/optional: This section is optional as not all the domain teams need to produce a business architecture for their respective domains.
Architecture Development Agreement
Security related?
No
Non-Functional Requirements
Mandatory
Yes
Security related?
Yes
Catalogue of non-functional (quality) requirements to be considered.
NFRs
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