ADM Guidelines and Techniques Part 1 Flashcards
What are the three Classes of Architecture Engagement?
■ Identification of Required Change: outside the context of any change initiative,
architecture can be used as a technique to provide visibility of the IT capability in order to
support strategic decision-making and alignment of execution
■ Definition of Change: where a need to change has been identified, architecture can be
used as a technique to define the nature and extent of change in a structured fashion
Within largescale change initiatives, architectures can be developed to provide detailed
Architecture Definition for change initiatives that are bounded by the scope of a program
or portfolio.
■ Implementation of Change: architecture at all levels of the enterprise can be used as a
technique to provide design governance to change initiatives by providing big-picture
visibility, supplying structural constraints, and defining criteria on which to evaluate
technical decisions
What does TOGAF standard use for organizing the Architecture Landscape?
Concepts of levels and the Enterprise Continuum
What three levels provide a framework for dividing the Architecture Landscape?
- Strategic Architecture provides an organizing framework for operational and change
activity and allows for direction setting at an executive level. - Segment Architecture provides an organizing framework for operational and change
activity and allows for direction setting and the development of effective architecture
roadmaps at a program or portfolio level. - Capability Architecture provides an organizing framework for change activity and the
development of effective architecture roadmaps realizing capability increments.
What four characteristics are typically used to organize the Architecture Landscape?
■ Breadth: the breadth (subject matter) area is generally the primary organizing characteristic for describing an Architecture Landscape Architectures are functionally decomposed into a hierarchy of specific subject areas or segments.
■ Depth: with broader subject areas, less detail is needed to ensure that the architecture has a manageable size and complexity More specific subject matter areas will generally permit (and require) more detailed architectures.
■ Time: for a specific breadth and depth an enterprise can create a Baseline Architecture and a set of Target Architectures that stretch into the future Broader and less detailed architectures will generally be valid for longer periods of time and can provide a vision for the enterprise that stretches further into the future.
■ Recency: finally, each architecture view will progress through a development cycle where it increases in accuracy until finally approved After approval, an architecture will begin to decrease in accuracy if not actively maintained. In some cases recency may be used as an organizing factor for historic architectures.
In the TOGAF standard, patterns are considered?
A way of putting building blocks into context. Patterns offer the promise of helping the architect to identify combinations of Architecture and/or Solution Building Blocks (ABBs/SBBs) that have been proven to deliver effective solutions in the past, and may provide the basis for effective solutions in the future.
Gap Analysis
The basic premise is to highlight a shortfall between the Baseline Architecture and the Target Architecture; that is, items that have been deliberately omitted, accidentally left out, or not yet defined.
Techniques to support migration planning?
- Implementation Factor Assessment & Deduction Matrix - The technique of creating an Implementation Factor Assessment and Deduction matrix can be
used to document factors impacting the architecture Implementation and Migration Plan. - Consolidated Gaps, Solutions, & Dependencies Matrix - The technique of creating a Consolidated Gaps, Solutions, and Dependencies matrix allows the architect to group the gaps identified in the domain architecture gap analysis results and assess potential solutions and dependencies to one or more gaps.
- Architecture Definition Increments Table - The technique of creating an Architecture Definition Increments table allows the architect to plan
a series of Transition Architectures outlining the status of the Enterprise Architecture at specified times.
Transition Architecture State Evolution Table - Transition Architecture State Evolution table - allows the architect to show the proposed state of the architectures at various levels using the defined taxonomy (e.g., the TOGAF TRM).
- Business Value Assessment Technique - A technique to assess business value is to draw up a matrix based on a value index dimension and a risk index dimension
Interoperability Requirements what is this used for?
“Is the ability to share information and services”. Defining the degree to which the information and services are to be shared is a very useful architectural
requirement, especially in a complex organization and/or extended enterprise.
Common way to categorize interoperability?
■ Operational or Business Interoperability defines how business processes are to be shared
■ Information Interoperability defines how information is to be shared
■ Technical Interoperability defines how technical services are to be shared or at least connect to one another
The process for risk management consists of the following activities:
■ Risk classification (impact, time (schedule), cost (budget), and scope)
■ Risk identification (The maturity and transformation readiness assessments will generate a great many risks)
■ Initial risk assessment (effect and frequency in accordance with scales)
■ Risk mitigation and residual risk assessment (will reduce the risk to an acceptable level)
■ Risk monitoring and governance (be approved by the IT governance framework and potentially in corporate governance)
What two levels of risk need to be considered?
- Initial Level of Risk: risk categorization prior to determining and implementing mitigating actions
- Residual Level of Risk: risk categorization after implementation of mitigating actions (if any)
What does Capability-Based Planning technique focus on?
- Focuses on the planning, engineering, and delivery of strategic business capabilities to the enterprise. It is business-driven and business-led and combines the
requisite efforts of all lines of business to achieve the desired capability. - Accommodates most, if not all, of the corporate business models
- Often the need for these capabilities are discovered and refined using business scenarios
- Capability-based planning frames all phases of the architecture development in the context of business outcomes, clearly linking
the IT vision, architectures (ABBs and SBBs), and the Implementation and Migration Plans with the corporate strategic, business, and line-of-business plans. - It assists in aligning IT with the business and helps focus IT
architects on the continuous creation of business value.
An example of three
Stakeholder analysis does what?
Identify the key stakeholders of the Enterprise Architecture. (who is impacted, power to disrupt)
Classify Stakeholder Positions (End users, project org and system operators)
Business scenarios are used to document?
Business requirements, and to articulate an Architecture Vision that responds to those requirements in phase A and B. May be used at different levels of detial.
