|
1. Architecture Vision |
|
|
|
No Content - Container heading only. Section 1 - Architecture Vision is produced during project… |
|
|
|
|
1.1 Problem Description |
|
|
|
No Content - Container heading only. This section describes the business challenges and… |
|
|
|
No |
1.1.1 Stakeholders and their Concerns |
Stakeholder Analysis |
|
Project Manager |
Lists the identified stakeholders and identifies the concerns to be addressed in this document |
- Provides a summary of the stakeholders whose concerns are to be addressed by the architecture.
|
Cost, Time, Quality |
Accessibility || Availability and Resiliency || Development Resource || Evolution || Internationalization || Location || Performance and Scalability || Security || Usability |
No |
1.1.2 Problem Analysis |
Problem analysis workshop |
|
Project Manager |
Describes the issues/scenarios to be addressed by the Architecture development work |
- Represents the agreed understanding of the problem to be addressed by the architecture
|
Cost, Time, Quality |
Accessibility || Availability and Resiliency || Development Resource || Evolution || Internationalization || Location || Performance and Scalability || Security || Usability |
|
1.2 Business Vision |
|
|
|
No Content - Container heading only. |
|
|
|
No |
1.2.1 Business Vision Statement |
Benefits analysis workshop |
|
Project Manager |
Describes the business motivations that have initiated the architecture development. |
- Provides a formally documented view of the business motivation and outcomes that inform architecture decisions and options.
|
Cost, Time, Quality |
Development Resource |
No |
1.2.2 Business Vision Diagram |
|
|
Project Manager |
A graphical representation of the business motivations that have initiated the architecture… |
- A visual alternative of the business motivation and outcomes that inform architecture decisions and options to support time poor stakeholders with understanding and reasoning about the motivation for change.
|
Cost, Time, Quality |
|
No |
1.2.3 Change Drivers and Opportunities |
Relevant strategies and agency priorities |
|
Architecture |
Analysis that shows how the initiative is mapped to drivers articulated in strategy. I.e the… |
- places the work in broader strategic context to support architecture decision making.
|
Quality |
Evolution |
No |
1.2.4 Detailed Objectives (Desired Outcomes) |
Outcomes workshop |
|
Project Manager |
Provides a summary of the business objectives that the architecture must meet or address |
- Defines outcomes and measures that can be used to define architecture development
|
Cost, Time, Quality |
Accessibility || Availability and Resiliency || Development Resource || Evolution || Internationalization || Location || Performance and Scalability || Security || Usability |
|
1.3 Resulting Architecture Model |
|
|
|
No Content - Container heading only
This section contains information regarding the scope of… |
|
|
|
Yes |
1.3.1 Architecture Scope |
Understanding of the business problem and expected benefits. Understanding of strategic alignment |
|
Project Manager |
A statement of the in-scope (and out of scope) architecture items |
- Provides a statement of the in-scope architecture components for stakeholder agreement. Constrains PLAN phase architecture development
|
Cost, Time, Quality, Security |
|
Yes |
1.3.2 Solution Concept Diagram |
|
|
Architecture |
A diagram showing the scope of architecture change. |
- Communicates architecture scope of change to stakeholders in a visual way
|
Quality |
|
No |
1.3.3 Architecture Principles |
Agreed principles |
|
Architecture |
Identifies the architecture / business principles that inform the architecture development. |
- Allows enterprise requirements to be considered in the development of the architecture to ensure strategic alignment beyond the focus of the project mandate.
- Allows decision makers to enforce or exempt project from alignment with principles.
|
Quality |
Accessibility || Availability and Resiliency || Evolution || Location || Security || Usability |
Yes |
1.3.4 Constraints |
NFR analysis |
|
Architecture |
Defines the business and technical constraints that are part of a set of non-functional… |
- Architecture development is informed by an agreed and/mandated set of business and technical constraints. eg WCAG compliance. Essential 8 Security compliance
|
Cost, Time, Quality, Security |
|
Yes |
1.3.5 Policies and Standards |
Relevant policies and standards analysis |
|
Architecture |
List of policies and standards that inform and constrain the architecture development |
- Identifies the policies and standards requirements that must be taken into consideration during architecture development.
- Ensures legal and regulatory compliance is included when defining the architecture.
|
Quality, Security |
|
Yes |
1.3.6 Architecture Summary |
Architecture scope analysis |
|
Architecture |
A set of architecture views that represent the scope of architecture development. Views are… |
- 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.
|
Cost, Time, Quality, Security |
|
No |
1.3.7 Requirements Mapped to Target Architecture |
Requirements, Architecture scope |
|
Project Manager |
Provides a record of the architectural response to identified high level requirements. Updated… |
- Provides a quality check to assess completeness of architecture development
- Provides traceability between requirements and architecture to be developed.
|
Cost, Time, Quality |
Accessibility || Availability and Resiliency || Evolution || Internationalization || Location || Performance and Scalability || Security || Usability |
Yes |
1.4 Architecture Decisions |
|
|
Architecture |
A log of all decisions affecting the target architecture including any rationale for the decision… |
- Governance and traceability of architecture decisions
|
Quality, Security |
|
Yes |
1.5 Risks, Issues, Assumptions and Dependencies |
|
|
Architecture |
No content - container only
Provides a record of identified risks, issues, assumptions and… |
|
Cost, Time, Quality, Security, Information Management |
|
Yes |
1.5.1 Risks |
|
|
Architecture |
Provides a record of identified/known architecture risks. Note: Not a place for project risk, eg… |
- Early identification of risk to ensure it is managed and addressed by subsequent architecture definition.
|
Cost, Time, Quality, Security |
|
Yes |
1.5.2 Issues |
|
|
Architecture |
Architecture issues only -no project related issues. may have related project issues. |
- Supports architecture decision making and planning activities.
|
Cost, Time, Quality, Security |
|
No |
1.5.3 Assumptions |
|
|
Architecture |
Architectural assumptions only. Assumptions will typically be resolved as the architecture is… |
- Provides visibility of unknowns to be addressed in later architecture phases. Can be used to capture assumptions throughout the architecture development lifecycle.
|
Cost, Time, Quality |
Accessibility || Availability and Resiliency || Development Resource || Evolution || Internationalization || Location || Performance and Scalability || Security || Usability |
No |
1.5.4 Dependencies |
|
|
Project Manager |
Architecture development that this architecture is dependant on. |
- Provides guidance for project and portfolio prioritisation.
|
Cost, Time, Quality |
Development Resource || Evolution |
|
2. Architecture Definition |
|
|
|
No content - container only. The Architecture Definition Section is the deliverable container for… |
|
|
|
|
2.1 Mapping to Architecture Repository |
|
|
|
No Content - Container only.
The purpose of this section is to highlight (not describe in detail)… |
|
|
|
No |
2.1.1 Artifacts |
|
|
Project Manager |
The purpose of this section is to describe the artifacts that are relevant for or from the… |
|
Cost, Time, Information Management |
|
Yes |
2.1.2 Mapping to Architecture Landscape |
|
|
Architecture |
The purpose of this section is to highlight any patterns that are relevant for or from the… |
- Identifies reuse and rationale for any variation.
|
Cost, Time, Quality |
|
Yes |
2.1.3 Mapping to Reference Models |
|
|
Architecture |
The purpose of this section is to highlight any products and technologies that are relevant to the… |
- Using reference models can reduce the cost and time of developing a solution by reducing complexity, increasing reuse, improving communication, enhancing governance and improving compliance.
|
Cost, Time, Quality, Security |
|
Yes |
2.1.4 Mapping to Standards |
|
|
Architecture |
The purpose of this section is to highlight any standards that are relevant for or from the… |
- Reduce cost by complying with existing standards. Reduce governance effort. Improve quality of architecture.
|
Cost, Time, Quality, Security |
|
Yes |
2.1.5 Re-Use Assessment |
|
|
Architecture |
The purpose of this section is to highlight any re-usable aspects of the architecture.
If there… |
- Reduce operational cost caused by duplication of solution building blocks.
|
Cost, Time, Quality |
|
|
2.2 Baseline Architecture |
|
|
|
No content - container only. |
|
|
|
No |
2.2.1 Business Architecture Models |
|
|
Architecture |
The purpose of this section is to define the current business architecture that is in scope for… |
- used to inform target architecture development if understanding current state architecture is important.
|
Quality |
Accessibility || Internationalization || Location || Security || Usability |
No |
2.2.2 Data Architecture Models |
|
|
Architecture |
The purpose of this section is to define the baseline data architecture for the domain/sub-domain.… |
- Used to inform target architecture development if understanding current state architecture is important.
|
Quality |
Availability and Resiliency || Evolution || Internationalization || Location || Performance and Scalability || Security |
No |
2.2.3 Application Architecture Models |
|
|
Architecture |
The purpose of this section is to define the baseline application architecture for the domain/sub-… |
- used to inform target architecture development if understanding current state architecture is important.
|
Quality |
Accessibility || Internationalization || Security || Usability |
No |
2.2.4 Technology Architecture Models |
|
|
Architecture |
The purpose of this section is to provide a high-level view of the baseline technology architecture… |
- used to inform target architecture development if understanding current state architecture is important.
|
Quality |
|
|
2.3 Target Architecture |
|
|
|
No content - container only |
|
|
|
Yes |
2.3.1 Business Architecture Models |
|
|
Project Manager |
The purpose of this section is to define the target business architecture that is in scope for this… |
- An agreed target architecture that can be approved by decision makers and consumed by implementors.
|
Cost, Time, Quality, Security |
|
Yes |
2.3.2 Data Architecture Models |
|
|
Architecture |
The purpose of this section is to define the target data architecture for the domain/sub-domain… |
- An agreed target architecture that can be approved by decision makers and consumed by implementors.
|
Cost, Time, Quality, Security, Information Management |
|
Yes |
2.3.3 Application Architecture Models |
|
|
Architecture |
The purpose of this section is to define the target application architecture for the domain/sub-… |
- An agreed target architecture that can be approved by decision makers and consumed by implementors.
|
Cost, Time, Quality, Security |
|
Yes |
2.3.4 Technology Architecture Models |
|
|
Architecture |
The purpose of this section is to either provide references to the relevant technology architecture… |
- An agreed target architecture that can be approved by decision makers and consumed by implementors.
|
Cost, Time, Quality, Security |
|
No |
2.4 Gap Analysis |
Target architecture |
|
Project Manager |
The purpose of this section is to define the gap between the current (as-is) and target (to-be)… |
- Informs solution work packages.
|
Cost, Time |
|
No |
2.5 Impact Assessment |
Target architecture, Gap analysis |
|
Project Manager |
The purpose of this section is to assess and document the impact (on the organization) of the… |
- Assess the organizational impact of change within their respective domains. Provides guidance for implementation planning.
|
Cost, Time |
|
Yes |
3. Architecture Requirements Specification |
|
|
Project Manager |
The Architecture Requirements Specification provides a set of quantitative statements that outline… |
- Specification suitable for implementation
|
Cost, Time, Quality, Security |
|
No |
3.1 Conceptual Requirements Summary |
|
|
|
|
|
|
|
Yes |
3.2 Logical Requirements Summary |
|
|
|
|
|
|
|
Yes |
3.3 Physical Requirements Summary |
|
|
|
|
|
|
|