sys 703 lec 4-2012- ea

7/31/2019 SYS 703 Lec 4-2012- EA

1/57

SYS703

ENTERPRISESYSTEMS

DEVELOPMENT

EnterpriseArchitecture

7/31/2019 SYS 703 Lec 4-2012- EA

2/57

7/31/2019 SYS 703 Lec 4-2012- EA

3/57

FLOOR

PLAN

3

7/31/2019 SYS 703 Lec 4-2012- EA

4/57

4

WIRING

PLAN

7/31/2019 SYS 703 Lec 4-2012- EA

5/57

5

PLUMBING

PLAN

7/31/2019 SYS 703 Lec 4-2012- EA

6/57

7/31/2019 SYS 703 Lec 4-2012- EA

7/577

7/31/2019 SYS 703 Lec 4-2012- EA

8/57

INTRODUCTION

Enterprise are struggling withexploding demands forinformation.

Competitive pressures make itnecessary to connect islands ofinformation, resources andpeople into a cohesive whole.

New era applicationsworkflow, collaboration,electronic data interchange, on-line imaging and intelligentdocumentscan enable

business process innovationand alter a companys positionin its industrys value chain.

The new business objectivesdemand a fully integrated

information framework andinfrastructure.

7/31/2019 SYS 703 Lec 4-2012- EA

9/57

NEXT GENERATION COMPUTING Further, enterprise needs a

framework for designingchangeable systems. Informationsystems must be able to respondto changes in the business and intechnology.

The need for systems to evolveover time and the requirement forongoing enhancements and

maintenance create growingcomplexity in informationsystems.

Hence, developing a systemsarchitecture, therefore, is not anoption but a necessity for

successfully implementingcomplex, next generationsystems.

A good enterprise architectureprovides a framework forchangeand change is one ofthe few constants in todaysbusiness world.

7/31/2019 SYS 703 Lec 4-2012- EA

10/57

SCOPE OF THE ENTERPRISE

Confusion often arises from the evolvingnature of the term "enterprise".

An extended enterprise nowadays frequentlyincludes partners, suppliers, and customers. Ifthe goal is to integrate an extendedenterprise, then the enterprise comprises thepartners, suppliers, and customers, as well asinternal business units.

The business operating model concept isuseful to determine the nature and scope ofthe enterprise architecture within an

organization.

7/31/2019 SYS 703 Lec 4-2012- EA

11/57

WHAT IS ENTERPRISE ARCHITECTURE?

Enterprise architecture has vastdefinitions ranging from pure enterprisewide technical architecture to pure

business architecture without anycorrelation to IT

In this class, we see EnterpriseArchitecture as a combination ofenterprise wide business architecture and

IT architecture

7/31/2019 SYS 703 Lec 4-2012- EA

12/57

12

7/31/2019 SYS 703 Lec 4-2012- EA

13/57


EA Online User Group

Enterprise Architecture is the practice of applying acomprehensive and rigorous method for describing acurrent or future structure for an organization's processes,information systems, personnel and organizational sub-units, so that they align with the organization's core goalsand strategic direction.

NIH (National Institute of Health): Enterprise architecture is a comprehensive framework

used to manage and align an organization's InformationTechnology (IT) assets, people, operations, and projects

with its operational characteristics. In other words, theenterprise architecture defines how information andtechnology will support the business operations andprovide benefit for the business.

7/31/2019 SYS 703 Lec 4-2012- EA

14/57


Enterprise architecture is the business of architectingthe enterprise.

The goal of the process is to take the businessstrategy and translate it into effective change of the

enterprise

The process itself involves creating key principals andmodelsthat describe the enterprises future and

enable its evolution.

Enterprise architecture typically refers to the highest ormost generic level at which architecture applies in anorganization.

7/31/2019 SYS 703 Lec 4-2012- EA

15/57


The scope of enterprise architectureincludes the enterprises people,processes, information, and technology

and their relationships to each other andthe external environment

Enterprise architects are the people who

create the solutions to address thebusiness challenges and support theenterprise in implementing those solutions.

7/31/2019 SYS 703 Lec 4-2012- EA

16/57

SAMPLE JOB POSTING FOR ENTERPRISE

ARCHITECT

Job Title: Enterprise Architect Position Type: Permanent Pay Rate: DOE Skills: Enterprise Architecture, Sharepoint This position is responsible for setting the Global

Enterprise Architecture strategy for those functions whichare enterprise wide such as Finance, Procurement, andHR. The SAP application suite is the primary technology forthese functions and the candidate must be an expert inmultiple areas of SAP (emphasis on Financial, HR, SEM,SRM, and BW). This person will also have expertise in

portal and collaboration technologies including SAP Portaland Microsoft Sharepoint. The Enterprise Architect reportsto the Chief Enterprise Architect and will be a keycontributor in developing the technology strategies used bythe corporation. The person will be responsible fordeveloping multi-year plans to implement the defined

strategies.

7/31/2019 SYS 703 Lec 4-2012- EA

17/57

SAMPLE JOB POSTING FOR LEAD ARCHITECT

The Lead Enterprise Architect will: Focus on establishing and championing a 3 year

Enterprise Architecture plan that is used to realize theI/T strategy which includes: SAP applications,middleware technologies such as webMethods, andPortal/Collaboration technologies.

Provide leadership to major global and strategicprojects. Work with all levels of the business and I/T (with a

focus on the executive level) to develop architectureblueprints to support major business initiatives.

Provide leadership around the creation, improvementand adoption of development methodologies.

Maintain a continuous focus on the technologyindustry and business solution providers Conduct research with leading industry analysts to

understand and validate current and futuretechnology and industry trends.

7/31/2019 SYS 703 Lec 4-2012- EA

18/57

A fairly general definition of architecture in the system space is as

follows:

Architecture is the high-level definition of thestructure of a system, which is comprised of parts,their interrelationships, and externally visibleproperties.

With this definition in mind, it is all the more obvious thatEnterprise Architecture is more than the collection of theconstituent architectures (Business, Application, Technology, andInformation). The interrelationships among these architectures, andtheir joint properties, are essential to the Enterprise Architecture.

http://www.ewita.com
http://www.ewita.com/http://www.ewita.com/

7/31/2019 SYS 703 Lec 4-2012- EA

19/57

19

7/31/2019 SYS 703 Lec 4-2012- EA

20/57

20

7/31/2019 SYS 703 Lec 4-2012- EA

21/57

WHY IS ENTERPRISE ARCHITECTURE NEEDED?

System Complexity : Information systems and business

processes are complex and will

become increasingly complex in thefuture.

As system complexity increases, the

costs to build and maintain thosesystems increase and take more of anorganizations resources in time, money,and personnel.

7/31/2019 SYS 703 Lec 4-2012- EA

22/57

WHY IS ENTERPRISE ARCHITECTURE NEEDED?

Poor business alignment:While costs are increasing, it is becoming

harder for organizations to make sure thatIT systems and spending are aligned withbusiness needs

IT costs are increasing while the value they

bring to an organization is decreasing if theIT and business goals are not aligned.

7/31/2019 SYS 703 Lec 4-2012- EA

23/57

23

7/31/2019 SYS 703 Lec 4-2012- EA

24/57

EA DOMAINS

With one leg in the business side of the enterprise,

one leg in the technological side and a head whichsees them both EA composed from several domains. EA domains are:

Business: describes how the business is working andbusiness directions.

Information: describes how the enterprise use, manageand maintain information

Applications: describes how applications are used andmanage

Technology/Infrastructure: describes the technology

needed to run the business Combination of all of these domains give a cross

wide overview of the enterprise, thus enables to bestalign IT to the business.

7/31/2019 SYS 703 Lec 4-2012- EA

25/57

Business Architecture

Business Architecture models the business enterprise using

logical service units (business processes) and the events that

trigger them to represent the re-architected approach tosatisfying customer requirements. It attempts to show howbusiness is to be done.

7/31/2019 SYS 703 Lec 4-2012- EA

26/57

Information ArchitectureThe Enterprise Information Architecture consists of datamodels, and databases that serve all participants in theenterprise business environment and the strategies,standards, policies required to develop and implement them.An Information Architecture implies that the enterprise nolonger develops "islands of databases." An InformationArchitecture enables the enterprise to develop a common,

shared, distributed, accurate, and consistent data resource.

7/31/2019 SYS 703 Lec 4-2012- EA

27/57

Application Architecture

Application Architecture links the data and business

architecture to reflect applications. It supports the work

activities of the business processes, and provides automatedprocedures. Application Architecture manages informationstorage and retrieval in support of the enterprise objectives. Itaddresses location considerations and how information isutilized.

7/31/2019 SYS 703 Lec 4-2012- EA

28/57

Technology Architecture

Technology Architecture links up with the Application,

Business, and Data Architectures to provide interoperable

technology platforms that meet the needs of the various userroles (Actors) at identified work locations.

7/31/2019 SYS 703 Lec 4-2012- EA

29/57

29

7/31/2019 SYS 703 Lec 4-2012- EA

30/57

EA DOMAINS

With one leg in the businessside of the enterprise, one legin the technological side anda head which sees them bothEA composed from severaldomains.

EA domains are: Business: describes how the

business is working and

business directions. Information: describes how

the enterprise use, manageand maintain information

Applications: describes howapplications are used andmanage

Technology/Infrastructure:describes the technologyneeded to run the business

Combination of all of thesedomains give a cross wideoverview of the enterprise,thus enables to best align ITto the business.

7/31/2019 SYS 703 Lec 4-2012- EA

31/57

31

7/31/2019 SYS 703 Lec 4-2012- EA

32/57

EA=S+B+T

Enterprise Architecture =

Strategy + Business + Technology

The distinct difference between EA andother types of IT planning is that EA isdriven by strategic goals and businessrequirements

7/31/2019 SYS 703 Lec 4-2012- EA

33/57

33

7/31/2019 SYS 703 Lec 4-2012- EA

34/57

EA IMPLEMENTATION PROCESS

These domains are used to define theas-is and to-be architecture of theenterprise.

Each domain requires a specializedarchitect (mainly in large enterprises)

After having the current and targetarchitecture, enterprise architectureanalyze the gaps and produce list ofprojects to fill the gaps

The projects prioritized by theenterprise principles and constraintsinto time-lined migration plane (multi-year plan)

Enterprise architecture isnt just astrategic plan. EA also govern thatthe defined projects are taking placeand are following EA blue-prints,principles and standards

Enterprise architecture continues toadd value by monitoring business andtechnology changes and finding outhow they effect the enterprise

7/31/2019 SYS 703 Lec 4-2012- EA

35/57

EA FRAMEWORK

Enterprise architecture is one of the complex taskscarried out by enterprises Composite from many tasks that need to be taken in

given sequence Required people with multi discipline knowledge Based on virtual team work Depend on organization culture and politics

An enterprise architecture framework provides support byserving as a checklist to identify the actual enterpriseelements that describe an enterprise.

To help enterprise architects, there are several enterprisearchitecture frameworks available for use.

EA framework definition has two versions: Zachman: what are the artefacts that EA shouldproduce

TOGAF,FEAF, Etc: what are the tasks that areneeded to be taken, and in what order, to producegiven artefacts

7/31/2019 SYS 703 Lec 4-2012- EA

36/57

EA FRAMEWORK

Enterprise architecture

frameworks providestructure, support, andintegrity in much thesame manner as theframe of a building.

Figure 1: A building framework

7/31/2019 SYS 703 Lec 4-2012- EA

37/57

EA HISTORYMAJOR MILESTONESDate Event

Mid 1980sZachman framework . The first Enterprise Architecture Framework

1989 National Institute of Standards and Technology (NIST) framework

1996 Clinger-Cohen ACT. American regulation which causes adaptation

of EA in American federal agencies

1999(Sep) Department of Defense (DOD) and the Department of the Treasury.

[DODAF, TEAF]. Two of the most common frameworks

2001 EU directives on the award of public contracts European regulation

that encourage enterprise architecture use

2002 (Feb) OMB established the Federal Enterprise Architecture Program

Management Office to develop the FEA,

2002 OMB was given explicit responsibility for overseeing government

enterprise architectures by the E-Government Act of 2002

2002 TOGAF ver 8.0 (enterprise edition). Previous versions just deal with

technology aspect

37From EA Online User Group

7/31/2019 SYS 703 Lec 4-2012- EA

38/57

HISTORY OF ENTERPRISE ARCHITECTURE

The field now known as enterprisearchitecture first came about 20 years ago.

In 1987, J.A. Zachman wrote an articleentitled A Framework for InformationSystems Architecture in the IBM SystemsJournal.

Zachman originally described as informationsystems architectural framework, but it wassoon renamed enterprise-architectureframework.

7/31/2019 SYS 703 Lec 4-2012- EA

39/57

ZACHMAN FRAMEWORK FOR ENTERPRISE

ARCHITECTURES

John Zachman describes the framework as,Simply a logical structure for classifying andorganizing the descriptive representations of anEnterprise that are significant to themanagement of the Enterprise, as well as the

development of the Enterprises systems.

Source: http://www.zachmaninternational.com/2/Home.asp

ZACHMAN FRAMEWORK

7/31/2019 SYS 703 Lec 4-2012- EA

40/57

ZACHMAN FRAMEWORK

Source: http://www.zachmaninternational.com/index.php/home-article/13

7/31/2019 SYS 703 Lec 4-2012- EA

41/57

HOW IT WORKS?

Rows- illustrate different descriptions of anenterprise from a certain perspective.


7/31/2019 SYS 703 Lec 4-2012- EA

42/57

HOW IT WORKS?

Columns- One aspect ofthe enterprise from top tothe bottom from different

perspectives.


7/31/2019 SYS 703 Lec 4-2012- EA

43/57

STRENGTHS AND WEAKNESSES

Strength End result (table) Good classification schema that defined what

are the views for each role in the enterprise

Weaknesses

Missing instructions and tools that will help tounderstand how to achieve the needed views(no process)

More technology oriented then business Recommended to be used in architecture work when the

outcomes needed to be defined

THE OPEN GROUP ARCHITECTURE

7/31/2019 SYS 703 Lec 4-2012- EA

44/57

THE OPEN GROUP ARCHITECTURE

FRAMEWORK (TOGAF)

Divides enterprise architecture into fourcategories:

1. Business architecture Describes theprocesses the business uses to meet itsgoals

2. Application architecture Describeshow specific applications are designedand how they interact with each other

3. Data architecture Describes how the

enterprise data stores are organized andaccessed4. Technical architecture Describes the

hardware and software infrastructure thatsupports applications and their

interactions

7/31/2019 SYS 703 Lec 4-2012- EA

45/57

TOGAF STRUCTURE

TOGAF has three Parts: ADM (Architecture Development Method Process)

What are the phases needed to be taken in order to produceenterprise architecture

For each step: Inputs Steps to follow

Expected outputs Continuum

Repository of the building blocks and patterns Gathered from the industry Entered by your enterprise

Has two main components: TRM Technology Reference Model SIB Standard Information Base

Resource base Resources to help enterprise architects in their work. Contain methods, approaches and advices for

Governance, Principles, Views, Business scenarios, Tools

ADM: HOW IT WORKS?

7/31/2019 SYS 703 Lec 4-2012- EA

46/57

ADM: HOW IT WORKS?

Source:http://www.opengroup.org/architecture/togaf8-doc/arch/Figures/prelim.gif

7/31/2019 SYS 703 Lec 4-2012- EA

47/57

HOW IT WORKS?

Source: http://www.developer.com/java/ent/article.php/3374171

7/31/2019 SYS 703 Lec 4-2012- EA

48/57


Strengths- provides a process fordeveloping an architecture.

Flexible so can be tailored to a companys

organization

Weakness- Open/generic, no specific end

result

FEDERAL ENTERPRISE ARCHITECTURE

7/31/2019 SYS 703 Lec 4-2012- EA

49/57

FEDERAL ENTERPRISE ARCHITECTURE

FRAMEWORK (FEAF)

Technical Architecture Framework forInformation Management (TAFIM) was one ofthe first attempts at enterprise architecture bythe Department of Defense in the mid 90s

Influenced the Clinger-Cohen Act (in US) whichstated that federal agencies should improvetheir IT investments

Over time Government efforts in enterprisearchitecture lead to the creation of FEA

7/31/2019 SYS 703 Lec 4-2012- EA

50/57

HOW IT WORKS?

An enterprise is built of segments:

There are two types of segments

Core mission area segments

Business-services segments

Also use enterprise services which spanpolitical boundaries

7/31/2019 SYS 703 Lec 4-2012- EA

51/57

SEGMENT MAP OF THE FEDERAL GOVERNMENT

Source:http://msdn2.microsoft.com/en-us/architecture/bb466232.aspx

7/31/2019 SYS 703 Lec 4-2012- EA

52/57

FEA PROCESS

Step 1: Architectural AnalysisDefine a simple and concise vision

for the segment, and relate it back to the organizational plan.

Step 2: Architectural DefinitionDefine the desired architecturalstate of the segment, document the performance goals, considerdesign alternatives, and develop an enterprise architecture for thesegment, including business, data, services, and technology

architectures.

Step 3: Investment and Funding StrategyConsider how theproject will be funded.

Step 4: Program-Management Plan and Execute ProjectsCreate

a plan for managing and executing the project, includingmilestones and performance measures that will assess projectsuccess.


7/31/2019 SYS 703 Lec 4-2012- EA

53/57


Strengths- clearly defines output andprovides a process for creating a framework

Weakness- Government architecture so ithas not been applied to a business before General Accounting Office (GAO) reported that,

Only 20 of 96 agencies examined hadestablished at least the foundation for effective

architecture management. Further, while 22agencies increased in maturity since 2001, 24agencies decreased in maturity and 47 agenciesremained the same.

7/31/2019 SYS 703 Lec 4-2012- EA

54/57

COMPARATIVE SURVEY OF ES FRAMEWORKS BY

IFEAD IN 2003

Other

6%

CIMOSA (Computer

Integrated Manufacturing

Open Systems

Architecture) framework

6%

Organization own

32%

C4ISR, US Defense

Architecture Framework

6%

TOGAF, the Open Group


9%

FEAF, US Federal

Enterprise Architecture

Framework

6%

Zachman Framework

18%

IAF, Cap Gemini Ernst &

Young's - Integrated


7%

ISO/IEC 14252 (IEEE

Std 1003.0) Guide to the

POSIX Open System

Environment

3%

TEAF, US TreasuryEnterprise Architecture

Framework.

4%

PERA (Purdue

Enterprise Reference

Architecture) Framework

3%

54

Survey Question: What kind of EA Frameworks are you using?

7/31/2019 SYS 703 Lec 4-2012- EA

55/57

ALIGN OR BECOME EXTINCT?

55

SUMMARY

7/31/2019 SYS 703 Lec 4-2012- EA

56/57

SUMMARY

EA is distinguished from, and yetencompasses, other forms of business,service, systems, data, and technologyarchitecture.

EA seeks to be the over arching frameworkand methodology for integrating strategic,business, and technology planning acrossthe entire enterprise. In so doing, EA claimsto be the highest level of all meta concepts

that guide the analysis, design, and ongoingimprovement of enterprises in the public,private, military, academic, and nonprofitsectors

7/31/2019 SYS 703 Lec 4-2012- EA

57/57

EA SURVEY FROM 2003

sys 703 lec 4-2012- ea

Documents