1.3.4 Constraints

Defines the business and technical constraints that are part of a set of non-functional requirements to be considered when developing the architecture.
Value
Architecture development is informed by an agreed and/mandated set of business and technical constraints. eg WCAG compliance. Essential 8 Security compliance
Entry Criteria
NFR analysis
mandatory section
Yes
Concern
Business Continuity
Change Cost
Change Impact
Control
Dependability
Efficiency
Scalability
Security
Specification
risk type
Cost
Time
Quality
Security
Stakeholder
Business Requirements Owners
Senior Leaders
Implementers
Program/Portfolio Managers
Risk Owners
Risk owner
Architecture
Dependent Section
2. Architecture Definition

Application Portfolio Catalog

Mandatory
Yes
Security related?
No
The purpose of this catalog is to identify and maintain a list of all the applications in the enterprise. This list helps to define the horizontal scope of change initiatives that may impact particular kinds of applications. An agreed Application Portfolio allows a standard set of applications to be defined and governed. The Application Portfolio catalog provides a foundation on which to base the remaining matrices and diagrams.

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.
Subscribe to 1.3.4 Constraints