1

2

Where it Where it Where it Where it All All All All BBBBeginseginseginsegins

3

The ProblemThe ProblemThe ProblemThe Problem

Every enterprise already has an architecture

EA addressed problems• Increasing IT system complexity• Poor business alignment

The Business Need• Implementation methodologies (i.e. RUP)

� Relative importance of response to a business need

• Enterprise Architecture Focus� Identification, specification and prioritization of business needs

4

What is Enterprise Architecture ?What is Enterprise Architecture ?What is Enterprise Architecture ?What is Enterprise Architecture ?

IBM Systems Journal, article "A Framework for Information Systems Architecture”, John Zachman, 1987. originally described as an information systems architectural framework, soon renamed to enterprise-architecture framework.

Definition: Formal description of the structure and operation of an organization. The motivation behind EA is to determine how the wholeorganization can effectively achieve its current/future objectives.

5

“ The cost involved and the success of the business that depends increasingly on its information systems require a disciplined approach to the management of those systems.”

J.A. Zachman

It’s a MetaphorIt’s a MetaphorIt’s a MetaphorIt’s a Metaphor

• Cottage• Simplicity!• Architect?

6

• Complex System = � costs for maintenance

• Large City• Simplicity is out of question!• City planners• Architects• Success not guaranteed

What is Architecture Framework?What is Architecture Framework?What is Architecture Framework?What is Architecture Framework?

An architecture framework is methodology and tool that:� Guides the development or organization specific architecture

� Embodies best practices and common wisdom

� Assists the evaluation of architectures

� Ensures that every domain is adequately

reviewed and documented

� Provides generic categorization

of architecture artifacts.

� Presents a set of standards,

design concepts, models, services

7

THE BIG FOURTHE BIG FOURTHE BIG FOURTHE BIG FOUR

90% of EA implementations apply

� Zachman Framework

� The Open Group Architecture Framework (TOGAF)

� Federal Enterprise Architecture (FEA)

� Gartner Methodology

8

Zachman Framework for EAZachman Framework for EAZachman Framework for EAZachman Framework for EA

9

TOGAF TOGAF TOGAF TOGAF v.v.v.v.9999

Architecture Content Framework (ACF)� provides structural model for architectural

content.

Architecture Development Method (ADM)� The TOGAF core - describes a method

for developing an EA� Iterative, over the whole process, between

phases, and within phases� Populates Architecture Repository

10

EA Architecture DomainsEA Architecture DomainsEA Architecture DomainsEA Architecture Domains

� Business architecture� Data/information architecture

� Application/systems architecture� Information Technology (IT)

architecture

11

Business architecture

Application architecture Technical architecture

Information architecture Data architecture

?

?

?

?

?

TOGAF ACFTOGAF ACFTOGAF ACFTOGAF ACF

Architectural work product categories:� Deliverables � Artifacts � Building blocks

� Architecture � Solution

Content Metamodeldefinition of all types of building blocks in EA and their relations.

12

TOGAF ADMTOGAF ADMTOGAF ADMTOGAF ADM

Preliminary phase� Review the organizational context for EA execution� Present and setup the process for stakeholders� Ensure commitment to the success of everyone involved

Phase A� In: Request for work – business need, budget, personel� Out: architectural vision - appropriate stakeholders have been

identified and their issues have been addressed

Phase B� detailed description of the baseline and target business objectives, and

gap descriptions of the business architecture

Phase C� Target Information and Applications Architecture

13

TOGAF ADM (Continued)TOGAF ADM (Continued)TOGAF ADM (Continued)TOGAF ADM (Continued)

Phase D� Complete the technical architecture—the infrastructure necessary to

support the proposed new architecture

Phase E� Evaluate the various implementation possibilities, identifies the major

implementation projects that might be undertaken (the projects that convinced the org. to start EA implementation)

Phase F� Prioritize projects on cost and risk

Phase G� Architectural specification for implementation of projects

Phase H� Modify change management process with new artifacts

Go to Phase A

14

Where TOGAF meets RUPWhere TOGAF meets RUPWhere TOGAF meets RUPWhere TOGAF meets RUP

• TOGAF is NOT RUP alternative

• The two frameworks have different purposes

• RUP • technology architecture driven. • Business requirements -> software

• TOGAF • business architecture driven • Technology -> realize business

vision

15

Methodology RatingMethodology RatingMethodology RatingMethodology Rating

Criteria Rating (1 – very poor, 4 – very good)

ZACHMAN17 TOGAF31 FEA31 GARTNER29

Taxonomy completeness* 4 2 2 1

Process completeness* 1 4 2 3

Reference-model guidance 1 3 4 1

Practice guidance* 1 2 2 4

Maturity model 1 1 3 2

Business focus* 1 2 1 4

Governance guidance 1 2 3 3

Partitioning guidance 1 2 4 3

Prescriptive catalog 1 2 4 2

Vendor neutrality* 2 4 3 1

Information availability* 2 4 2 1

Time to value* 1 3 1 4

To To To To AAAAvoid Misunderstandingvoid Misunderstandingvoid Misunderstandingvoid Misunderstanding

• EA is not rocket science

• EA brings the business and the technology sides together

• EA is a path and not destination

• EA is a valuable tool that guides the change

• A framework does not make architectural design an automated process

17

How will EA Change Your Business?How will EA Change Your Business?How will EA Change Your Business?How will EA Change Your Business?

EA purpose is to create environment that is respons ive to change and supportive of the delivery of the busine ss strategy.

�Use common sense / common language�Be systematic�Avoiding misunderstandings�Know WHAT you do before you start�Know WHY you are doing it� Learn from best practices� Talk to business users in business terms�Record what, where, when, how, who and why

18

Enterprise Architecture BenefitsEnterprise Architecture BenefitsEnterprise Architecture BenefitsEnterprise Architecture Benefits

Efficient IT operation: � Lower software development and maintenance costs� Increased portability of applications� Improved ability to address critical enterprise-wide issues (i.e. security)� Easier system management� Easier upgrade and exchange of systems

Reduced risk for future investment: � Reduced complexity in IT infrastructure� Flexibility to make, buy, or out-source IT solutions� Reduced risk overall in new investment

Return of investment� Greater ability to respond to new demands� Greater business value from IT operations � Greater ability to implement new technologies� Faster, simpler and cheaper delivery to market

19

To TOGAF or Not?To TOGAF or Not?To TOGAF or Not?To TOGAF or Not?

20

What TOGAF does What TOGAF does NOT

provides framework and guidelines make decision (Business and IT architects do)

guides building EA necessarily guide building good EA

provides guidelines for I/O provide detailed templates

allows phases to be skipped, done incompletely or reordered

put the EA process in strict limits

DEMO

21

22

IT ArchitectureIT ArchitectureIT ArchitectureIT Architecture

� Clearly define the structure of AS-IS state� Be derived from BUSINESS requirements� React to change according to the enterprise market� Be understood and receive support in the enterprise� Set out the strategy for future purchases� Specify migration strategies� Reduce number and complexity of interfaces between components

23