Deliverables Baseline Deliverables (B) Flashcards
Communications Plan
Output: A
Input: B, C, D, E, F
-
Purpose
Is used to communicate targeted information to the right stakeholders at the right time in a planned manner is a Critical Success Factor (CSF) for Enterprise Architecture.
Content
■ Identification of stakeholders and grouping by communication requirements
■ Identification of communication needs, key messages in relation to the Architecture Vision, communication risks, and CSFs
■ Identification of mechanisms that will be used to communicate with stakeholders and allow access to architecture information, such as meetings, newsletters, repositories, etc.
■ Identification of a communications timetable, showing which communications will occur with which stakeholder groups at what time and in what location
Capability Assessment
Output: A, E
Purpose
Need to understand the baseline and target capability level of :
■ Business Capability Assessment
■ IT Capability Assessment
■ Architecture maturity assessment
■ Business Transformation Readiness Assessment
-
This Capability Assessment can be examined on several levels:
■ What is the capability level of the enterprise as a whole? Where does the enterprise wish to increase or optimize capability? What are the architectural focus areas that will support the desired development of the enterprise?
■ What is the capability or maturity level of the IT function within the enterprise? What are the likely implications of conducting the architecture project in terms of design governance, operational governance, skills, and organization structure? What is an appropriate style, level of formality, and amount of detail for the architecture project to fit with the culture and capability of the IT organization?
■ What is the capability and maturity of the architecture function within the enterprise? What architectural assets are currently in existence? Are they maintained and accurate? What standards and reference models need to be considered? Are there likely to be opportunities to create re-usable assets during the architecture project?
■ Where capability gaps exist, to what extent is the business ready to transform in order to reach the target capability? What are the risks to transformation, cultural barriers, and other considerations to be addressed beyond the basic capability gap?
Compliance Assessment
Output: G
Input: H
Purpose
Once an architecture has been defined, a governance process is used during the implementation to ensure that the original Architecture Vision is appropriately realized and that any implementation learnings are fed back into the architecture process.
-
Periodic compliance reviews of implementation projects provide a mechanism to review project progress and ensure that the design and implementation is proceeding in line with the strategic and architectural objectives.
Content
■ Overview of project progress and status
■ Overview of project architecture/design
■ Completed architecture checklists:
Implementation and Migration Plan
Output: E, F
Input: F
Purpose
Provides a schedule of the projects that will realize the Target Architecture.
The Implementation and Migration Plan includes executable projects grouped into managed portfolios and programs. The Implementation and Migration Strategy identifying the approach to change is a key element of the Implementation and Migration Plan.
Content
■ Implementation and Migration Strategy
■ Project and portfolio breakdown of implementation
■ Project charters
Implementation Governance Model
Output: F
Input: G, H
Purpose
Ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance.
-
Once an architecture has been defined, it is necessary to plan how the Transition Architecture that implements the architecture will be governed through implementation
Within organizations that have established architecture functions, there is likely to be a governance framework already in place, but specific processes, organizations, roles, responsibilities, and measures may need to be defined on a project-by-project basis.
The Implementation Governance Model ensures that a project transitioning into implementation also smoothly transitions into appropriate Architecture Governance.
Content
■ Governance processes
■ Governance organization structure
■ Governance roles and responsibilities
■ Governance checkpoints and success/failure criteria
Requirements Impact Assessment
Output: RM
Input: RM
Purpose
Assesses the current architecture requirements and specification to identify changes that should be made and the impact of those changes.
-
Content
■ Reference to specific requirements
■ Stakeholder priority of the requirements to date
■ Phases to be revisited
■ Phase to lead on requirements prioritization
■ Results of phase investigations and revised priorities
■ Recommendations on management of requirements
■ Repository reference number
Solution Building Blocks
Output: G
Input: A, B, C, D, E, F, G
Purpose
Implementation-specific building blocks from the enterprise’s Architecture Repository.
Change Request
Output from: F, G, H
Input: None
Purpose
A Change request can be be submitted when the Architecture Definition Document and Architecture Requirement Specification are not sufficient to complete the implementation of a solution.
-
Content
■ Description of the proposed change
■ Rationale for the proposed change
■ Impact assessment of the proposed change
■ Repository reference number
Business Principles, Business Goals, and Business Drivers
Output: Pre, A, B
Purpose
Describe the needs and ways of working employed by the enterprise and provide context for architecture work,
-
Many factors that lie outside the consideration of architecture discipline may nevertheless have significant implications for the way that architecture is developed.
Content
The content and structure of business context for architecture is likely to vary considerably from one organization to the next.
Architecture Requirements Specification
Output from: B, C, D, E, F, RM
Input: C, D, RM
Purpose
A list of quantitative measurable statements that outline what an implementation project must do in order to comply with the target architecture.
-
A major part of the implementation contract. Used with the Architecture Definition Document. An Architecture Requirements Specification will typically form a major component of an implementation contract or contract for more detailed Architecture Definition.
■ The Architecture Definition Document provides a qualitative view of the solution and aims to communicate the intent of the architect
■ The Architecture Requirements Specification provides a quantitative view of the solution, stating measurable criteria that must be met during the implementation of the architecture
Content
■ Success measures
■ Architecture requirements
■ Business service contracts
■ Application service contracts
■ Implementation guidelines
■ Implementation specifications
■ Implementation standards
■ Interoperability requirements
■ IT Service Management requirements
■ Constraints
■ Assumptions
Architecture Building Blocks
Output: F, H
Input: A, B, C, D, E
Purpose
Architecture documentation and models from the enterprise’s Architecture Repository