ROLE CASE Togaf Project togaf action

Aquire for a company Extending mother company Vision & Approval

Lead Integrartion
43 Montoring system satellite monotoring system based on DDD
Architct outdated to include aquired one presented

No centralized entry for

44 Chief ARCHITICT reliable global online portal CIO setup team
customer requests

Design an enhancement of
business Leverage on customer data the current enterprise data
intelligence to gain source of analytic
45 warehousing system to
subject matter data which increase support change in business
expert company revenue model

Mssive replacement for Replace REP using green

46 Chief architict supply chain to reduce field appreach
production cost
 Process imporovemnt by Architecture Vision
47 Lead Arcitict replacing outdated MRB2 Produced
with ERP

chief architiect Reducing It Costs

48

consultant to lead Consolidated ERP system A phased approach is needed

49 to implement target
archtict architicture
 consultant to lead Consolidated ERP system A phased approach is needed
49 to implement target
archtict architicture
 togaf Ans
TOGAF PART/question
phase wer

C
Recommend best approach to design
D full architecture and present it to the
board D
A

Vision present architecture vision B

Phase C determine suitable artifact for our case C

D

Architict To write architicture design and

ure B
development contract
contract C
D
 D

update update IT architecture principals

pricipals

A
C

examining opportunities & Solutions

E before presenting to the board

A
after E steps to prepare final implementation
and migation plan
after E steps to prepare final implementation
and migation plan
D
B
 claim

follow togaf sequence

missing roadmap impact assessment

Sequence phaese,develop target before base

mention implementation & migration plan snd then mention GAP

follow all phase A Steps Stakeholder map, evaluation business

cabapility assessment transformation readiness, apply business
scenario technique,
missing : stakeholder map,bussiness capability assessment,
transformation readiness assessment
missing hagat kteer
in vision we don't perform detailed view nor architicture defintiin
document.

system/data matrix identify relation between data entitles and

applications, Data life cycle diagram identify common data
requirement.apllications that operates on data entities includes data
warehouse
Like A except Data life cycle
mention data/matrix with wrong function

Role/system catalogue identify relation between application/business

role, no artifact called data use case diagram .

follow architicture contract content except ARCHiticure development

mangemnts process and roles
Same as A but include business arch defenition which is not in
architucture contract
missing some output from contracts
dosn'tcontain any of arch contract and contains gap and impact whcigh
are not included in contra ct
Information Management is Everybody's business:address Information
mangement concern/IT Responsibility:address responsibility/Data
Trastee:address security requied in consolodation projects/Technology
Independence:requird in consolodation projects/Responsive Change
Management:address time to change

Business Continuity addressess reliability/Service-Orientation

addressess interoperability and location transparency./Data is
shared,secured address securedResponsive Change
Management:address time to change

no addressing for information mangement and time

to change concerns
No principal is called data is normalized

Follows phase E steps:1. Determine/confirm key corporate change

attributes ---
2. Determine business constraints for implementation
3. Review and consolidate Gap Analysis results from Phases B to D
4. Review IT requirements from a functional perspective
5. Consolidate and reconcile interoperability requirements
6. Refine and validate dependencies
7. Confirm readiness and risk for business transformation
8. Formulate high-level Implementation and Migration Strategy
9. Identify and group major work packages
10. Identify Transition Architectures
11. Create portfolio and project charters and update the architectures

Missing:. Determine/confirm key corporate change attributes

2. Determine business constraints for implementation
Confirm readiness and risk for business transformation
8. Formulate high-level Implementation and Migration Strategy

Missing:. Determine/confirm key corporate change attributes

2. Determine business constraints for implementation
3. Review and consolidate Gap Analysis results from Phases B to D.
8. Formulate high-level Implementation and Migration Strategy
11. Create portfolio and project charters and update the architectures

Contains features n Migration plan (Cost benefit/risk) lessons learned

mentioned integration to other frameworks(which has been mentioend

explictly in the case).
didn’t mention integration with other frameworks
what is configuration control???governenace model is reviewed not
produced
it is phase G
 ROLE CASE Togaf Project togaf action

replacing current enterprise develop a comprehensive pln

Lead enterprise planning and scheduling for transformation to team +Request for
1 architectue planning with a common achieve desired outsomes architicture work
centralized ERP and benifites

Consultant to a Customer service system & Developing

2 Problem in customer service
chief architict Green initiative buissiness scenario

The Corporate Board is

concerned that the new ERP
system must be able to manage
and safeguard customer
3 Chief Architect. information in a ERP system
manner that meets or exceeds
the legal requirements of the
countries in which the company
operates.

an architecture project was

completed that defined a
The Chief Engineer, standard approach for
sponsor of the activity, has controlling the Automated An Architecture
4 Lead Archtict expressed concern that a Test System that is used at Contract was
uniform process be employed at each plant to perform final developed
each site to ensure consistency. quality assurance tests on
each completed blade
assembly.

completed a
the researchers have been Business
resisting the change because of Transformation
concerns about Readiness
5 Lead Architict
 concerns about Readiness
5 Lead Architict safeguarding individually Assessment in
identifiable information about Phase A
the subjects who were (Architecture
participating in the trials Vision).

develop strong directed

Florians international operations team in each location, define
6 Lead Architict are subject to various legal and new business models
regulatory requirements. profitable and green

consolidate and reduce

redundant procurement company prefers to
processes and systems implement existing package no particularly
7 higher volume discounts and applications from systems useful architectural
lower related IT support costs by vendors with little assets
instituting a preferred supplier customization.
program.
 togaf Ans
TOGAF PART/question
phase wer

Vision Update Principals

B

A
D

B
advise the Chief Architect on the best
ways to approach to the C
Vision implementation planning activities for
this significant A
business transformation.

recommend the approach to take in

Prelimin the Preliminary Phase to ensure that
ary the Corporate Board's concern is D
addressed

C
B

D
You have been asked to recommend
the best approach to adopt to address
G the Chief Engineer's concern.
(COTRACT)
C
B
A

B
You have been asked to recommend
E how this situation be managed in the
implementation planning phases.
 You have been asked to recommend
E how this situation be managed in the C
implementation planning phases. D
A

A
You have been asked to recommend an
approach that would enable the B
B development of an architecture that
addresses the needs of all these parties D
C

B-to- F
Architec
ture
Defeniti
on cycle

\
\
 claim

Bussiness contiunty = relability /Data is shared +Secured = Security/

Maximize benefit to the organization = impove efficiency of
applications (from the case)

lacks data is shared and amximize benefite to the organization

lacks bussiness continuity and maximize benefit to thre enterprise

technology independace contradicting with the case.

we should use capability based planning as we are in initiative that

providing bussiness outcome and it is a horizontal activity,
it is horizontal activity ,no apprach is callled developemnt lift cycle in
TOGAF
it shouldn't go through conventianl planning
capability based plannig could be used in provate sector , it shouldn't
go through conventianl planning

evaluate the requirement of the board’s concern In term of regulatory,

update and publish the security policy, security team to ensure security
consideration are included, assessment of security requirement for the
company business and their suppliers.

Missing the security policy publishing and assessment of security

policy on the company business and their suppliers.
it focuses on allocating security architecture team only missing
updating and publishing the policy and assessing the implication of it
on the company business and their suppliers
wrong security is not a separate architecture projec

1- the only that mention each site (concern).

2- The onl ythat mention contract components.
3- the only that mention complaince .
4- mention deviation mangement

Only mention deviation mangement.

mention deviation mangement wrong.
we can make change request not re quest for architicture work.

a sitiuation that arise makes them return to phase A and risk

mitigation
RISK MITIGATION BUT IN PHASE E

NO overall solution strategy. No risk mitigation mentioned

develop model ,model compaiance with local regulations, follow

sequence of modeling
missing complaince with regulations
missing modeling sequence
didn't mention modeing

relation between actors and business process

need from basline applications and actors use this applications
relation between bussiness process and applications
lifecycle of the request,interopearbility,data sharing
6 YY
P6P
HH
Q NO PHASE Answer

1 Preliminary C

implementa CapabilityBased
2 B
tion planning Planning.

Adapting ADM
3 Preliminary A
Security

4 G architicture contract D

5 E Risk mitigation C

Stackholder
6 Vision D
concerns
7 content metamodel B

8 E Techniques C

Architecture
9 G D
complaiance

10 A Scope A

11 E Work packages A

course of action to
12 after Vision complete the B
project

13 preliminary Principles D
14 F F steps B

15 artifacts C

after Stackholder
16 D
preliminary concerns

17 D architicture contract A

Adapting ADM
18 Preliminary C
Security
19 After Vision ADM iteation A

E(prior to
approval of
20 detailed assessing risk C
implentation
plan )

21 Preliminary Principals B

business
transformation
22 Vision C
readiness
assessment

23 Extention of
Priliminary content A
metamodel

tacke stakholder
24 Vsion C
concrns

25 After Vision ADM iteation B

NOT Stackholder
26 C
determined concerns
27 Prliminary Principles D

28 prilimiinary Principals C

29 Security B

30 begin in B steps in B_D C

31 E steps of E D
32 Principals D

33 content metamodel A

34 Vision Vision steps A

35 Priliminary Priliminary steps C

Befor
development Risk assessement
36 B
of arciticture
project
 Compliance review
37 D
steps

38 F F steps B

39 E E steps C

40 G B

41 content metamodel A

Stackholder
42 Vision D
concerns
43 Vision Steps from B TO D C

44 Vision Steps of phase A A

45 content metamodel A

46 architicture contract A

47 Principals B
48 E E steps D

49 F F steps C

after Stackholder
50 A
priliminary concerns

E(prior to
approval of
51 detailed assessing risk D
implentation
plan )

52 D architicture contract A
53 After Vision ADM iteation B

54 content metamodel C

55 Principals B

Security In
56 D
priliminary

57 EA TEAM SKILLS C
58 Priliminary Content extension A

59

business
transformation
60 Vision C
readiness
assessment

61 E Work packages B
 Rational from TOGAF
minimize waste and improve the efficiency of all of its production operations = Maximize benefit to the enterprise
Business continuity = reliability data is secured = data is shared, data is secured centeralized application= common
use applications.

outcome= capability based planning / in the case he needs horizonal green capability
in the case : improving overall customer service within each business unit = in the answe: It is crucial to gain
business unit support and cooperation to achieve the broader business outcomes which will benefit all

The security policy should be examined to find relevant sections, and updated if necessary. Architecture constraints
established in the security policy must be communicated to the other members of the architecture team.
A written security policy for the organization must be in place, and there should be regular notification and
education established for employees. ISO/IEC 17799: 2005 is a good place to start the for mation of a security
policy, and can be used to assess the security readiness of an organization. Without a written and published
security policy, enforcement is difficult
Architecture constraints established in the security policy must be communicated to the other members of the
architecture team.

Phase G establishes the connection between architecture and implementation organization,

through the Architecture Contract.
Project details are developed, including:
■ Name, descr iption, and objectives/■ Scope, deliverables, and constraints
■ Measures of efectiveness/■ Acceptance criter ia/■ Risks and issues
The steps in Phase G are as follows:
■ Confir m scope and prior ities for deployment with development management ■ Identify deployment resources
and skills
■ Guide development of solutions deployment
■ Perform enterprise architecture compliance reviews
■ Implement business and IT operations
■ Perfor m post-implementation review and close the implementation

Confirm Readiness and Risk for Business Transformation

Review the findings of the Business Transfor mation Readiness Assessment previously conducted in Phase A and
determine their impact on the Architecture Roadmap and the Implementation and Migration Strategy. It is impor
tant to identify, classify, and mitigate risks
associated with the transfor mation efor t. Risks should be documented in the Consolidated Gaps, Solutions, and
Dependencies matrix.

Science I need to analyse stackholders with their concerns I begin with stackholder map
1. What groups of people should be involved in procurement-related business processes? = Business
Service/Function catalog
2. What current applications do those groups use? App Organization matrix
3. Which procurement-related business processes are supported by zero, one, or many existing applications?
4. What are the overall lifetimes of the Request for Proposal and Purchase Order business objects? = Product
Lifecycle diagrams
5. What non-procurement applications will need to be integrated with any new procurement applications?
Application Communication diagrams and an Application Interaction matrix
6. What data will need to be shared? = Data Entity/Business Function matrix

lists the steps (techniques) to construct initial implementation and migration plan
The steps in Phase E are as follows:
n Deter mine/confirm m key cor porate change attributes
n Deter mine business constraints for implementation
n Review and consolidate gap analysis results from Phases B to D
n Review consolidated requirements across related business functions
n Consolidate and reconcile interoperability requirements
n Refine and validate dependencies)
n Confirm readiness and risk for business transform mation
n Formulate Implementation and Migration Strategy
n Identify and group major wor k packages
n Identify Transition Architectures
n Create the Architecture Roadmap & Implementation and Migration Plan

Non-conformant: Any of the above in which some features in the architecture specification are implemented not in
accordance with the specification

appropriate and useful technique to discover and document business requirements, and to
ar ticulate an Architecture Vision that responds to those requirements

13.4.9 Identify and Group Major Work Packages

Key stakeholders, planners, and the enterpr ise architects should assess the missing business capabilities identified
in the Architecture Vision and Target Architecture.
Using the Consolidated Gaps, Solutions, and Dependencies matrix together with the Implementation Factor
ssessment and Deduction matrix, logically group the var ious activities into wor k packages.

summerize togaf steps after vision

Pr inciples are general rules and guidelines, intended to be enduring and seldom amended, that infor m and
support the way in which an organization sets about fulfilling its mission. Architecture principles are typically
developed by the enterpr ise architects, in conjunction with the key stakeholders, and are approved by the
Architecture Board.
Confirm management framework interactions for Implementation and Migration Plan
n Assign a business value to each work package
n Estimate resource requirements, project timings, and availability/delivery vehicle
n Prioritize the migration projects through the conduct of a cost/benefit assessment and risk
validation
n Confirm Architecture Roadmap and update Architecture Definition Document
n Complete the Implementation and Migration Plan
n Complete the architecture development cycle and document lessons learned

science there is no architictue exists we neglect points that begins with baseline / concern 1 relationship between
business process and applications which exists in data entity/business function matrix and application data matrix
dtat will be shared it needs a baseline artifact for data which is data entity/data component entity

The purpose of the Stakeholder Map matrix is to identify the stakeholders for the architecture
engagement, their influence over the engagement, and their key questions, issues, or concer ns
that must be addressed by the architecture framework.

Phase G establishes the connection between architecture and implementation organization,

through the Architecture Contract.
Project details are developed, including:
■ Name, descr iption, and objectives/■ Scope, deliverables, and constraints
■ Measures of efectiveness/■ Acceptance criter ia/■ Risks and issues
The steps in Phase G are as follows:
■ Confir m scope and prior ities for deployment with development management
■ Identify deployment resources and skills
■ Guide development of solutions deployment
■ Perfor m enter prise architecture compliance reviews
■ Implement business and IT operations
■ Perfor m post-implementation review and close the implementation

Define and document applicable regulatory and security policy requirements

The framework and principles rarely change, and so the security implications called out in the objectives of this
phase should be fair lee straightforward. A written security policy for the organization must be in place, and there
should be regular notification and education established for employees. ISO/IEC 17799: 2005 is a good place to
start the for mation of a security policy, and can be used to assess the security readiness of an organization.
Without a written and published security policy, enforcement is difficult. Security policies refer to many aspects of
secur ity for the organization — such as physical premises security — that are remotely related to secur ity of
systems and applications. The security policy should be examined to find relevant sections, and updated if
necessary. Architecture constraints established in the security policy must be communicated to the other members
of the architecture team.
In a similar fashion, there may be regulator y requirements that specify obligations the system must fulfil or actions
that must be taken. Whether the system will be subject to regulation will depend upon the functionality of the
system and the data collected or maintained. In addition, the jurisdiction where the system or service is deployed,
where the users reside, or under which the deploying entity is chartered or incorporated will infor m this decision.
It may be wise to obtain legal counsel regarding these obligations at the outset of activities.
Architectural Definition of Bounded Change Initiatives
Architecture Development (Target First)
Transition Planning
Focus on elaborating the target to meet a previously defined an agreed vision, scope, or set of constraints. Use
the target as a basis for analysis to avoid per petuation of baseline, suboptimal architectures

Review the findings of the Business Transfor mation Readiness Assessment previously
conducted in Phase A and determine their impact on the Architecture Roadmap and the
Implementation and Migration Strategy. It is impor tant to identify, classify, and mitigate risks
associated with the transfor mation efor t. Risks should be documented in the Consolidated
Gaps, Solutions, and Dependencies matrix.

Bussiness contiunty = relability /Data is shared +Secured = Security/ Maximize benefit to the organization = impove
efficiency of applications (from the case)

A Business Transfor mation Readiness Assessment can be used to evaluate and quantify the organization’s
readiness to undergo a change. This assessment is based upon the determination and analysis/rating of a series of
readiness factors, as descr ibed in Chapter 30. The results of the readiness assessment should be added to the
Capability Assessment (see Part IV, Section 36.2.10). These results are then used to shape the scope of the
architecture, to
identify activities required within the architecture project, and to identify risk areas to be addressed.

Governance Extensions:Extension to support in-depth, operational governance/

Services Extensions: Extension to support definition of discrete business and application services
Process Modeling Extensions : Extension to support process modeling
Data Extensions:Extension to support data modeling
Infrastructure Consolidation Extensions : Extension to support consolidation of applications and technology across
locations
Motivation Extensions : Extension to support linkage of drivers, goals, and objectives to organizations and services
All extension modules are optional and should be selected during the Preliminary Phase of the
architecture development to meet the needs of the organization

Architectural Definition of Bounded Change Initiatives

Architecture Development (Target First)
Transition Planning
Focus on elaborating the target to meet a previously defined an agreed vision, scope, or set of constraints. Use
the target as a basis for analysis to avoid per petuation of baseline, suboptimal architectures

The purpose of the Stakeholder Map matrix is to identify the stakeholders for the architecture
engagement, their influence over the engagement, and their key questions, issues, or concer ns
that must be addressed by the architecture framework.
Architecture principles are typically developed by the enterpr ise architects, in conjunction with
the key stakeholders, and are approved by the Architecture Board.
Architecture principles will be infor med by principles at the enterpr ise level, if they exist.
Architecture principles must be clearly traceable and clearly articulated to guide decisionmaking.
They are chosen so as to ensure alignment of the architecture and implementation of
the Target Architecture with business strategies and visions.
Specifically, the development of architecture principles is typically influenced by the following:
n Enterprise mission and plans: the mission, plans, and organizational infrastr ucture of the
enter prise.
n Enterprise strategic initiatives: the character istics of the enterpr ise — its strengths,
weaknesses, oppor tunities, and threats — and its current enterpr ise-wide initiatives (such
as process improvement and quality management).
n External constraints: mar ket factors (time-to-market imperatives, customer expectations,
etc.); existing and potential legislation.
n Current systems and technology: the set of infor mation resources deployed within the
enter prise, including systems documentation, equipment inventor ies, networ k configuration
diagrams, policies, and procedures.
n Emerging industry trends: predictions about economic, political, technical, and market
factors that influence the enterpr ise environment.

Bussiness contiunty = relability /Data is shared +Secured = Security/ Maximize benefit to the organization = impove
efficiency of applications (from the case)

Secur ity concer ns are pervasive throughout the architecture domains and in all phases of the architecture
development. Security is called out separately because it is infrastr ucture that is rarely visible to the business
function.
All groups of stakeholders in the enterpr ise will have secur ity concer ns and it is desirable to
br ing a secur ity architect into the project as early as possible. Throughout the phases of the
ADM, guidance will be ofered on security-specific infor mation which should be gathered, steps
which should be taken, and artifacts which should be created. Architecture decisions related to
secur ity should be traceable to business and policy decisions and their risk management.

no assessts and target is not clear so traditional baseline bottom up approach

The steps in Phase E are as follows:

Deter mine/confirm key corporate change attributes
Deter mine business constraints for implementation
Review and consolidate gap analysis results from Phases B to D
Review consolidated requirements across related business functions
Consolidate and reconcile interoperability requirements
Refine and validate dependencies
Confirm readiness and risk for business transformation
Formulate Implementation and Migration planning
Identify and group major work packages
Identify transition Architectures
Creat the architecture roadmap & implementation and migration plan.
Quality of data :Data Trustee: Statement: Each data element has a trustee accountable for data quality.
Maintain without disruption : business continuty : Statement: Enterprise operations are maintained in spite of
system interruptions.
without any unforseen delays :Responsive Change Management:Changes to the enterpr ise infor mation
environment are implemented in a timely manner.Implications: We have to develop processes for managing and
implementing change that do not create delays.
Technology Independence : Statement: Applications are independent of specific technology choices and therefore
can operate on a var iety of technology platfor ms.

1- They want to analyze the roles of the top management for each revenue earning service = means role and
business service =Actor/Role Matrix
2-many of the HR related critical Search application component have become extremely slow. This needs to be
diagnosed and rectified. = System/Functions Matrix
3- there is no proper tracking of revenue from retail store component products over time. = Data Entity/Business
Function Matrix
4- There has also been a lot of unauthorized or unwanted access to many of the critical information. Hence the
mode of access needs to be strengthened and made much more secure. = Data Security Diagram
5- the new launches and the progress of each of the launches over time. = Technology Portfolio Catalog

#VALUE!

The steps within the Preliminary Phase are as follows:

n Scope the enterpr ise organizations impacted (see Section 6.4.1)
n Confir m governance and support frameworks (see Section 6.4.2)
n Define and establish enterpr ise architecture team and organization (see Section 6.4.3)
n Identify and establish architecture principles (see Section 6.4.4)
n Tailor TOGAF and, if any, other selected Architecture Frameworks (see Section 6.4.5)
n Implement architecture tools (

There will always be risk with any architecture/business transfor mation efor t. It is important to identify, classify,
and mitigate these risks before starting so that they can be tracked throughout the transfor mation efor t.
Mitigation is an ongoing efor t and often the risk triggers may be outside the scope of the transfor mation planners
(e.g., merger, acquisition) so planners must monitor the transfor mation context constantly.
It is also important to note that the enterpr ise architect may identify the risks and mitigate certain ones, but it is
within the governance framework that risks have to be first accepted and then managed.
The risk identification and mitigation assessment wor ksheets are maintained as governance
ar tifacts and are kept up-to-date in Phase G (Implementation Governance) where risk monitoring
is conducted.
1-Request architecture review,2-Identify responsible part of Architecture Review ,3-Identify Lead Enterpr ise
Architecture , 4 Deter mine scope of review,5- Tailor checklists.,6shedule Architecture Review Meeting
7 Inter view project principals,8 Analyze completed checklists,9 Prepare Architecture Compliance review repor t
10 Present review findings 11 Accept review and sign of 12 Send assessment Lead Enter prise Architect
repor t/summar

The steps in Phase F are as follows:

n Confirm management framework interactions for Implementation and Migration Plan
n Assign a business value to each work package
n Estimate resource requirements, project timings, and availability/delivery vehicle (
n Prioritize the migration projects through the conduct of a cost/benefit assessment and risk validation
n Confir m Architecture Roadmap and update Architecture Definition Document
n Complete the Implementation and Migration Plan
n Complete the architecture development cycle and document lessons learned

The steps in Phase E are as follows:

Deter mine/confirm key corporate change attributes
Deter mine business constraints for implementation
Review and consolidate gap analysis results from Phases B to D
Review consolidated requirements across related business functions
Consolidate and reconcile interoperability requirements
Refine and validate dependencies
Confirm readiness and risk for business transformation
Formulate Implementation and Migration planning
Identify and group major work packages
Identify transition Architectures
Creat the architecture roadmap & implementation and migration plan.

most TOGAFSH

· To identify the changes to existing business processes.=Process/Event/Control/Product Catalog : identify the full
chain of impacts resulting from changing a high-level process.
· To identify the data entities that can be shared among the sales agents.= Data Entity/Data Component Catalog
· To clarify how to keep the data secured.= Data Security diagram,System/Data matrix,
· To identify the list of non-sales application to be integrated with the sales applications= interface catalog

Identify Stakeholders, Concerns, and Business Requirements

Identify the key stakeholders and their concerns/objectives, and define the key business requirements to be
addressed in the architecture engagement
The major product resulting from this step is a stakeholder map for the engagement, showing which stakeholders
are involved with the engagement, their level of involvement, and their key concernsAnother key task will be to
consider which architecture views and viewpoints need to be developed to satisfy the var ious stakeholder
requirements.
The steps in Phase B are as follows: as example
n Select reference models, viewpoints, and tools (see Section 8.4.1)
n Develop Baseline Business Architecture Description (see Section 8.4.2)
n Develop Target Business Architecture Description (see Section 8.4.3)
n Perfor m gap analysis (see Section 8.4.4)
n Define candidate roadmap components (see Section 8.4.5)
n Resolve impacts across the Architecture Landscape (see Section 8.4.6)
n Conduct for mal stakeholder review (see Section 8.4.7)
n Finalize the Business Architecture (see Section 8.4.8)
n Create Architecture Definition Document (

The steps in Phase A are as follows:

n Establish the architecture project (see Section 7.4.1)
n Identify stakeholders, concer ns, and business requirements (see Section 7.4.2)
n Confir m and elaborate business goals, business drivers, and constraints
n Evaluate business capabilities (see Section 7.4.4)
n Assess readiness for business transfor mation (see Section 7.4.5)
n Define scope (see Section 7.4.6)
n Confirm and elaborate Architecture Principles, including business principles
n Develop Architecture Vision (see Section 7.4.8)
n Define the Target Architecture value propositions and KPIs (see Section 7.4.9)
n Identify the business transfor mation risks and mitigation activities (see Section 7.4.10)
n Develop Statement of Architecture Wor k; secure approval (see Section 7.4.11)

You first list the data used across the enterprise using a Data Entity/Data Component Catalog, including data entities
and also the data components where data entities are stored. You then classify what the data source are and the
relationship with the data entities via a System/Data Matrix. You finally identify common data requirements using a
Data Lifecycle Diagram.

Typical contents of an Architecture Design and Development Contract are:

n Introduction and background
n The nature of the agreement
n Scope of the architecture
n Architecture and strategic principles and requirements
n Confor mance requirements
n Architecture development and management process and roles
n Target Architecture measures
n Defined phases of deliverables
n Pr ior itized joint wor kplan
n Time window(s)
n Architecture deliver y and business metrics

reliability= Business Continuity

Statement: Enterprise operations are maintained in spite of system interruptions.
Rationale: As system operations become more pervasive, we become more dependent on them; therefore, we
must consider the reliability of such systems throughout their design and use.
Security :Data is shared + Data is secured
The steps in Phase E are as follows:
Deter mine/confirm key corporate change attributes
Deter mine business constraints for implementation
Review and consolidate gap analysis results from Phases B to D
Review consolidated requirements across related business functions
Consolidate and reconcile interoperability requirements
Refine and validate dependencies
Confirm readiness and risk for business transformation
Formulate Implementation and Migration planning
Identify and group major work packages
Identify transition Architectures
Creat the architecture roadmap & implementation and migration plan.

The steps in Phase F are as follows:

n Confirm management framework interactions for Implementation and Migration Plan
n Assign a business value to each work package
n Estimate resource requirements, project timings, and availability/delivery vehicle (
n Prioritize the migration projects through the conduct of a cost/benefit assessment and risk
validation
n Confir m Architecture Roadmap and update Architecture Definition Document
n Complete the Implementation and Migration Plan
n Complete the architecture development cycle and document lessons learned

Review the findings of the Business Transfor mation Readiness Assessment previously
conducted in Phase A and determine their impact on the Architecture Roadmap and the
Implementation and Migration Strategy. It is impor tant to identify, classify, and mitigate risks
associated with the transfor mation efor t. Risks should be documented in the Consolidated
Gaps, Solutions, and Dependencies matrix.

Phase G establishes the connection between architecture and implementation organization,

through the Architecture Contract.
Project details are developed, including:
■ Name, descr iption, and objectives/■ Scope, deliverables, and constraints
■ Measures of efectiveness/■ Acceptance criter ia/■ Risks and issues
The steps in Phase G are as follows:
■ Confir m scope and prior ities for deployment with development management
■ Identify deployment resources and skills
■ Guide development of solutions deployment
■ Perfor m enter prise architecture compliance reviews
■ Implement business and IT operations
■ Perfor m post-implementation review and close the implementation
Architectural Definition of Bounded Change Initiatives
Architecture Development (Target First)
Transition Planning
Focus on elaborating the target to meet a previously defined an agreed vision, scope, or set of constraints. Use
the target as a basis for analysis to avoid per petuation of baseline, suboptimal architectures

What groups of people should be involved in procurement-related business processes? = business interaction
matrix
What are the overall lifetimes of the Request for Proposal and Purchase Order business objects? = Data life cycle
Diagram
What non-procurement applications will need to be integrated with any new procurement applications?
=Application communication diagram , Application interaction matrix

Define and document applicable regulatory and security policy requirements The framework and principles rarely
change, and so the security implications called out in the objectives of this phase should be fair ly straightforward.
A written security policy for the organization must be in place, and there should be regular notification and
education established for employees.

Skills frameworks provide a view of the competency levels required for specific roles. They
define:
n The roles within a wor k area
n The skills required by each role
n The depth of knowledge required to fulfil the role successfully
problem from the case :
1- upgrade reliability and performanc e for its secure communication service .
2- the upgraded system must be able to provide assurance and verifications of specific performance measures on
the key services .
3- focusing on these service level details and specific mesasures allow more strong strong requirements to be
inforced in service contract .
4- review processes, content , governeance of th EA cabability to ensure higher target performance and service
levels required by the upgraded system .
5- the artifact don't have explicit provision for defing the in-depth measurement requirements regarding specific
services
from TOGAF
34.4.1 Governance Extensions
The scope of this extension is as follows:
n The ability to apply measures to objectives and then link those measures to services
Changes to the metamodel entities and relationships are as follows:
n Measure is added as a new entity that links objective and business service.
n Ser vice Quality is added as a new entity that provides a generic service profile template to
be applied to business services or contracts.
Changes to the metamodel attributes are as follows:
n Attr ibutes are added for the new metamodel entities of Measure, Ser vice Quality, and
Ser vice Contract
34.4.6 Motivation Extensions
Purpose
The motivation extension is intended to allow additional structured modeling of the drivers, goals,
and objectives that influence an organization to provide business services to its customers. This
in turn allows more efective definition of service contracts and better measurement of business
perfor mance.

A Business Transfor mation Readiness Assessment can be used to evaluate and quantify the organization’s
readiness to undergo a change. This assessment is based upon the determination and analysis/rating of a series of
readiness factors, as descr ibed in Chapter 30. The results of the readiness assessment should be added to the
Capability Assessment (see Part IV, Section 36.2.10). These results are then used to shape the scope of the
architecture, to
identify activities required within the architecture project, and to identify risk areas to be addressed.

13.4.9 Identify and Group Major Work Packages

Key stakeholders, planners, and the enterpr ise architects should assess the missing business capabilities identified
in the Architecture Vision and Target Architecture.
Using the Consolidated Gaps, Solutions, and Dependencies matrix together with the Implementation Factor
ssessment and Deduction matrix, logically group the var ious activities into wor k packages.
Comments

Question 17
 tamam

same as 61

same as 27
 same as 7

same as 6 we ana mosh

moktan3a

Question 4

tamam
 discussed well in
answers we hoa
megawb wrong same
as,25 , 53

same as 51

same as 29 tamam

tamam same as 60

discussed well in
answers we hoa
megawb wrong same
as,19 , 53

Confusion sam as 6 and

16
same as 13

same as 21
hoa mgawb wrong

tamam

tamam
 tamam

reconsider

zeft & vey confusing

confusing

tamam
 tamam

tamam

tamam

tamam we hoa megawb

wrong
tamam we hoa megawb
wrong

tamam we hoa megawb

wrong

tamam we hoa megawb

wrong

same as 20

tamam we hoa megawb

wrong
same as 17
 discussed well in
answers we hoa
megawb wrong same as
19

tamam
subset of 7

tamam we hoa
megawb wrong

same as 18
 hoa mgawb wrong

tamam same as 22 we
hoa mwgawb wrong

tamam we hoa megawb

wrong
same as 11
 Interface Catalouge
App Integration App Interaction Matrix
App Communication Diagram

Data Security Data Security Diagram

Changes in Bus Processes over time Process/event/control/product Catalouge

roles of top Management Actor/Role Matrix

Identify Common Data Req. Data life Cycle Diagram

Purchase Order Product life cycle Diagram

Mesurement Governance extension

group of people Function or Organization
Realiability Bus Contuenity
Distracion Bus Contuenity

minimize Waste, improve efficincy Maxemize Benefit to enterprize

Data is Shared, Data Secure Security

Time to Change Responsive Change Management

Data Quality Data Trustee Data Is an asset

Dependieces is minimal Technology independence

 A
I ensure there is a Request for Architecture Work from the CIO.
Then I ensure that there is recognition for the architecture vision project by
following any project management and programmed management frameworks
used within the organization.

I would identify the key stakeholders and engage with them to understand and
document their concerns and high-level requirements. This would result in a
stakeholder map used to support other deliverables such as the Architecture
Vision, a Communications plan and a Statement of Architecture Work.

I would then define the business capabilities of the

organization needed to fulfill those business goals and drivers and their
readiness for change. Once complete, I would define the scope
, confirm the architecture business principles
and develop the Architecture Vision.

would define the business case for the architecture project, assess the business
risks and produce a risk mitigation plan.

I would then define a plan of enterprise architecture work to meet the scope in
the desired time line and the resources required and secure the support of
stakeholders.
 C

I would start by establishing the architecture project and follow the

appropriate project management method.

I would identify stakeholders their concerns and business requirements

then confirm and elaborate the business goals, business drivers and
constraints I would then evaluate the business capabilities and readiness
for business transformation and define the scope.

I would then develop the architecture vision

, define the target architecture value proposition, KPIs and identify and
mitigate all risks associated with the transformation efort.

I would develop an Enterprise Architecture Plan and Statement of Work

and secure approval from the relevant stakeholders.
 The steps in Phase A are as follows:
n Establish the architecture project (see Section 7.4.1)
n Identify stakeholders, concer ns, and business requirements
(see Section 7.4.2)
n Confir m and elaborate business goals, business drivers, and
constraints (see Section
7.4.3)
n Evaluate business capabilities (see Section 7.4.4)
n Assess readiness for business transfor mation (see Section
7.4.5)
n Define scope (see Section 7.4.6)
n Confirm and elaborate Architecture Principles, including
business principles (see Section
7.4.7)
n Develop Architecture Vision (see Section 7.4.8)
n Define the Target Architecture value propositions and KPIs
(see Section 7.4.9)
n Identify the business transfor mation risks and mitigation
activities (see Section 7.4.10)
n Develop Statement of Architecture Wor k; secure approval
(see Section 7.4.11)