Profession of Enterprise ArchitectProfession of Enterprise Architect

Vineet S RajputVineet S RajputVice President, Bank of America

Vineet.S.Rajput@Bankofamerica.com

AgendaAgenda

What is Enterprise Architecture– Understanding Architecture– What are different types of IT architects– What is an enterprise architect

Application of Enterprise Architecture– When do we use it– Who uses it

Execution of Enterprise Architecture– Why do we need it?– When do we need it?– When will we use it?– Who should be involved in the effort?– Skills & tools for an enterprise architect

Pop Quiz!Pop Quiz!

Enterprise Architecture is designing applications using J2EE, .Net, or similar technologies

False Enterprise Architecture is a way to Organize

Enterprise Data to facilitate integration

False Enterprise Architecture is a way to Design

IT Systems

False

Myth & RealityMyth & Reality

Myth:– It is a way to design IT systems– It is a way to organize Data– It is a way to develop Java applications (J2EE! &

Java certified enterprise architect)

Reality:– It is “Enterprise” Architecture– It involves overall documentation & management

of all aspects of Enterprise– It is a Business issue, not just an IT issue– It has nothing to do with Java!

What is ArchitectureWhat is Architecture

How is a Building BuiltHow is a Building Built

Client / End user has a need Client discusses his needs & taste with an architect The architect ‘designs’ the building considering

– Explicit requirements by the client– Explicit requirements by regulators (city rules etc.)– Implicit requirements of lot location, environment etc.– Implicit requirements that the building must look good and can be

built The structural engineer designs the house structure

– It complies with architects ‘design’– Can be built with existing technologies– Will be strong enough for desired use

The designer creates the embellishments like– Exterior surfacing– Interior colors– Cabinets, Fixtures etc.

Points to notePoints to note

All of the above are ‘required’ in each building

Multiple roles may be played by the same person

The skill set required for each role is distinct

A building will fail if it lacks in any one of the aspects

Strength

BeautyFunction

Requirements Construction

Leaning tower of PisaLeaning tower of Pisa

Great design Would meet functional

requirements Poor structural

strength

Result: It was never

completed

Winchester HouseWinchester House

Sound structural design

Decorated beautifully Lacks functional

design

Result: Legendary status as a

non-functional monument

Museum of LouvreMuseum of Louvre

Highly functional design

Structurally sound Beautiful

Result Considered a

masterpiece

IT system delivery cycleIT system delivery cycle

Client identifies a need Architect creates a

functional ‘design’ Engineers creates the

structure of the system– Software engineers

design application– Network engineers

design infrastructure User experience

designer creates the aesthetics

Developers build the systems

Strength(Robustness)

Beauty(Aesthetics)

Function

Requirements

Construction

Role of an ArchitectRole of an Architect

Ensure system meets the functional needs Ensure system meets the implicit non-

functional needs Ensure system meets the standards

– Legal / Regulatory standards– Industry standards– Company standards

Ensure the system is “engineerable”

Types of ArchitectsTypes of Architects

Types of ArchitectsTypes of Architects

Business Architect Application/ Solutions Architect Information/ Data Architect Infrastructure Architect Enterprise Architect

Business ArchitectBusiness Architect

Ensures that the business processes and strategies can support the business functions.

Primarily concerned with business processes & organizations

This role may have only peripheral interest in IT

A business architect may focus on one process at a time.

A0

Step 1

A0

Step 2

A0

Step 3

Mr. Manager

Supervisor 1 Supervisor 2Supervisor 3

AssociateAssociate Associate Associate

Associate

Application/ Solutions ArchitectApplication/ Solutions Architect

Responsible for understanding the business functions and translating them into implementable systems.

Primarily concerned with individual systems and their interface with ‘neighboring’ systems.

Not really concerned with the big picture or the whole enterprise.

Component1

Component2

Component3

Component4

Component5

Component6

Data/ Information ArchitectData/ Information Architect

Responsible for ensuring that the data is organized properly and supports the solutions.

The responsibility may be across many systems in order to ensure that multiple systems can work together.

Table1

Table2

Table3

Table4

Table5

Infrastructure ArchitectInfrastructure Architect

Concerned about the physical IT infrastructure of the company

This role is concerned with aspects like resource capacity, network capacity, server clustering, administration, and security.

The focus may be enterprise wide or departmental

IBM

IBM

Enterprise ArchitectEnterprise Architect

A big picture role. Responsible for the overall

framework to ensure that all other roles can work in sync.

Ensures that the work of all the architects is a cohesive whole.

Ensures that results are aligned with the business direction.

Sets the strategic direction, manages risks, defines standards and maintains cross organization communication.

““Official” DefinitionOfficial” Definition

Enterprise Architecture (EA) links the business mission, strategy, and processes of an organization to its IT strategy. It is documented using multiple architectural models or views that show how the current and future needs of an organization will be met

The Final White Paper on Enterprise Architecture

US Chief Information Officers Council

But!But!

This is the still an IT Centric view of Enterprise Architecture

Because– This definition was created for the CIOs– Most of today’s enterprises are information centric

However– True EA must deal with the WHOLE enterprise– EA may create/ improve solutions with little or no

IT involvement

Application of Enterprise ArchitectureApplication of Enterprise Architecture

When do we use EAWhen do we use EA

Enterprises use it Every day! Change management

– Strategy planning– Requirement analysis– Cost & schedule estimation– Regulatory compliance & certification– Enterprise wide planning reporting– Knowledge sharing

How to utilize Documented EA?How to utilize Documented EA?

Day to Day operations & management Creating a managed strategy of evolution

– Process change– System & technology change

Tactical planning– Requirement validation for projects– Process, system, and technology traceability– Risk assessment & management

Regulatory compliance monitoring & reporting

Mergers & Acquisitions: evaluating the partner against stated goals for acquisition

Who can benefit from itWho can benefit from it

Owners: for understanding the overall enterprise

Business leaders: for setting directions Planners: for strategy & tactical planning Managers: for managing risks, costs,

priorities, & timelines Implementers: for evaluating alternatives

& achievement of objectives

Implementing Enterprise ArchitectureImplementing Enterprise Architecture

Why do we need Enterprise ArchitectureWhy do we need Enterprise Architecture

Regulatory/ Legal reasons– Under Clinger-Cohen act, all federal govt. projects

need Enterprise Architecture– EA can help with Sarbanes Oxley requirements– Financial institutions may use EA for operational

risk management under Basel II

IT strategy planning Enterprise change management Operational risk assessment/ mitigation

When do we need it?When do we need it?

All the time The sooner the better The alternative

– Trial and error– Demolish and restart

What does an Enterprise Architect do?What does an Enterprise Architect do?

Create portfolio: Current & Future states of– Goals & Strategies– Locations– Organizations– Functions & processes– Physical & knowledge assets

Create standards & processes for– Documenting the portfolio– Keeping portfolio current– Perform gap analysis and solution evaluation– Creation of solution

The Enterprise Architecture processThe Enterprise Architecture process

Document baseline: the as-is state– What we have: Physical, Intellectual, and Data

assets– How we do things: Functions & processes– Where: Physical and logical locations associated

with processes– Who: Roles, organizations & persons associated

with processes

Understand reason for change: drivers, strategies & timelines.

Design Future state Identify gaps & create migration strategy

The Enterprise Architecture ToolsThe Enterprise Architecture Tools

Knowledge Collection– Databases, Word, Groupware

Portfolio repository for knowledge assets– Popkin, Troux etc.

Process modeling tools– IDS-Scheer Aris, Visio etc.

Analysis & traceability tools– Excel, Popkin, minitab etc.

Communication tools– E-mail, Websites, Powerpoint etc.

Who should be involved in definitionWho should be involved in definition

Senior managers/ execs, both IT & business

Strategy planners Process improvement specialists Technology SMEs

Functions of Enterprise ArchitectFunctions of Enterprise Architect

Understand Goals& Strategies

AnalyzeStrategies & Requirements

SynthesizeSolutions

CommunicateTo Stakeholders

•Communication•Domain Knowledge

•Environment Knowledge

•Communication•Domain Knowledge

•Environment Knowledge

•Technology Knowledge

•Communication•Domain Knowledge

•Environment Knowledge

•Technology Knowledge

•Communication•Domain Knowledge

•Environment Knowledge

Govern/ Control

•Communication•Policing

Skills for an enterprise architectSkills for an enterprise architect

Communication– Learn– Listen– Understand– Critique– Translate– Champion– Envision– Educate– Mediate– Police/ Enforce– Document– Present

Domain Knowledge– Understand– Spot trends– Translate– Model– Process Knowledge– Analysis

Technology Knowledge– Technology

Environment– Spot trends– Methodologies– Tools– Design solutions

SummarySummary

An Architect is ensures the functional integrity of a system

Enterprise Architect is responsible for the functional integrity of WHOLE Enterprise

Good architecture is the foundation of a strong enterprise

Architecture documentation is necessary to manage change

A savvy business leader is the best Enterprise Architect

Is it a surprise then

that Bill Gates is an “Architect” of Microsoft

QuestionsQuestions