Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
419 Cards in this Set
- Front
- Back
What are the phases within the ADM? |
Preliminary, A through H, Requirements Management |
|
Describe the ADM Preliminary Phase |
" prep & initiation activities required to create an Arch Capability includes customization of TOGAF and defn of Architecture Principles" |
|
Describe ADM Phase A |
Phase A: - Architecture Vision Describes the initial phase of an architecture development cycle: -defining the scope of the architecture development initiative, -identifying the stakeholders, -creating the Architecture Vision, -obtaining approval to proceed with the architecture development. |
|
Describe ADM Phase B |
Phase B: describes the development of a Business Architecture to support the agreed Architecture Vision. develop baseline (bottom up) develop target (top down) |
|
Describe ADM Phase C |
Phase C: describes the development of Information Systems Architectures to support the agreed Architecture Vision. |
|
Describe ADM Phase D |
Phase D: describes the development of the Technology Architecture to support the agreed Architecture Vision. |
|
Describe ADM Phase E |
Phase E: Opportunities & Solutions conducts initial implementation planning and the identification of delivery vehicles for the architecture defined in the previous phases. |
|
Describe ADM Phase F |
Phase F: Migration Planning addresses how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan. |
|
Describe ADM Phase G |
Phase G: Implementation Governance provides an architectural oversight of the implementation. |
|
Describe ADM Phase H |
Phase H: Architecture Change Management establishes procedures for managing change to the new architecture. |
|
Describe ADM Requirements Management Phase |
Requirements Management examines the process of managing architecture requirements throughout the ADM. |
|
What are the 4 types of architecture in TOGAF (architecture domain) |
BDAT Business, Data, Application, Technical |
|
What is business architecture domain? |
The Business Architecture defines the business strategy, governance, organization, and key business processes. look at business problems irrespective of tech; must be done first |
|
What is data architecture domain? |
The Data Architecture describes the structure of an organization's logical and physical data assets and data management resources. |
|
What is application architecture |
a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization. |
|
What is technical architecture domain? |
logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc. |
|
What is the TOGAF Architecture Content Framework? |
A structural model for arch content (from process flows to requirements to assessments and so on) |
|
What are the three categories of assets in the Content Framework? |
Deliverables, artifacts, and building blocks |
|
What is a deliverable? |
a work product that is contractually specified gets signed off on by stakeholder output of a project |
|
what is an artifact? |
an architectural work product that describes an aspect of the architecture; may not be in a deliverable!! Artifacts are generally classified as catalogs, lists, matrices , and diagrams (pictures of things) NOTE: deliverables may contain artifacts |
|
What is a building block? |
apotentially re-usable component of business, IT, or architectural capability |
|
Name the two categories of building blocks. |
Architectural (ABB)- The requirement - Describe required capability and shape the specification of Solution Building Blocks (SBBs). Solution (SBB) - the solution - components that will be used to implement the required capability i.e. a network |
|
relationships between deliverables, artifacts, and building blocks |
|
|
An example of the relationships between deliverable, artifacts, and building blocks |
|
|
What is the enterprise continuum? |
A view of the Architecture Repository that provides a way to classifying architecture and solution artifacts as they evolve from generic Foundation Architectures (left) to Organization-Specific Architectures (right) "a continuum is a line"; generic on the left, specific on the right |
|
What two concepts make up the enterprise continuum? |
the Architecture Continuum and the Solutions Continuum. |
|
Enterprise Continuum |
|
|
What is the architectural repository? |
Architecture Repository is used to store different classes of architectural output at different levels of abstraction, created by the ADM Think filing cabinet |
|
arch repository |
|
|
What are the major components of the arch repository? |
Architecture Metamodel Architecture Capability Architecture Landscape Standards Information Base (SIB) Reference Library Governance Log |
|
What is the metamodel? |
Describes the organizationally tailored application of an architecture framework, including a metamodel for architecture content. THE TEMPLATES |
|
What is the capability in the arch repository |
The Architecture Capability defines the parameters, structures, and processes that support governance of the Architecture Repository. |
|
What is the arch landscape in the arch repository? |
architectural representation of assets deployed within the operating enterprise at a particular point in time. The landscape is likely to exist at multiple levels of abstraction to suit different architecture objectives Defines as is and to be |
|
What is the SIB? |
Standards Information Base (SIB) captures the standards with which new architectures must comply, SIB may include industry standards, selected products and services from suppliers, or shared services already deployed within the organization. |
|
What is a reference library of the arch repository? |
The Reference Library provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the creation of new architectures for the enterprise. |
|
What is the governance log in the arch repository? |
The Governance Log provides a record of governance activity across the enterprise. |
|
What is the importance of the business capability WRT enterprise arch? |
It defines the organization structures, roles, responsibilities, skills, and processes |
|
Business Capability |
|
|
T/F: An enterprise architecture practice must be run like any other operational unit within a business; i.e., it should be treated like a business. |
TRUE! |
|
What are the capabilities that must be established to support an enterprise architecture practice? |
Financial Management Performance Management Service Management Risk Management Resource Management Communications and Stakeholder Management Quality Management Supplier Management Configuration Management Environment Management |
|
Name some business benefits of enterprise governance using TOGAF |
transparency controlled risk Value creation through monitoring, measuring, evaluation, and feedback
|
|
NOTE: In all cases, it is expected that the architect will adapt and build on the TOGAF framework in order to define a tailored method that is integrated into the processes and organization structures of the enterprise. |
|
|
Define Abstraction |
The technique of providing summarized or generalized descriptions of detailed and complex content. |
|
Actor |
A person, organization, or system that has a role that initiates or interacts with activities. can be internal or external |
|
Application |
A deployed and operational IT system that supports business functions and services; |
|
Application Architecture |
A description of the structure and interaction of the applications as groups of capabilities that provide key business functions and manage the data assets |
|
Application Platform |
The collection of technology components of hardware and software that provide the services used to support applications. |
|
Application Platform Interface (API) |
The interface, or set of functions, between application software and/or the application platform. |
|
Architectural Style |
The combination of distinctive features in which architecture is performed or expressed. |
|
Architecture (2 defns) |
(1) formal description of a system, or a detailed plan of the system at component level, to guide its implementation (source: ISO/IEC 42010:2007). (2) The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time. |
|
Architecture Building Block (ABB) |
A constituent of the architecture model that describes a single aspect of the overall model. |
|
ADM is method used to define arch 9 phases + requirements Flower Chart |
heart of togaf iterative/ never ending baseline and target architecture |
|
What are the classification system or levels of architectures in the Enterprise Continuum (generic to specific)? |
Foundation arch (most generic) Common systems arch Industry arch Org specific arch (most specific) |
|
What is the arch capability of your organization? |
capability of business to support arch full time architecture/group and governance top down and bottom up buy-in roles and responsibilities defined skills and processes |
|
What is the arch repository? |
Think filing cabinet Support enterprise continuum different levels of abstraction MetaModel - templates |
|
ADM - Arch Dev Method |
Most important part of TOGAF; Preliminary phase + 8 phases (A-H) with requirements at the center Phase A-H repeat as necessary; preliminary happens once only method for developing and managing lifecycle of enterprise arch |
|
ADM |
|
|
Can you adapt the ADM and change phase order? |
"One reason for wanting to adapt the ADM ... is that the order of the phases in the ADM is to some extent dependent on the maturity of the architecture discipline within the enterprise" "it often doesn't make sense to do things out of order - like you can't do migration planning before requirements design" Intended to be generic and fit most BUT modifiable/tailorable |
|
All phases have inputs and outputs |
-- |
|
Describe Requirements phase |
it is continuous |
|
Preliminary Phase |
+Prep and initiation activities: -->Define what makes up the "enterprise" (could be a business unit, company, or outside partners) -->Pick your framework -->Evaluate enterprise maturity/capability -->Define architectural principles |
|
Phase A |
Vision Phase (PMI-like) Very business focused High Level Vision - "0.1 level" Obtain SOW -->define scope -->estimate resources -->develop roadmap / schedule -->define KPIs/metrics -->communication plan |
|
Phase B |
Business Architecture; "B" in BDAT Develop baseline business arch v1.0 (current; bottom up) Develop target bus arch v1.0 (top down) Map gaps between baseline and target |
|
Phase C |
Information Systems Arch ("D" & "A" in BDAT) data and app done separately define baseline(s) and target(s) - one for each |
|
Phase D |
Tech Arch; "T" in BDAT develop baseline and target (v1.0s) and gap Tech Arch supports BDA At the end of phase D, have traditional solution defined |
|
Phase E |
Opportunities & Solutions initial implementation planning the identification of delivery vehicles for the architecture defined in previous phases |
|
Phase F |
Migration Planning addresses how to move from the Baseline to the Target Architectures by finalizing a detailed Implementation and Migration Plan. |
|
Phase G |
Implementation Governance provides an architectural oversight of the implementation. |
|
Phase H |
Architecture Change Management establishes procedures for managing change to the new architecture. |
|
Requirements Management |
Managing architecture requirements throughout the ADM. |
|
Objectives of Preliminary Phase |
1- determine arch capability desired by org 2 - establish arch capability |
|
Approach to Preliminary Phase |
-define enterprise -identify key drivers / elements -define requirements for arch work (the arch project) -define arch principles -define frameworks -define relationships between mgmt f/w -evaluate EA maturity |
|
Inputs to Preliminary Phase |
(not as important) -reference materials: TOGAF, Other frameworks - non-arch: strategies, business plans, ITS strategy, business principles Major frameworks w/in the business arch capability partnership / contract agreements - Arch inputs: pre-existing org models; pre-existing arch F/W |
|
Steps of Preliminary Phase |
1 - scope enterprise orgs impacted 2 - confirm governance and support frameworks 3 - define / establish arch team 4 - identify /est arch principles 5 - Tailor TOGAF & F/Ws 6 - implement arch tools |
|
Outputs of Prelim |
1- organizational model for EA 2 - tailored arch F/W 3 - arch repository (possibly new) 4 - restate/reference business principles 5 - "Requests for arch work" (like an SOW) 6 - arch governance F/W |
|
Architecture development is a continuous, cyclical process, and in executing the ADM repeatedly over time, the architect gradually adds more and more content to the organization's Architecture Repository |
NOTE: In fact, the first execution of the ADM will often be the hardest, since the architecture assets available for re-use will be relatively scarce |
|
Which phases are the "arch development phases" and what are the common steps for these phases? |
Phase B, C, & D -Select reference models, viewpoints, and tools -Develop Baseline Architecture Description -Develop Target Architecture Description -Perform gap analysis -Define candidate roadmap components -Resolve impacts across the Architecture Landscape -Conduct formal stakeholder review -Finalize the Architecture -Create Architecture Definition Document |
|
Describe the ADM version # convention |
Phase A docs are 0.1 Phase B, C, and D are 1.0 |
|
Does the order of the phases matter? |
the order is to some extent dependent on the maturity of the architecture discipline within the enterprise.
OR may also be defined by the architecture principles and business principles of an enterprise. |
|
Name some reasons for adapting the ADM |
-ADM is one of many F/Ws in the enterprsie -ADM is mandated for contractors so need to collaborate -the enteprise is smaller -the enterprise is larger |
|
What is a product line architecture? |
In a vendor or production environment, a generic architecture for a family of related products |
|
What are the major ADM info areas managed by a governance approach? |
1 - reference data including external data 2 - process status 3 - audit information including decisions |
|
Why Scope the architecture? |
limits on 1 - organizational authority 2 - objectives and stakeholder concerns 3 - availability of people, resources, and so on |
|
What is an architectural partition? |
mechanism to make sure duplicate work does not happen |
|
What are the four dimensions use to limit scope? |
Breadth Depth Time Period Arch Domains typically focus is on B/D/T and then determine extent of domains |
|
In a complex environment, what/why is an alterntaive to a single ent arch? |
If thought of as too complex/unwieldy then use a number of different ent architectures "Federated Ent Arch" |
|
Define the publish/subscribe model for ent arch scope |
a way to roll out arch governance agreed on quality of materials use of materials monitored |
|
SCOPE DEPTH - needs to be sufficient to express future tailoring/re-use/ extention |
-- |
|
Architecture Integration |
Architectures to address a set of enterprise issues need a consistent frame of reference |
|
What is EA? |
EA is a management discipline that provides a clear line-of-sight from strategicbusiness objectives to underlying business and technology enablers EA aim: facilitate and improve thebusiness decision making process byrevealing how complex organizations EA is: description of the current and/orfuture structure |
|
What are common drivers for EA |
business, technical, and financial challenges -Business Challenges‒ Redundant processes‒ Increasing customer demands‒ Multiple customers, stakeholders & partners -Technical Challenges‒ Redundant data & applications‒ Heterogeneous technologies (old & new)‒ Stove-piped systems‒ No standardization -Financial Challenges‒ Increasing costs (Internal & External)‒ Budget shortfalls |
|
What are some questions that EA focuses on to enable decision making? |
What does the existing enterprise look like? What are oppty to increase performance? Are resources sufficiently allocated? Can solutions be streamlined or shared? What standards should be enforced? What costs can be reduced? |
|
When is EA relevant on a consulting project? |
for consulting projects aimed atoptimizing the often fragmented legacy of processes (both manual and automated), transformingbusinesses into integrated environments responsive to change, or supporting the delivery of thebusiness strategy. |
|
What are the components of a successful EA program? |
Governance An EA methodology• EA descriptive layers (e.g. framework) Program management plans Principles and standards These form the as-is, to-be, and transition |
|
Define Framework |
Comprehensive classification scheme for organizing modeling approach, policies,standards, methods and tools into a synergistic infrastructure |
|
Define Policy |
Formal ground rules for managing & utilizing information resources |
|
Define Standards |
Formal measures to manage & control the quality of IT resources; addressing form, contentand quality |
|
Define Method |
Specified procedures for development, maintenance and control of information outputs;data & process modeling and testing methods |
|
Define Tools |
Comprehensive set of tools to assist the development, management & control of theinformation resources; architecture modeling, dictionary/repository, CASE and modelingtools |
|
What is an EA methodology including some examples |
Describes the process (how) the EnterpriseArchitecture is implemented including:‒ Who‒ How‒ When Examples: • Centralized Approach • Federated/Hybrid Approach • Mission Based Approach • Pattern Based Approach • Hypothesis-drivenApproach |
|
What is an EA framework and include examples |
Describes the deliverables & products used torecord information about each layer of theorganization Examples :• FEAF (Federal EnterpriseArch. Framework) • Zachman Framework• DoDAF • TEAF (Treasury Ent. Arch.Framework) |
|
T/F: Togaf is methodology AND framework |
True dat! |
|
Phase B = which domain? And why does it matter? |
Business Arch (B in BDAT) foundation on which all other domain architectures are built |
|
What are inputs to business? |
LOOK up all 11 |
|
What are the steps to Bus Arch? |
1. select reference model/'view point, tools 2. develop baseline 3. develop target - builds on the vision v0.1 4. gap analysis 5. define candidate roadmap 6. resolve impacts across landscape 7. stakeholder review 8. finalize 9. arch definition document |
|
outputs to Bus Arch? |
1. refined phase A deliverables 2. draft arch defn doc (baseline & target) v1.0 3. draft arch requirements spec and gap analysis 4. business arch components of arch roadmap |
|
names some business artifacts |
catalogs - org, actor, driver, business serivce, role, location, events matrices - business interaction, actor/role diagrams - business footprint, product lifecycle., use-case diag, process flow diag words |
|
What are some of the processes/domains to be identified and understood during the preliminary phase? |
current methods for architecture description Current project management frameworks and methods Current systems management frameworks and methods Current project portfolio management processes and methods Current application portfolio management processes and methods Current technology portfolio management processes and methods Current information portfolio management processes and methods Current systems design and development frameworks and methods |
|
When you are in prelim phase and are trying to understand organizational context, what are some areas to tailor for the selected F/W? |
-level of formality and rigor applied -level of sophistication/expenditure required touch points w/ other -organizations/process/roles/responsibilities -focus of content coverage |
|
list some examples of imperatives that drive requirements for architectural work |
Business requirements Cultural aspirations Organization intents Strategic intent Forecast financial requirements |
|
Are architectural principles based on business principles? |
Yes, in part, though business principles are defined outside the scope of arch function. |
|
What other F/W much coexist with TOGAF? |
Business capability mgmt Project/portfolio mgmt ops mgmt solution development mgmt |
|
describe the interoperabilty between f/w for an enterprise |
|
|
The enterprise is a system of systems |
The enterprise is a system of systems |
|
Why do you use an capability maturity model? |
to assess the ability of the enterprise to exercise different capabilities examples: NASCIA and US Dept of Commerce ACMM |
|
in the prelim phase, how to you scope the enterprise org impacts? |
Identify: -core enterprise units - most affected and achieve most value from the work -soft enterprise units - will see changes as result of working with core -extended enterprise - outside scope -communities involved -governance involved (legal frameworks / geographies |
|
in Prelim phase, describe how/why confirm governance / FW |
need to understand how arch material is brought under governance (what type of repository, what are mandates for repository, what are relationships and who reports on status, ownership |
|
What aspects of TOGAF do you tailore during prelim? |
-terminology tailoring -process tailoring -content tailoring |
|
What are the outputs of prelim? |
-Org Model -Tailored Arch F/W -Initial arch repository -restatement of business principles, goals and drivers -request for arch work -governance F/W |
|
When does phase A start? |
With receipt of request for arch work from sponsor |
|
What is the key activity of Phase A |
-ensuring that existing definitions are current, and clarifying any areas of ambiguity -ensuring that the existing principles definitions are current, and clarifying any areas of ambiguity. |
|
What benefit does the sponsor get from the architectural vision? |
provides key tool to sell the benefits of the proposed capability to stakeholders describes now new capability meets business goals/ strategic objectives |
|
what are key elements of the arch vision |
enterprise mission, vision, strategy, and goals |
|
NOTE: if there is little existing EA assets, during Phase A , may need to establish |
OR during prelim... much latitude on when things happen |
|
What is the ADM approach for creating business scenarios? |
it is a "method w/in a method"... |
|
What are the inputs to Phase A |
-reference materials: organizational model -non-arch: request for arch work; principles, goals, drivers -Arch inputs: org model, maturity model, tailored arch framework populated repository NOTE: These are tied to outcomes of prelim |
|
Level of detail for Phase A depends on ?? |
scope and goals of request for arch work |
|
What are the steps in Phase A? |
11 Steps 7.4.1 Establish the Architecture Project 7.4.2 Identify Stakeholders, Concerns, and Business Requirements 7.4.3 Confirm and Elaborate Business Goals, Business Drivers, and Constraints 7.4.4 Evaluate Business Capabilities 7.4.5 Assess Readiness for Business Transformation 7.4.6 Define Scope 7.4.7 Confirm and Elaborate Architecture Principles, including Business Principles 7.4.8 Develop Architecture Vision 7.4.9 Define the Target Architecture Value Propositions and KPIs 7.4.10 Identify the Business Transformation Risks and Mitigation Activities 7.4.11 Develop Statement of Architecture Work; Secure Approval |
|
Describe establishing the arch project (phase A) |
keep P< f/w in mind secure recongnition of the porject and endorsement |
|
What are the 3 key objectives during phase A WRT stakeholder/concern identification and what is the primary product? |
Identify candidate vision components and requirements to be tested identify candidate scope boundaries for the engagement identify stakeholder concerns, issues, and cultural factors PRODUCT: stakeholder map |
|
What is included in the stakeholder map? |
concerns, viewpoints, some aspects of communications plan key roles/responsibilities |
|
T/F - during arch vision, new requirements may be generated |
yes and they must be managed and scoped appropriately |
|
why assess readiness for business transformation |
augment capability assessment used to shape scope of architecture |
|
What are the key steps to defining target arch value proposition/KPI? What is the output? |
Develop the business case for the architectures and changes required Produce the value proposition for each of the stakeholder groupings Assess and define the procurement requirements Review and agree the value propositions with the sponsors and stakeholders concerned Define the performance metrics and measures to be built into the enterprise architecture to meet the business needs Assess the business risk outputs are incorporated into statement of work |
|
What are the two levels of risk? |
initial level of risk residual level of risk |
|
during Phase A - develop statement of arch work, you will need to assess work products. what are two items you need to ensure in order to assess the work products |
performance metrics are built in specific performance work products are available. |
|
What are outputs of Phase A? |
approved statement of arch work refined business principles, goals and drivers arch principles capability assessment arch vision tailored arch framework (method, content, tools) communications plan |
|
what are the objectives of Phase B? |
develop target business arch identify candidate arch roadmap components to fill gaps |
|
T/F - Business arch is prerequisite for any other arch domain (B-D-A-T) |
True - it also demonstrates value |
|
Name some business models used during Phase B |
-activity models/ business process models -use case models -class models (similar to logical data models, describe static information and relationships) -node connectivity diagram -info exchange matrix ( includes performance/security and ownership) NOTE: All can be represented using UML |
|
Name inputs to Phase B |
org model tailored F/W approved stateme of arch work arch principles enterprise continuum arch repository arch vision draft arch defn doc (0.1 versions) |
|
What are the steps in Phase B? |
8.4.1 Select Reference Models, Viewpoints, and Tools 8.4.2 Develop Baseline Business Architecture Description 8.4.3 Develop Target Business Architecture Description 8.4.4 Perform Gap Analysis 8.4.5 Define Candidate Roadmap Components 8.4.6 Resolve Impacts Across the Architecture Landscape 8.4.7 Conduct Formal Stakeholder Review 8.4.8 Finalize the Business Architecture 8.4.9 Create Architecture Definition Document |
|
What are some modeling processes used to support view points during Phase B? |
structured analysis use-case analysis process modeling |
|
What are sub-steps for selecting reference models/viewpoints/tools in Phase B? |
-determine overall modeling process -identify service granularity level, boundary/contracts -identify catalogs of business building blocks (generally based on attributes of metamodel entities) -identify matrices & diagrams identify requirements to be collected |
|
What are outputs of Business Arch Phase B? |
refined arch vision draft arch defn doc draft requirements spec busines arch components catalogs/matrices/diagrams |
|
What are the objectives of Phase C? |
-develop target info system arch (data and app) -identify arch roadmap |
|
What are inputs to Phase C? |
org model, tailored F/W **Application principles **Data principles statement of arch work arch vision repository draft arch defn doc draft requirements spec business arch components of arch roadmap |
|
What are outputs of Phase C? |
refined arch vision draft arch defn doc V1.0 draft requiremenst spec info system components of an arch roadmap |
|
What are the objectives of the data arch of Phase? |
develop target data arch identify candidate arch roadmap |
|
What are key considerations for data architecture? |
data management data migration data governance repository - there are data standards based on industry |
|
During Phase C, what are key considerations for data management |
-which components are system of record or reference for master data -is there enterprise-wide standard for all app components -what are data entries used by business processes/functions/services -software needs for data integration Think backups! |
|
Name 3 types of data migration? |
master, transnational and reference |
|
During Phase C- Data arch, what are 3 dimensions of data governance |
structure, management system, people |
|
What are the steps for addressing Phase C- Data Arch |
NOTE: all steps must be closed during finalize data arch step and outputs published. -Select Reference Models, Viewpoints, and Tools -Develop Baseline Data Architecture Description -(should be able to leverage existing standards) -Develop Target Data Architecture Description -Perform Gap Analysis -Define Candidate Roadmap Components -Resolve Impacts Across the Architecture Landscape -Conduct Formal Stakeholder Review -Finalize the Data Architecture -Create Architecture Definition Document |
|
During Phase C - data arch, what are key sub-steps for modeling? |
Collect data-related models Rationalize data requirements and align with any existing enterprise data catalogs and models; Update and develop matrices by relating data to business service, business function, access rights, and application **Elaborate Data Architecture views by examining how data is created, distributed, migrated, secured, and archived |
|
What catalog should be created for data architecture and housed in the repository? |
data entity/data component |
|
Name a few Data Arch matrices. |
- Data Entity/Business Function -Business Service/Information -Application/Data |
|
Name a few diagrams to develop for data architecture. |
Conceptual Data diagram Logical Data diagram Data Dissemination diagram Data Lifecycle diagram Data Security diagram Data Migration diagram |
|
Once data arch is finalized, the impacts on the arch landscape need to be resolved. explain |
impact on pre-existing arch? opportunities to leverage this work in other places in the enterprise will this be impacted by other projects |
|
Name some data arch items in the arch defn doc... |
-Business data model -Logical data model- -Data management process model -Data Entity/Business Function matrix -Data interoperability requirements (e.g., XML schema, security policies) |
|
What are the objectives of the app arch or Phase C? |
-develop target app arch -identify candidate arch roadmap to fill taps |
|
During Phase C - App Arch - what are some inputs from the arch repository? |
-Re-usable building blocks -Publicly available reference models -Organization-specific reference models -Organization standards III-RM from TOGAF |
|
What are the steps for Phase C App Arch? |
11.4.1 Select Reference Models, Viewpoints, and Tools 11.4.2 Develop Baseline Application Architecture Description 11.4.3 Develop Target Application Architecture Description 11.4.4 Perform Gap Analysis 11.4.5 Define Candidate Roadmap Components 11.4.6 Resolve Impacts Across the Architecture Landscape 11.4.7 Conduct Formal Stakeholder Review 11.4.8 Finalize the Application Architecture 11.4.9 Create Architecture Definition Document |
|
Identify required catalogs for Phase C - App Arch? |
-Application Portfolio catalog -Interface catalog |
|
Identify some matrices of the Phase C - App Arch... |
-Application/Organization matrix -Role/Application matrix -Application Interaction matrix -Application/Function matrix |
|
Name a few app arch diagrams to develop during Phase C - App Arch |
-Application Communication diagram -Application and User Location diagram -Enterprise Manageability diagram -Process/Application Realization diagram -Application Migration diagram -Software Distribution diagram -Software Engineering diagram -Application Use-Case diagram |
|
NOTE: INPUTS for PHASE C are outputs of Prelim, A and B |
Always leverage the repository |
|
Does the TOGAF offer templates? |
Yes - https://www2.opengroup.org/ogsys/jsp/publications/PublicationDetails.jsp?catalogno=i093 |
|
NAme a few App Arch Artifacts |
catalogs: app portfolio, interface matrices - app/ org matrix, role/app Diagrams - app communication, app use location, enterprise manageability diagram Key words: application, interface, software |
|
Phase D - Tech arch - what is key purpose? |
identify baseline and target tech arch V1.0 |
|
What is the approach for Phase D? |
go to Arch repository and check for -existing IT services -TOGAF Tech Reference Model (TRM) -Generic industry tech models |
|
What are some Phase D artifacts? |
Catalogs - tech standards Matrices - app/tech matrix Diagrams - environment/locations diagram, decomposition diagram, communications engineering diagrams Key words: technology, network, hardware, environment, platform, communication |
|
Objectives of Phase E |
-complete initial version of arch roadmap based on gap analysis of BDAT -determine if incremental approach -formulate implementation and migration strategy (is a transitional arch needed) -identify and group work packages |
|
What is the approach to Phase E (opportunities and solutions)? |
Figure out how to deliver target arch: -arch roadmap -work packages -transitional arch -implementation and migration plan |
|
Inputs are the same for Phase E with exception of what? |
product information (COTS) change requests for business programs/projects |
|
What are the steps for Phase E?? |
-determine key corporate change attributes -determine business constraints -review and consolidate gap analysis of Phase B-D -consolidate requirements -validate dependencies -consolidate inter-operability requirements -confirm readiness/risk -formulate impl/migration strategy -work package grouping -identify transition arch ***Create arch roadmap & the implementation/migration plan |
|
Unique Phase E outputs? |
baseline/target V1.0 arch roadmap V0.1 Implementation and migration plan v0.1 |
|
Only two artifacts of Phase E, what are they? |
Product context diagram, benefits diagram Key Word: "Benefits" |
|
Phase E concentrates on HOW to deliver architecture |
NOTE: the roadmap should be best-fit |
|
Phase E is the first step for the creation of what? |
implementation and migration strategy |
|
What are some migration strategies? |
greenfield revolutionary evolutionary |
|
What are a few common migration methodologies? |
quick win achievable target value chain |
|
What is Phase F? |
Migration Planning |
|
What are Phase F objectives? |
-Finalize arch roadmap and implemmentation plan -ensure plan coordinated with enterprise change approach -ensure business value understood by stakeholders -think through implementation costs, resources, timing -Transition from developing arch to implementing |
|
What is the approach for Phase F? |
create implementation and migration plan |
|
what are inputs for Phase F? |
reference: arch repository non-arch: request for arch, capability assessment, comms plan arch: org models, governance models, tailored F/W, SOAW, Arch vision, arch repository, draft arch defn doc; draft requirements spec, CRs, V0.1 roadmap, Business and IT capability assessment |
|
What are Phase F Steps? |
-confirm mgmt f/w interactions -assign business values to each work package -estimate resource requirements/timings -prioritize -confirm arch roadmap and update arch defn doc -generate impl and migration plan -complete arch development and lessons learned - |
|
What are document outputs of Phase F? |
-implementation plan V1.0 -finalized: arch defn doc; arch requirements, and arch roadmap -reuseable ABBs -gather requests for arch work for next cycle of ADM -implement governance model -change requests for arch capabilities -project charters |
|
What is an ABB? |
Arch building block (non-tech per se) |
|
For Phase F, one step is confirming mgmt F/W interactions... explain |
4 frameworks typically involved: -Business planning -EA -PPM -Ops MGMS |
|
During Phase F, business value is assigned to work packages. What are some issues to address during this process? |
-performance evaluation criteria to monitor transformation -ROI Criteria -Business value defn -Critical Success Factors -Measures of Effectiveness (MOE_ -Strategic Fit |
|
How are SBBs used for migration planning? |
Used during prioritization determine net benefit of SBB delivered and validate risks effectively mitigated |
|
What is involved in Phase G? |
ensure conformance with target arch governance duties handling CRs for implementation team update baseline arch as changes implemented |
|
When does Phase G end? |
When solutions are fully deployed NOTE: can be long phase |
|
What are the objectives of Phase G? |
1- Ensure implemetation conforms with target arch 2- perform appropriate arch governance functionsl |
|
What is the approach for Phase G? |
-establish implementation program for transition arch -phased deployment schedule that reflects arch roadmap -follow standards for governance -use project/portfolio mgmt approach -define operations F/W |
|
Inputs (documents) |
All existing docs to date
|
|
What are Phase G steps? |
-Confirm scope and priority -Identify deployment resources/skills -Guide development of solutions deployment -Perform EA compliance reviews -Implement business and IT Ops - Post Imp review and closure |
|
What are outputs of Phase G? |
-Architecture contract - agreements between development partners and sponsors on (chapter 49) -Compliance Assessments -CRs -Arch compliant solutions deployed |
|
Name key aspects of deploying an arch compliant solution |
-populated arch repository arch compliance recommendations recommendations on service delivery requirements recommendations on performance metrics SLAs update Arch Vision Arch defn doc up[dated ops models updated |
|
Where does Phase H generally occur? |
Last Phase of ADM |
|
What's involved in Phase H? |
-keep arch alive -ensure arch governance happening -ensure arch capability maintained monitoring and track changes |
|
Objectives of Phase H (change mgmt) |
-ensure arch livecycle maintained -ensure arch governance F/W executed -ensure arch capability meets requirements |
|
Describe the approach to Phase H |
-drivers for change - react to reality -Change mgmt process determines how changes handled -how to determine simple maintenance versus ADM cycle |
|
Phase H inputs? |
all same + Change Requests - tech changes, business changes, lessons learned Governance model |
|
What are Phase H steps?? |
-establish value realization process -deploy monitoring tools -manage risk -provide analysis for arch change mgmt -develop change requirements to meet performance targets -manage governance process -activate process to implement changes |
|
Outputs of Phase H? |
arch updates changes to arch F/W changes to arch principles new request for arch work update SOaW Update arch contract update compliance assessments |
|
Monitoring business growth/decline is an aspect of Phase H - change management - why? |
need to understand if EA continues to work for tomorrow |
|
What role does capacity measurement have in EA and in what phase is it monitored? |
Monitored in phase H - used to determine if EA still bringing maximum business value |
|
What is an arch compliance report and when is it created? |
created during phase H states if change is compliant to current arch and if non-compliant, why exempt and what future plan is |
|
What are the three ways to change existing infrastructure? |
strategic - top down (capital) bottom up - operations and maint) experience based incremented by ops mgmt |
|
What is an RFC? |
request for change |
|
What are tech related drivers for arch CRs? |
new tech reports asset mgmt cost reduction tech withdrawal standards initiatives |
|
What are business drivers for arch CRs? |
business-as-usual development business exceptions business innovations business tech innovation strategic change |
|
What are the three categories of changes? |
simplification change - reduce investment incremental change - get additional value re-architecting change - increase investment for new value |
|
What are activities are undertaken to determine the category of change? |
-Registration of all events that may impact the architecture -Resource allocation and management for architecture tasks -The process or role responsible for architecture resources has to make assessment of what should be done -Evaluation of impacts |
|
Describe rules-of-thumb for maintenance over redesign WRT CRs. |
-If change impacts two stakeholders or more, architecture redesign If impacts only one stakeholder, change management. If the change can be allowed under a dispensation, then change management. |
|
What are inputs to Phase H - Change Management? |
Everything to date! |
|
During Phase H, what things could you monitor with tools? |
-technology changes --> impact the Baseline Architecture -business changes --> Baseline Architecture -Business value tracking -enterprise Architecture Capability maturity -asset management programs -QoS performances and usage -business continuity requirements |
|
When does requirements management occur during ADM? |
continuously all the time for all phases in response to many things including new competitor, new legislation, disproven assumptions, no company policy or missed requirement |
|
What are the objectives of requirements management |
ensure sustained req. mgmt process operates for entire ADM and are available for each phase when needed |
|
Describe the Approach to requirements mgmt... |
-center of hub -architecture should identify which requirements relevant to which phase -no specific tool recommended by TOGAF |
|
What is different about the steps steps involved in requirements management? |
-manage interactions between requirements and phases -steps are continuous -steps are assigned to either req. mgmt or adm phase |
|
What are the requirements management steps? |
-identify/document (from ADM) -base on baseline req, determine priorities. -confirm stakeholder buy-in -monitor baseline -identify Change requirements (from ADM) -identify Change requirements (non-ADM) -Assess impact -implement Phase H outcomes -update requirements repository -implement change in current ADM phase -revise gap analysis |
|
name the outputs of requirements management |
requirement impact assessment arch requirement spec |
|
what are the artifacts of requirements management |
there are none |
|
Can the requirements repository hold requirements from multiple ADM cycles? |
Yes |
|
When are high level requirements gathered? |
during architectural vision - phase A |
|
What are the two kinds of requirements? |
functional and non-functional |
|
when defining requirements, what other aspects should be taken into account? |
-Assumptions for requirements -Constraints for requirements -Domain-specific principles that drive requirements -Policies affecting requirements -Standards that requirements must meet -Organization guidelines for requirements -Specifications for requirements |
|
Know the requirements steps in 17.4 of the TOIGAF |
requirements management steps versus ADM Phase steps |
|
Which phase is recognized as the "final phase" of defining enterprise arch? |
Phase F - when switch from arch to implementation governance |
|
What is the enterprise continuum? |
-a view of the arch repository -classifying arch and solution artifacts -from generic to specific -contains arch continuum and solutions continuum "[...] a view of the Architecture Repository that shows the evolution of these related architectures from generic to specific, from abstract to concrete, and from logical to physical" "Enterprise Continuum is as a view of the repository of all the architecture assets" |
|
What is the arch repository? |
contains all building blocks that go into architecture "empty box you fill with arch outputs" tool that allows you to classify artifacts a matrix with generic to specific (left to right) from arch to solutions (AAB on top, SBB on bottom) |
|
What is foundation architecture? |
generic / arch continuum like TFM or SIB |
|
What is common systems arch? |
less generic / arch continuum |
|
What is industry arch? |
more specific/ arch continuum managed by industry group e.g. credit card processing |
|
What is org specific arch? |
most specific/ arch continuum your business services and function only for your business |
|
what are the 4 levels of specificity of arch continuum?
|
Foundation arch --> common Systems arch --> Industry arch --> Org Specific arch |
|
what are the 4 levels of specificity of solutions continuum? |
Foundation solutions--> common Systems arch --> Industry arch --> Org Specific arch |
|
what is a foundational solution |
generic/solutions continuum generic solutions e.g. programming languages, ITIL, operating systems |
|
what is a common systems solution |
product on top of foundational generic but with some details e.g. MS Office, firewall software applicable across industry |
|
what is an industry solution? |
solutions continuum/more specific the solution is industry specific like a COTS credit card processing software |
|
what is an org specific solution? |
your customization specific to your business |
|
What are the two primary TOGAF reference models? |
Technical Reference Model (TRM) and the Integrated InformationInfrastructure Model (III-RM) |
|
What is contained in the enterprise continuum? |
it can contain architecture descriptions, models, building blocks, patterns, viewpoints, and other artifacts - that exist both within the enterprise and in the IT industry at large, |
|
|
|
|
What are the three distinct continua in the enterprise continuum? |
enterprise continuum architectural continuum solutions continuum |
|
Describe the Overarching Enterprise Continuum |
-outermost -contains assets that may influence arch but not directly used by ADM -policies, standards, strategic initiatives, org structures - contextual factors: regulatory change, tech advances, competitor activity contains two specializations: arch and solution |
|
Describe the architectural continuum. |
-a consistent way to describe the generic -rules/relationships. -includes reusable assets (AABs) shows relationships among foundational frameworks like TOGAF useful for discovery to uncover commonality |
|
describe the solutions continuum |
-describes the implementation of what is described in the arch continuum -contains SSBs |
|
what is the difference between ABB and SBB |
ABBs are defined in relation to a set of contextual factors and then realized through SBBs. |
|
Where does the TRM fall on the architectural continuum? |
foundational architecture |
|
describe common system arch |
Common Systems Architectures guide the selection and integration of specific services from the Foundation Architecture to create an architecture useful for building common (i.e., highly re-usable) solutions across a wide number of relevant domains. |
|
give examples of common systems arch |
a security architecture, a management architecture, a network architecture, an operations architecture, etc. Each is incomplete in terms of overall system functionality, but is complete in terms of a particular problem domain TOGAF III-RM is a common sys |
|
What are characteristics of common systems arch? |
-Reflects requirements specific to a generic problem domain -Defines building blocks specific to a generic problem domain -Defines business, data, application, or technology standards for implementing these building blocks -Provides building blocks for easy re-use and lower costs |
|
Describe industry architectures |
-integration of common architectures... -guides the creation of industry solutions for targeted customer problems within a particular industry. |
|
what are some characteristics of an industry architecture? |
-Reflects requirements and standards specific to a vertical industry -Defines building blocks specific to a generic problem domain -Contains industry-specific logical data and process models -Contains industry-specific applications and process models, as well as industry-specific business rules -Provides guidelines for testing collections of systems -Encourages levels of interoperability throughout the industry |
|
Describe an org specific architecture. |
-describes and guides the final deployment of solution components for an enterprise provides a way to communicate and manage business across all 4 arch domains |
|
What is the solutions continuum? |
the detailed specification and construction of the architectures at the corresponding levels of the Architecture Continuum - A populated repository based on the Solutions Continuum can be regarded as a solutions inventory or re-use library, |
|
|
|
|
describe the relationship between the solutions and arch continuum |
guidance, direction, and support. |
|
The Enterprise Continuum presents mechanisms to help improve productivity through leverage. The Architecture Continuum offers a consistent way to understand the different architectures and their components. The Solutions Continuum offers a consistent way to understand the different products, systems, services, and solutions required. |
The Enterprise Continuum presents mechanisms to help improve productivity through leverage. The Architecture Continuum offers a consistent way to understand the different architectures and their components. The Solutions Continuum offers a consistent way to understand the different products, systems, services, and solutions required. |
|
what are the 4 areas included in an architectural capability assessment |
business IT arch maturity business transformation created in phase A; updated in Phase E |
|
Where are results of arch capability assesment stored? |
in governance log |
|
What is stored in the governance log? |
decisions compliance assessments capability assessments calendar project portfolio performance measurements |
|
Describe Business Capability Assessment |
capabilities of business baseline state assessment of performance future state aspiration how capability is realized (baseline or future) likely impacts to business if target arch is realized |
|
describe IT capability |
baseline / target maturity of change process baseline/target maturity of operational process capability and capacity assessment likely impacts if target arch realized |
|
Arch Maturity Assessment |
-arch governance processes/org/roles/responsibilities -arch skills assessment -breadth/depth/quality of landscape defn -breadth/depth/quality of standards defn -breadth/depth/quality of reference models assessment of re-use potential |
|
Business Transformation Readiness Assessment |
-readiness factors -vision for readiness factors -current/target readiness ratings -readiness risks think "organizational change mgmt" |
|
define Stakeholders |
an individual, team or organization with interests or concerns with the outcomes of the architecture |
|
define view |
representation of a related set of concerns may be represented by a model does not need to be visual/graphic in nature demonstrates area of interest to stakeholders |
|
provide examples of views |
people workflow view business objects view data entity view cost view hardware view |
|
define viewpoint |
a generic way to create a view a view is what you see; a viewpoint is where you are looking from "the vantage point or perspective that determines what you see" |
|
name some benefits of stakeholder mgmt |
-identify key players and get support -help win more resources -better communication / transparency -better anticipate reactions -identify competing |
|
what are the steps in stakeholder management? |
identify stakeholders classify stakeholder positions determine stakeholder mgmt approach tailor engagement deliverables |
|
what are the most important stakeholders to identify |
influencers - well respected and moving up |
|
what a a few sample questions you would ask to assess stakeholder readiness to behave in a supportive manner? |
-Is that person ready to change direction and begin moving towards the Target Architecture? If so, how ready? - Is that person capable of being a credible advocate or agent of the proposed enterprise architecture initiative? If so, how capable? |
|
What is the power matrix/grid for stakeholders? |
|
|
what are 4 columns of a stakeholder map? |
stakeholder position key concerns class catalogs/matrices/diagrams |
|
define governance |
practice why which architectures are controllled "Governance is essentially about ensuring that business is conducted properly. " |
|
What is the hierarchy of governance? |
Corporate (Exec) tech (CIT/CTO) IT (linked to business goals) Arch NOTE: each can exist in multiple geographic levels as well |
|
what are the characteristics of governance? |
-discipline -transparency -independence -accountability -responsibility -fairness |
|
What occurs during architectural governance |
-systems of controls over components/activities -system to ensure compliance with standards and legal obligations -process to support management of the controls/compliance -accountability practices |
|
When does implementation governance occur? how does that differ from overall arch governance |
implementation governance happens in Phase G arch governance is overarching |
|
What are the 6 processes of architectural governance? |
-policy management/take-on -compliance -dispensation (exceptions/waivers) -monitoring/reporting -business control -env mgmt NOTE: there are many layers of governance |
|
describe technology governance |
how an organization utilizes technology in the research, development, and production of its goods and services. |
|
What is IT Governance |
the framework and structure that links IT resources and information to enterprise goals and strategies Institutionalizes best practices for planning, acquiring, implementing, and monitoring IT performance NOTE: example IT F/W = COBIT there is mapping of TOGAF to COBIT |
|
Is arch governance a board level responsibility? |
YES |
|
conceptual arch governance F/W |
|
|
What is Policy Management and Take-on? |
"architecture amendments, contracts, and supporting information must come under governance through a formal process in order to register, validate, ratify, manage, and publish new or updated content" |
|
Describe Arch governance |
"Architecture governance is the practice and orientation by which enterprise architectures and other architectures are managed and controlled." |
|
What groups are typically invovled in arch governance org structure? |
-Global governance board -Local governance board -Design authorities -Working parties |
|
|
|
|
What are the three key areas of architectural management? |
Develop, Implement, and Deploy |
|
What are some of the operational benefits of arch governance? |
-Integrates and institutionalizes IT best practices -Aligns with industry frameworks such as COBIT -Protects the underlying digital assets of the organization -Promotes visible risk management |
|
What are key success factors of Arch Governance? |
-Best practices for the submission, adoption, re-use, reporting, and retirement of architecture policies, procedures, roles, skills, organizational structures, and support services -Organizational responsibilities and structures to support the architecture governance processes and reporting requirements -Integration of tools and processes to facilitate the take-up of the processes, both procedurally and culturally -Control Criteria of the architecture governance processes, dispensations, compliance assessments, SLAs, and OLAs -Internal and external requirements for the effectiveness, efficiency, confidentiality, integrity, availability, compliance, and reliability of all architecture governance-related information, services, and processes |
|
Reference Models --> not much on TOGAF L1 test aside from where they fit on continuum |
Reference Models --> not much on TOGAF test aside from where they fit on continuum |
|
What does III-RM stand for |
Integrated information infrastructure reference model |
|
What does TRM stand for |
technical reference model universally applicable and can be used for any system arch (sooo generic) |
|
What are the three levels of the TRM |
applications --> app platforms --> communications infrastructure |
|
TRM details |
TRM is this graphic plus definitions of the terms here |
|
Where is TRM on arch continuum |
foundational |
|
Where is III-RM on arch continuum |
common systems arch |
|
III-RM |
|
|
Describe Prelim Phase - Step 5 - Tailor TOGAF |
- TOGAF designed to be modified including terminology - modify ADM to complement your enterprise - update the arch content F/W templates as needed |
|
Describe Prelim Phase - Step 6 - Implement Arch tools |
-tools selected based on scale & arch maturity -possible tool for arch repository -anywhere from simple MS office to specialty tools |
|
Describe Prelim Phase - Step 1 - Scope |
figure out who is impacted: -Core Ent/Units - direct -Soft Enterprise - see change but not direct impact -Extended enterprise - outside scoped enterprise that will see the changes -Communities - groups of stakeholders -Governance |
|
Describe Prelim Phase - Step 2 - Confirm Governance/FWs |
-assess current governance model -figure out how arch docs will be brought under governance -determine if governance changes needed |
|
Describe Prelim Phase - Step 3 - est Arch Team |
-Look @ existing enterprise and business capabilities - Do a maturity assessment and id the gap - key roles -request process changes -are there constraints on the arch work -review w/ sponsors and AAB - assess budget for arch team |
|
Describe Prelim Phase - Step 4 - arch principles |
-rules for designing arch -don't change often -foundation for governance -gives way to say "no" for things that fall outside principles |
|
Describe the Phase A - Arch Vision Steps |
1 - establish arch proj 2 - id stakeholders/concerns/bus req |
|
Describe Phase A - Step 1 - establish arch project |
-create the project (same as other PM efforts) -plan and manage using acceptable practices secure recognition |
|
Describe Phase A - Step 2 - Identify Stakeholders/concerns |
- id the stakeholders & concerns (use matrix) - gather business requirements - figure out which view and viewpoints need to be dev'd |
|
Describe Phase A - Step 3 - confirm business goals/drivers/constraints |
-what are business goals and strategic drivers - make sure definitions up to date and clear defined constraints (time/budget/resources) |
|
Describe Phase A - Step 4 - business capabilities |
two bus capabilities - 1- ability of enterprise to develop and use arch 2 - baseline and target capabilities of the enterprise itself - address any gaps in arch capability / go back to prelim phase if you need to - include gaps/limitations into arch |
|
Describe Phase A - Step 5 - assess readiness |
- use TOGAF bus trans readiness assessment to figure out if can adapt to change - results are inputs to defining target arch |
|
Describe Phase A - Step 6 - define scope |
-scope for arch itself (what's in and out) -baseline & target often different detail levels; target needs to be more detailed -include the breadth of the enterprise, lev of detail needed, address partitioning and arch domains as well as existing assets |
|
Define Phase A - Step 7 - confirm principles |
- make sure defns current - secure endorsement for new itesm |
|
in Define Phase A ... which step is biggest |
Step 8!! - develop arch vision |
|
Define Phase A - Step 8 - Develop arch vision |
- based on inputs to date - create high level (version 0.1) of baseline and target system (can be simple conceptual diagrams) |
|
Define Phase A - Step 9 - define arch value and KPIs |
- Develop business case - Review value with stakeholders -Define performance metric and measures to build in -accept risk(s) |
|
Define Phase A - Step 10 - id transformation risks/mitigation |
identify risks of the arch vision Two levels of risk: 1 - initial level of risk - prior to implementing mitigation 2- residual risk - after mitigation *May include in SOW |
|
in Phase A - what is the most important step?? |
Step 11 - develop SOarchW & get approvals |
|
Define Phase A - Step 11 - develop SOarchW & get approvals |
- Assess work products required (make sure metrics built in, make sure - ? - new work products? - work products to changed? - which domains to develop? (BDAT), views and level of detail - assess resource requirements - communications plan - review and agree w/ sponsors; get approval |
|
Define Phase B - Step 1 - select reference models/viewpoints/tools |
-select reference models/viewpoints/tools from the repository - select relevant viewpoint - ID tools for modeling/analyzing/documenting Step 1.1 - determine modeling process |
|
What are the different substeps for Phase B- Step 1.... select reference modes/VPs/tools |
Step 1.1 - determine modeling process Step 1.2 - identify service granularity levels, boundaries Step 1.3 Id catalogs Step 1.4 Id matrices Step 1.5 - Id diagrams Step 1.6 - Id which type of requirements to collect |
|
What are the business Service granularity lkeveles |
-micro-level functions -boundaries no governance -services- boundaries and governance -macro-functions - no boundaries but governance |
|
Define requirements from a TOGAF POV? |
what does the target arch need to do to satisfy stakeholder concerns |
|
Describe Phase B- Step 2 - Develop Baseline Bus Arch |
baseline existing business architecture using models from step 1 to defined new baseline content |
|
Describe Phase B- Step 3 - Develop TARGET Bus Arch |
figure out level of detail and make sure the future arch supports the arch vision use models as appropriate |
|
What is Phase B - Step 4 - gap analysis |
gap analysis of the business arch and make sure it supports principles/concerns/constraints you also want to test models for completeness against the requirements |
|
What is included in Phase B - Step 5 - candidate roadmap? |
-extract differences from gap and make those features of the target -need to prioritize activities |
|
What is included in Phase B - Step 6 - resolve impacts |
-understand wider impact even outside scope - are there recent changes outside that need to be accounted for? - is there an opportunity to share outside? - is there impact on in-flight work? |
|
What is in Phase B - Step 7 - stakeholder review |
check and see if architecture conforms to the original SOaW then present to stakeholders |
|
What is in Phase B - Step 9 - finalize bus arch |
- check repository if there are standards for new ABB -complete documentation and cross-check against the bus goals - finalize products to date |
|
What is in Phase B - Step 10 - Create Arch def doc |
- document business block rationale - create bus arch section of arch defn doc including --- business footprint ---description of bus functions ---mgmt footprint ---standards/rules/guidelines ---skills matrix and JDs |
|
Describe Phase C - Data Arch & Info Systems Arch |
Develop Baseline Data Arch Same 9 steps as BArch 1- reference models/VPs/Tools |
|
What is involved in Data modeling? (Phase c- Step 1) |
1.1 - Determining overall modeling process 1.2 - identify catalogs of data building blocks (track from apps to business function to entities and create the data catalog) 1.3 - Identify matrices 1.4 - ID data diagrams (conceptual, logical, security ) 1.5 - Data requirements |
|
NOTE: data arch & requirements are inputs to appl arch and so it comes first in phase c |
NOTE: data arch & requirements are inputs to appl arch and so it comes first in phase c |
|
Describe Phase C - Step 2 (Data)- Baseline data arch |
- Baseline existing to the level needed; much could carry forward - use inputs from Step 1 |
|
Describe Phase C - Step 3 (Data)- Target arch |
should support the arch vision identify building blocks and use inputs from Step 1 |
|
Describe Phase C - Step 4 (Data)- Define Gaps |
-Validate target and baseline including different views against one another -make sure support principles/objectives - test models for completeness -ID the gaps |
|
Explain Phase C - Step 5 (Data)- Candidate Roadmap |
extract exact differences from the gap analysis make them into features use roadmap to prioritize activities use to feed opportunities and solutions |
|
Explain Phase C - Step 6 (Data)- Resolve impacts |
- understand wider implications - are there outside changes that need to be accounted for -opportunity to share work with others outside our scope? |
|
Explain Phase C - Step 7 (Data) - stakeholder review |
- make sure the data arch conforms to original purpose and the SOarchW - present to stakeholders |
|
Explain Phase C - Step 8 (Data) - finalize arch |
-check repository for standards for new building blocks -complete documents -cross check against business requirements -finalize work products |
|
Explain Phase C - Step 9 (Data) - arch defn doc |
- document rationale - prep data arch section of arch dfn doc ---business data model ---logical data model ---data management process -- data entity/business function matrix |
|
Explain Phase C - Step 1 (App Arch) - select ref models/VP/Tools |
-select reference models/viewpoints/tools from the repository - select relevant viewpoint - ID tools for modeling/analyzing/documenting |
|
Describe the modeling steps for Phase C - Step 1 (app arch) |
1.1 - Determining overall modeling process 1.2 - identify catalogs of building blocks NOTE: hierarchies of catalogs: logical --> Physical --> service 1.3 - Identify matrices 1.4 - ID diagrams (conceptual, logical, security ) 1.5 - define the types of app arch requirements needed (impacts data and tech arch) |
|
explain step 2 of Phase C app arch - baseline app arch |
- develop baseline app arch description - may include existing assets that will carry over - model step 1 models as necessary |
|
explain step 3 of Phase C app arch - define target arch |
-describe target arch v1.0 -make sure it supports the vision and target business and data arch -leverage building blocks where you can user models from Step 1 NOTE: APP And DATA are done side by side |
|
What's involved in Step 4 - gap analysis of app arch phase C? |
-Validate architectures including different views -validate against principles/objectives/constraints -test models for completeness -ID gaps between target and baseline arch |
|
Explain Phase C - app arch - step 5 - roadmap |
-extract differences from gap and make those features of the target-need to prioritize activities |
|
Phase C (app arch) - step 6 includes what steps to resolve impacts |
-understand implications -check if impacts outside your scope -outside changes that impact your work? -identify opportunities to share -check other projects and know impacts |
|
Explain Phase c - step 7 for app arch - formal review |
- make sure conform to SOarchW - business or data arch need to change? |
|
Explain Phase c - step 8 for app arch - finalize arch |
-check repository for standards for new building blocks -complete documentation -cross check with business requirements |
|
Explain Phase c - step 9 for app arch - arch defn doc |
document rationale prep app arch section of arch dfn doc |
|
Explain Phase D - Technical Architecture... which letter in the BDAT acronym? |
T in the BDAT Develop baseline tech arch v1.0 Develop target tech arch v1.0 identify gaps between baseline and target |
|
What is step 1 of Phase D - Technical arch? |
Select reference Models, viewpoints and tools |
|
Specific to step 1 of Phase D, what are the sub steps? |
1.1 determine modeling process 1.2 identify catalogs of tech building blocks 1.3 identity the required matrix: the application/technology matrix 1.4 ID diagrams (topology) 1.5 ID types of requirements to collect 1.6 select services needed |
|
Explain Phase D Step 2.... develop baseline tech arch |
describe the existing tech arch pull out existing building blocks much should exist... this is "physical stuff" that exists |
|
Explain Phase D Step 3.... develop target tech arch |
describe the target tech arch make sure it supports the arch vision and the business/data arch identify relevant building block ( if pre-existing) use models from step 1 to develop the new tech arch |
|
Explain Phase D Step 4.... tech arch GAP analysis |
-look at baseline and compare to target state -compare using principles, objectives, and constraints -test for completeness against requirements |
|
Explain Phase D Step 5.... build candidate roadmap |
extract key differences from teh gap analysis and the features needed shoudl be on the roadmap a tech roadway is needed to prioritize activities over the coming phases |
|
Explain Phase D Step 6.... resolve impacts for the tech arch |
-evaluate the wider implications -check with architectures outside direct scope -are there any additional outside changes that need to be considered -can this work be shared? -will this impact others? |
|
Explain Phase D Step 7... stakeholder review of the tech arch |
-make sure the tech arch conforms to the original purpose of teh project and the SOarchW |
|
Explain Phase D Step 8 , Finalize Tech Arch |
-select standards for the tech arch building blocks -complete the documentation is finished -cross check everything against business requirements -final work products |
|
what is involved in Phase D Tech Arch Step 9 - create arch defn document |
- need to document the rationale - prep the tech arch section of the comprehensive arch defn doc |
|
Phase E is called what? |
the opportunities and solutions step |
|
What is the purpose of Phase E? |
to get you to the first full a complete version of the arch roadmap (v1. |
|
What is included in step 1 of Phase E - confirm corporate change |
essentially, how can the architecture best be implemented to take advantage of the corporate culture... are they slow and need incremental rollout? -Execute the business readiness transformation analysis -then fill out the implementation factor assessment and deduction matrix |
|
What is the focus of Phase E Step 2 - Business Constraint? |
this is the step where you identify business drivers that could constrain rollout? think about season rushes, budget issues and so on |
|
What is the focus of Phase E Step 3 - review and consolidate gap analysis results |
-create the gap/solution/dependency matrix -identify potential solution building blocks and arch building blocks - |
|
What are the activities during Phase E Step 4 - consolidate requirements |
-identify the minimal requirements that can lead to most effective target architecture -figure out if the solution you are solving can be used by different LOBs |
|
Phase E Step 5 for the opportunity/solution phase is what focus area? |
-consolidate and reconcile Interoperability requirements -identify any conflicts via two approaches: new building block or modify existing |
|
What is included in Phase e Step 6 of the opportunity/solution phase: refine/validate dependencies? |
identifying tasks that directly impact you such as a mandatory OS upgrade |
|
What is the complete list of steps for Phase E (there are 11!!) |
1 2 3 4 5 - 6 - refine and validate dependencies 7 - confirm readiness |
|
What is included in Phase E Step 7 - confirm readiness? |
review the transformation readiness assessment and figure out if it impacts the roadmap... if so, you need a risk mitigation plan |
|
What is included in Phase E Step 8 - formulate implementation/migration strategy |
3 implementation approaches: greenfield, revolutionary, evolutionary revolutionary -- replace old with new (big bang) 3 mitigation approaches: a. quick wins b. achievable targets c. value chain approach |
|
what are 3 implementation/migration mitigation strategies in Phase e? |
3 mitigation approaches: a. quick wins - what is the easiest item to deploy with most benefitb. achievable targetsc. value chain approach |
|
During Phase E - step 9 - what outputs are defined? |
Work packages, that is , groups of activities to do this, fill in th esolution column of the consolidated gaps/solutions/dependencies matrix then classify each system: mainstream, contain, replace |
|
What are the classifications you apply when identifying work packages in Phase E? |
mainstream - part of the target future contain - expect to replace in 3 years +/- replace - new work package will replace old |
|
Phase 3 - Step 10: Identify transition architectures |
schedule work packages figure out if there is an incremental approach... and if so, you will have transitional architectures (that is it brings an incremental business value) an implement the easier activities first (the quick wins)
|
|
what is included in Phase 3 - Step 11 - create arch Roadmap and implementation/migration plan |
consolidate workpackages and transition architectures into the roadmap V0.1 layout timelines fro baseline to Target make sure each transition architecture has a clear set of outcomes. Make sure you are always working to realize the roadmap. |
|
What is the name of Phase F? |
Migration Planning |
|
What are the key aspects of migration planning ? |
Finalizing the arch road map and implementation and migration plan Ensuing plan is coordinated with the enterprise's change management approach ensure business value of the approach is understood transition from development of arch to implementing |
|
What is step 1 of Phase f - Migration Planning? |
confirm management f/w interactions... this means to make sure it fits well with the management approach (pm plan) -business plan, ent arch f/w, ppm, ops management, |
|
Explain Phase F - Step 2 - assign business value |
establish and assign business values to work packages address issues such as (1) performance evaluation (2) ROI (3) business value, (4) CSF - critical success factors, (%) measures of effectiveness, (6) strategic fit Assign risk to projects |
|
Explain Phase f - Step 3 - estimate resource requirements (costs & timing) |
determine resources, timing and then identify the costs... for costs, there are two types: capital cost and ongoing operational cost |
|
describe Phase f Step 4 - Prioritize migration projects |
prioritize projects with most business value and low cost (quick win) review the risks and ensure they are mitigated (to the extent possible) get stakeholder agreement review the risk and revise; residual risk |
|
What is residual risk? |
once you have executed risk mitigation, there is often left over risk... called residual risk |
|
Describe Phase f - Step 5 - confirm arch roadmap |
update architecture roadmap including transition architecture create transition architecture state evolution table... if the approach ever changes, update the arch definition document |
|
What is included in Phase f Step 6 - generate imp&migration plan |
generate the completed imp and migration plan capture external dependencies |
|
For Phase f - migration, what are all teh steps? |
6- generate implementation & migration plan 7 - complete arch dev |
|
Describe Phase f - Step 7 - complete arch dev |
complete the arch dev and transition to implementation identify lessons learned revisit phase B if required for deeper details |
|
Phase G is concerned with what? |
Implementation governance |
|
What are the key activities of Phase G |
-ensure conformance with target arch -execute governance duties -handle change requested -update baseline arch as changes implemented |
|
What is included in Phase G Step 1 - confirm scope and priorities? |
produce recommendations for deployment identify ea priorities for dev team identify deployment issues identify building blocks that need replace,ment |
|
What activities are involved in Phase G Step 2 - identify development resources |
identify system dev methods (SDM) ensure system dev method enable feedback to arch team on design |
|
What are all the steps in Phase G - Execute implementation governance |
1 2 3 - guid3 development |
|
How do you execute step 3 of phase g - guide development |
1 - formulate project recommendations 2 - create arch contract/obtain signature 3 - update the enterprise continuum 4 - guide service development 5 - implementation plan |
|
Describe Phase G step 4 - compliance reviews |
review ongoing implementation governance and arch compliance conduct post dev reviews close out development |
|
Describe Phase G Step 5 - Implement business and IT operations |
This is where you actualy carry out the final aspects of the deployment and publish baseline |
|
Describe Phase G step 6 - Post-Imp Review |
Conduct a review to make sure the implementation was executed as expected then publish a review Finally, you'll close the project out after talking to the stakeholders. |
|
So what is Phase H all about?? |
after the project is live, it is the last phase where change management of the architecture is conducted.... this is where you wait for changes that will kick off new ADM cycles You also monitor |
|
What are the key items includes in Phase H Step 1 - Establish Value Realization Process |
- influence business projects to exploit the EA for value realization (push folks to use the enterprise assets) |
|
What are the Steps in Phase H |
1- establish value realization process 2 - deploy monitoring tools 3 - manage risks 4 -analyse change management 5 - develop change requirements 6 - manage the governance process 7 - activate process to implement change! |
|
During Phase H Step 2 - Deploy Monitoring tools, what are some of the different dimensions that you will monitor? |
-tech changes -business changes -business value -arch capability maturity -asset management -QoS |
|
There are many different ways and times that you address risk in TOGAF, in Phase H Step 3, you will _______ risk |
Manage risk and provide recommendations for IT Strategy |
|
Phase H Step 4 includes analyzing for change management , what type of activities will you do? |
analyze performance EA performance reviews assess change requests take on any gap analysis needed make sure governance is being followed |
|
Phase H Step 5 is focused on developing change requirements if you are not meeting performance targets |
the steps are in the title... if you are not meeting targets, then you make recommendations to change |
|
Phase H Step 6 is all about the governance process.... who is involved? |
the architecture review board |
|
Phase H has a final step, step 7, that include activating the process to implement change... what's included? |
-producing new requests for work -ensuring changes that get implemented are documented in the arch repository |
|
What is at the center of the ADM cycle? |
requirements management |
|
How does Req Management differ from other phases? |
Requirements management is more like a centralized hub instead of a phase w/ separate steps... it provides the process used by each of the outer phases |
|
For requirements management, what is step 1? |
Identify/document requirements |
|
What are the steps 1-5 of requirements management and where does it actually happen? |
1 - identify requirements (ADM) 2 - prioritize requirements (RM) 3 - monitor baseline requirements (RM) 4 - identify changed requirements (ADM) 5 - identify changed requirements (RM) |
|
What are the steps 6 - 10 of requirements management and where does it actually happen? |
6 - assess impact of the requirements (ADM) 7 - implement requirements for phase H (ADM) 8 - update requirements repository (RM) 9 - implement the change in the current ADM phase (ADM) 10 - assess and revise gap analysis of PRIOR phases |