An Introductory Session on Enterprise Architecture

The Enterprise Architecture An Introduction

Keshav Tripathy

AgendaAgenda

• What is architecture?What is architecture?• What is Enterprise Architecture?

H EA i b i i l t d?• How EA is being implemented?• Who’s running EA in the world and what

are the outcomes• Practical steps for beginnersp g• Questions

Architecture - OxfordArchitecture Oxford

• “The art or science of building orThe art or science of building or constructing edifices of any kind for human use ”use…

• “The special method or ‘style’ in accordance with which the details of theaccordance with which the details of the structure and ornamentation of a building are arranged ”are arranged.

What is architecture IEEEWhat is architecture IEEE• “The organizational structure of a system or g y

component.”– IEEE Standard 610, “Standard Computer Dictionary: A

Compilation of IEEE Standard Computer Glossaries”Compilation of IEEE Standard Computer Glossaries

• “The fundamental organization of a system embodied in its components, their relationships to each other, and to the environment, and the principles guiding its design and evolution.”– IEEE Standard 1471 “IEEE Recommended Practice forIEEE Standard 1471, IEEE Recommended Practice for

Architectural Description of Software-Intensive Systems.

What is system architectureWhat is system architecture

• Design:Design:– How each component should be build– OO, Class, design patterns etc’.g p

• Differences between architecture and design– Many different designs may address the same need– Different architectures imply different needs

• Sample from reality: House– Architecture: number of rooms, main structure,

character, guiding lines.Design: interior design rooms structure electricity– Design: interior design, rooms structure, electricity, etc’

What is EAWhat is EA

• Its not technical!Its not technical!• Aligning IT to business.• Answering all of the enterprise needsAnswering all of the enterprise needs• Transverse view.• knowing and managing the current situation• knowing and managing the current situation,

paving the road for the wanted one.• Implementation of information management• Implementation of information management• Enforce homogeneous solutions and enable

“One system” to the usersOne system to the users.

The TOGAF wayThe TOGAF way

• Reference modelReference model– How to do certain tasks.

Not an outcome!– Not an outcome!• Zachman, DoDAF, TOGAF, other sector

i t doriented. • They’re all adjustable to your needs.

The TOGAF wayThe TOGAF way

• Never ending organization process which buildsNever ending organization process which builds upon several stages:– Initiation– Business architecture.– Information architecture– Applications architecture– Infrastructure architecture

G– Governance– Gap analysis– And againAnd again …

Enterprise architecture - TOGAFEnterprise architecture TOGAF

Steps for each phaseSteps for each phase• A – Initiation and Framework:

• Use Business Scenarios to define relevantUse Business Scenarios to define relevant business requirements

• Identify stakeholders / concerns• Build consensus with partnersBuild consensus with partners

• B – Baseline Description• Build description of current system

Id tif “ h t’ ”• Identify “what’s wrong”• Inventory of re-usable building blocks

• C –Target Architecture:g• Identify all needed services• Multiple views to address stakeholder concerns

Steps for each phaseSteps for each phase• D –Opportunities and pp

Solutions:• Evaluate and select major work

packagespackages

• E – Migration Planning:• Prioritize work• Develop outline plan

• F –Implementation:• Develop full planDevelop full plan• Execute

• G –Architecture M i tMaintenance• Establish procedure for

maintenance of new baseline

Business architectureBusiness architecture• Enterprise architecture awarenessp• Implement EA vision

– Organization commitment– Mapping stakeholders

• Business architectureH th b i k– How the business works

• BPM / BPMN / BPEN– Business targetsg

• What are the vision and mission.• Gaps from current situation

– Constraints and demands from ITConstraints and demands from IT

Information architectureInformation architecture• Influence from business architecture.• Classification enterprise information.• How information is being managed?g g• Where to store data?• Data schemas• How to collaborate data• Mapping of unused / missing information• Information availability• Information security.

Application architectureApplication architecture

• Byproduct of business and informationByproduct of business and information architecture.

• Aligning systems to business needs• Aligning systems to business needs• Basic structure of systems

– Architecture patterns• Relations and communication between

systems• How systems share datay

Technology architectureTechnology architecture

• Influenced by other architectures.Influenced by other architectures.• Needed infrastructure to support the systems.• Collection of selected technologies and tools toCollection of selected technologies and tools to

implement chosen architectures– Developmentp– Tools– Communication– Backups– Standards

ImplementationImplementation• Solution

– Mapping current situation– Defining the ideal situation– Gap analysisp y– Creating blueprints, instructions and standards to fill the gaps.

• Work planPractical definition of migration to ideal situation on time line– Practical definition of migration to ideal situation on time line.

– Taking into account current situation and other constraints• Governance

G th h hit t i d il k– Governance the chosen architecture in daily work

Who implement itWho implement it• Governmental agencies in the states

– DODO– States– FBI

• Firms & enterprisesp– Exxon– Starbucks– Pepsi– Telco (1.5 B euro).– DHL

• Improvement of IT products and saving• In Israel

– ת"מפא– בזק– אורנג– משרדים ממשלתיים

Cisco exampleCisco example

Practical stepsPractical steps• Read about EA

– Books:• Enterprise Architecture Planning, Steven H. Spewak. • The Practical Guide to Enterprise Architecture by James p y

McGovern,Scott W. Ambler,Michael E. • Handbook on Enterprise Architecture (International

Handbooks on Information Systems) by Peter Bernus, Laszlo Nemes (Editor), Gunter Schmidt (Editor).Laszlo Nemes (Editor), Gunter Schmidt (Editor).

– Articles• A Practical Guide for Developing an Enterprise Architecture

: http://www.gao.gov/bestpractices/bpeaguide.pdfp g g p p g p• Awareness

– PostersOrganization meetings– Organization meetings

Practical stepsPractical steps

• Choose a frameworkChoose a framework– Learn it– Consider hiring a consultant that knows it.g

• Adjust the framework to your enterprise needs • Determine the scope and objectives. p j• Create a vision. • Get CxO level approve.Get CxO level approve.• Set KPIs (key performance indicator) for

measurement.

Q&AQ&A