lesson 1 v0.2

1

SoberITSoftware Business and Engineering Institute

HELSINKI UNIVERSITY OF TECHNOLOGY

Enterprise Architectures

Timo Itälä, Paavo Kotinurmi, MattiHämäläinen

2



Timo Itälä

Enterprise Architectures Outline

Presenter Introduction

Why do we use computers in enterprises?

Why do we need an enterprise architecture?

What are architecture, methodologies, frameworks

Zachman Framework

TOGAF Framework

Other frameworks

Discussion, summary

3



Timo Itälä

Presenter Introduction: Timo Itälä

1969: Started studies in data processing at Helsinki University

1970: Started half time programmer at Helsinki UniversityCentral Hospital

1972: Datasaab-Valmet: Minicomputers, compilers, business systems

1979: Tandem Computers, OLTP, Data Warehousing

1996: ICL Data, Data Warehousing, BI, Architectures

1999: EMC, storage, professional services

2000: Conceptia Oy, consultant, seamless healthcare, integration, data warehousing, HL7, IT capabilities

4



Timo Itälä

Why do we use computers in enterprises?

Cost savings

Competitive advantage

Infrastructure

Business Intelligence

Enterprise Applications

Technology is shaping the enterprise

5



Timo Itälä

Cost savings

Automation of manual tasks

Justification based on ROI: savings

Hospital: Automation of laboratory, payroll, invoicing, statistics

Can you continue saving 10% of costs per annum?

To achieve more results with the sameemployees

6



Timo Itälä

Competitive Advantage

To add value to the customer

Shorter delivery times: Paper Manufacturers

Build to order: Cars, computers

Local advertisements: Newspaper publishers

Interactive banking, self service

Competitive edge <-> competition will catch up

7



Timo Itälä

Computing infrastructure

Shipyard: Computing will be as necessary and as natural as water, drain and electricity

ATM networks: from competitive advantage to commodity which have to be produced at lowcost

Mission critical systems: operational systemswhich are needed to run the business

Product Data Management: Product structures, Version control, review process, change impactanalysis, workflow management

E-mail: you cannot survive without it

8



Timo Itälä

Business Intelligence

Retailers: Who are our customers? What do theybuy? What are our best products? What are ourbest markets? What are our competitors?

Loyalty cards: Understand customer behaviour. Give bonus in return of getting the information

Supplier management: Who are our suppliers, how do they perform? (Case Nokia)

Information within the product (paper, electricity, travel bureaus)

9



Timo Itälä

Enterprise Applications

Process SupportERP (Enterprise Resource Planning)

SCM (Supply Chain Management)

CRM (Customer Relationship Management)

HR (Human Resources)

Financials

Patient Administration System

PDM (Product Data Management)

Content ManagementDocument Management

Portals

10



Timo Itälä

Technology is shaping the enterprise

Lippupalvelu, verkkopankki, E-kirje

Amazon.com

Google

eBay, Huuto.net

Vertaa.com

…

11



Timo Itälä

Legacy is here to stay

Old applications are still working

Multiple platforms (mainframe, unix, windows, linux…)

New applications are somehow connected to the old ones (common database, file transfer, message queues, remote procedure calls, webservices…)

Applications built in-house, tailored, packaged, bought as a service (asp)

12



Timo Itälä

Example: A Healthcare organization

SELITYKSETLiittymät Toteutumattomat osajärjestelmät

JUVO Vuodeosastot- SIJAINTITIEDOT(ML 2, Radu, Upo, Toti, Puh.kesk.)- HOITOJAKSOT(Hoit.luok.,Infekt.,Maksuli,Mama,Mynla)- sis./ulos kirj.- REIPAS jonot- HILMO hoitoilmoitukset

Hoit.luokitus

MAKSULI Maksuliikenne- potilasmaksut

ML 2 Kliin.kemian lab.- pyynnöt, tulokset- laboratorion sisäinen osuus- verikortisto

VERTTI Verikeskus- Verituotteet- tilaukset- verikeskuksen sisäinenosuus

SAMBA Mikrobiologian lab.- laboratorion sisäinen osuus

RADU Rtg, Klf, Knf- lähetteet, lausunnot- röntgenin sisäinen osuus- ilmoittautumiset ja käyntitiedot- ajanvaraus- kuljetuslista

QPATI Patologian lab.- patologian laboratorion sisäinenosuus

YKERT Sairaskertomusten hallinta- SIJAINTITIEDOT(Radu, Upo,Juvo,- sairaskertomusten sijainnit (paperit)

Haikara Äitiyshuolto- esitiedot- raskaus- synnytys- vastasyntynyt

TOTI Toimenpideyksiköt- leikkaussalivaraukset- leikkauslistat- tehdyt leikkaukset- päivystysilmoitus

SAIRAALAINFEKTIOT- infektioiden seuranta

WEBKERTsairaskertomukset- sairaskertomustekstit

SYÖPÄREKISTERI

FTP- syöpäilmoitus

YLEISET REKISTERIT(kaikki käyttävät)- yksikkö-, osasto-, erikoisala-, laitos-- kunta-, postinumerorekisterit- lääkäri-, diagnoosirekisterit-, toimenpiderekisteri....

FTP- HETU, nimi, tutk

KUVANTAMISLAITTEET

TERVEYSKESKUS

OVT- lähete

OVT- lausunto

HL7- pyyntö

HL7- tulos

- pyyntö(veriryhmänsopivuus)

HL7- tulos

(veriryhmänsopivuus) HL7

- vastausHL7

- tilausOVT

- vastaus- tilaus

KANS.TERV.LAIT.

FTP- tartuntatauti

ilmoitus

UPO Poliklinikat- POTILASREKISTERI(kaikki käyttävät, paitsi Seniori)- KÄYNTITIEDOT(Mynla, Infekt., Maksuli, Haikara )- lähetetiedot- ajanvaraus- käyntitiedot- rtg-UPO rtg ajanvaraus

FYSIS Fysiatria- fysiatrian käynnit

SOSISSosiaalityöntekijät- sosiaalityöntekijöidenkäynnit

MYNLA- hinnoittelu

VÄESTÖREKISTERIKESKUS

FTP (OVT)- henkilötiedot

VRK SatSHP- henkilötiedot

- henkilötiedot

-ilmoittautumiset

- RTG, KLF, KNFajanvaraus

HL7- lausunto

FTP- tulokset

MEDREC Dialyysi

CD postitus (OVT)- synt.lapset

- tulokset

- tulokset

- pkl toimenpiteet

- äidin tiedot- veriryhmä, vasta-aineet

SATSHP:n POTILASTIETOJÄRJESTELMIENLIITTYMÄT JOISSA TIETO SIIRTYY FYYSISESTI

21.3.2005/T Seppänen

FTP- Potilaslista hoitojaksojen perusteella- Potilaslista ajanvarauste perusteella

- vastasyntyneentiedot

FTP (OVT)- vastasyntyneen tiedot

- kuolintiedot

SENIORI Psykiatria- potilasrekisteri- käynti- ja hoitotiedot (Mynla)- potilasmaksut

HL7- pyyntö

HL7- tulos

ORDER Tilaukset- lääketilaukset- materiaalitilaukset

SAMPO varasto / apteekkiMateriaalihallinto

- tilaukset

FINATaloushallinto

POWERPLAYTilastot / Raportit

FTPRadu,ML2,Toti,Fysis,Vertti,Maksuli,My

nla

FTPRadu, ML2, Toti, Fysis, Upo, Juvo,

Mama, Hoit.luok., Seniori, Fina

CASHMANAGER

PRIMAhenkilöstöh.

palkanmaksu

FTP- viitesuor

FTP-

todist.palkkiot- eml palkkiot

STAKESCD postitus- hilmotiedot

CD postitus- hilmotiedot

FTP- perintä

FTP- kyselytAKTIV KAPITAL

FTP- viitesuor

CD-postitus- E-ostot

TYKS

-luokitustiedot

NOS ksilpHL7Ajanvaraukset

TT2000+ Työterveysh.-Pyynnöt tehdääm ML2:eentyöpäytäintegraation kautta

Adapterit-UPO, JUVO, Webkert,ML2, Seniori,

miten uudet tiedot?ATJ

MD-TITANIA

LÄÄKITYS

Lähete-Palaute

Anestesia

Teho

NordDRG

AROMI/tilaukset

-hoitojakso- diagnoosit

- toimenpiteet

-hoitojaksotiedot

SPR / Vok

FTP- veritilaukset /

varaukset

-laskutustietoja

Kuntosoft

Fysotools

HYS

FTP- E-ostot

- laskurivit

FTP- avohoito tiedot- hoitojaksotiedot-tuotepäätös nro:t

- E-osto laskut

AHA- KUNTOUTUS- määrärahaseuranta- kuntoutuspäätökset

- OSTOPALVELUT- päätökset- APUVÄLINEET- välineiden vuokraus- väl. luokitusrekisteri

KERNEL- käyttäjähallinta- käyttäjien valikot- TaskMan tausta-ajojen hallinta

SANOMAT HL7/OVT- M-gate

- Datagate

Luettelo järjestelmistäjohon on liittymät

Muut liittymät

Peräkkäistiedostot

FTP-

henkilökunta

FTP- sairaslomat

FTP- palkat

DNApuhelinvaihde

LII potilaspuhelut FTP- puh.maksut

FTP- potilaat

- saldot-nimikkeet

Kuva-arkisto

Sovellukset

Säilytettävät

Korvattavat

Epäselvät

Kehitetään/poistetaan

Ulkopuoliste

13



Timo Itälä

Critical questions to IT department

What is the balance between your software development, support and maintenance costs?How do procure new applications?What technology platforms do you support?How do you solve interoperability issues?What are your security and privacy policies and solutions?How do you support innovation and the change of business of the enterprise?What is your IT architecture?

14



Timo Itälä

Course Map

13.9: Enterprise Architectures Overview

20.9: ERP and PDM systems

27.9: BI and Data Warehousing

4.10: BPM and SOA

11.10: Content Management Systems

18.10: Enterprise Architecture Summary

15



Timo Itälä

Why do you need IT architecture?An effective IT architecture is critical to business survivaland success, and is the indispensable means to achievingcompetitive advantage through IT.Today´s CEOs know that the effective management and exploitation of information through IT is the key to business success.An IT architecture addresses this need, by providing a strategic context for the evolution of the IT system in response to the constantly changing needs of the business environment.An IT architecture provides the necessary technicalfoundation for an effective IT strategy, which is the core of any succesful modern business strategy

”The Open Group”

16



Timo Itälä

What makes an architecture of a house?

What did I think when building the house?How the house looks like?What is the floor plan?How is it located on the site?How are the connections: road, electricity, water, drain, phone, internet…What is it made of?

When building a house you need to answer many questionsof different stakeholders/roles: The answers are models ordesigns or artefacts…

17



Timo Itälä

A Framework

Predefined set of models and designs

Example:Permission to buildReport of ownership

Extract of cityplan

Drawings of the buildingFloor plans

Facade

Location on the site

Implicit classification of roles and views

18



Timo Itälä

Zachman Framework

John Zachman: Observation of different industries:Buildings

Airplane construction

Information systems

Design, construction and maintenance of complex products: what different people need?

Roles or perspectives: the planner, the owner, the designer, the builder, the subcontractor (the functioning enterprise).

Different questions: What, How, Where, Who, When, Why

19



Timo Itälä

Models by roles and views

Sub-contractor

Builder

Designer

Owner

Planner

WhyWhenWhoWhereHowWhat

Can be applied to any complex system, notjust information systems

20



Timo Itälä

From information systems to an enterprise

Why should we make a distinction between an enterprise and the processes, data and infrastructure of which it is composed?Focus on the abstraction of the enterprisearchitectureIs an enterprise a house or a city, which is a collection of houses, roads and otherinfrastructureHow do you integrate?How do you manage change?

21



Timo Itälä

What is an enterprise?An enterprise in this context is any collection of organizations that has a common set of goals and/or a single bottom line.

CorporationDivision of a corporationSingle departmentGovernment agencyChain of geographically distant organizations linked together by common ownership

Extended enterprise may includePartnersSuppliersCustomers

22



Timo Itälä

Zachman Framework

e.g. DATA

ENTERPRISE ARCHITECTURE - A FRAMEWORK

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. Application Architecture

I/O = User ViewsProc .= Application Function

e.g. System Design

I/O = Data Elements/SetsProc.= Computer Function

e.g. Program

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Business Logistics System

Node = Business LocationLink = Business Linkage

e.g. Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. Technology Architecture

Node = Hardware/SystemSoftware

Link = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g. Rule Specification

End = Sub-condition

Means = Step

e.g. Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals/Strat

Ends/Means=Major Bus. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component CycleTime = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

John A. Zachman, Zachman International (810) 231-0531

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGYENTERPRISE

e.g. Business Plan

TM

(1987)

23



Timo Itälä

Zachman FrameworkThe Framework is a classification scheme for descriptive representations of a complex object, in this case the Enterprise.Some set of the models identified in the Framework may be produced in some sequence by some application development methodology, but the Framework itself is neutral relative to the methodology or tool or to a manual process for creating the Enterprise.The selected subset of Cells, or the composites of Cells, or the sequence of producing the Cells for application development (or for manual systems development, for that matter) is a function of the value system inherent in the methodology (or tool).The Framework implies nothing about the sequence in which the models may (or may not) be produced methodoligally nor does it imply anything about who produces or contributes to the production of the models.

24



Timo Itälä

Examples of models

Cell R1-R2:C1 ConceptualData Model

Palveluntilaaja

HoitojaksoLaskutettu

palveluHinnaston

tuote

Palvelun-tuottaja

Palvelunmaksaja

Tuotettusuorite

Aika

Palveluketju

Hoito- taipalvelu-

tapahtuma

Hoitoko-konaisuus

Palvelun-tuottajantyöntekijä

Henkilö

Palkkatiedot

Henkilönkoulutus- jatyöhistoria

Työpanos

Asiakas/Potilas

Asiakas-palaute

Potilas-kertomus-merkintä

Kertomus

RekisteriMateriaali tai

palveluHankinta

Rekisterin-pitäjä

25



Timo Itälä

Examples of models

Cell R1-R2:C2 Core Business Processes

26



Timo Itälä

Example: A process map

PäivVos

VosPkl

PklPkl Vos Lab Rtg Leikk Jne

Potilaan hoitoprosessi

Talousprosessi

Toiminnan suunnittelu- ja seurantaprosessi

UPO,WEBKERTX

JUVOWEBKERTY

MULTI-LAB II

RADU TOTI

Toiminnanohjaus

Kustannusseuranta

Seuranta jaraportointi

Z

27



Timo Itälä

Primitive and Composite Models

A Cell represents a primitive model

Combination of Cells represent a CompositeModel

Cells can be combined horisontally or verticallybut not diagonally

28



Timo Itälä

Enterprise Architecture IFEAD:

Enterprise Architecture is a complete expression of the enterprise; a master plan which “acts as a collaboration force” between aspects of business planning such as goals, visions, strategies and governance principles; aspects of business operations such as business terms, organisation structures, processes and data; aspects of automation such as information systems and databases; and the enabling technological infrastructure of the business such as computers, operating systems and networks.

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

29



Timo Itälä

Why do we need a method?

We want to repeat something?

In what order do we produce the models?

Method: Wikipedia definition:…“In Software Engineering in particular, a method is technical recipe for building software. Compare with a methodology.”

Zachman Framework is method neutral

Other frameworks have evolved over time to give a method

30



Timo Itälä

Evolution of Frameworks

31



Timo Itälä

Survey 2003: What EA are you using?

32



Timo Itälä

The Open Group Architecture Framework(TOGAF) structure

TOGAF Architecture Development Method

The Enterprise Architecture Continuum

The TOGAF Foundation ArchitectureTOGAF Technical Reference Model

TOGAF Standards Information Base (SIB)

The Integrated Information Infrastructure ReferenceModel

TOGAF Resource Base

33



Timo Itälä

The Open Group Architecture Framework(TOGAF)

Business Architecture

Data Architecture

Applications Architecture

Technical Architecture

ADM Architecture Development Method

Principles: How to develop good principles

34



Timo Itälä

Architecture Development Cycle

ADM is iterativeWhole process

Between phases

Within phases

For each iteration:The breath of coverage

The level of detail

Time horizon

The architectural assets

35



Timo Itälä

Architecture Development Cycle- Expansion

Steps within phasesExample phase D

Output is generatedthroughout the process

Versioning: Version numbers

Early versions may bemodified in later phases

36



Timo Itälä

Mapping to the Zachman Framework

37



Timo Itälä

Scope of TOGAF ADM

Architecture domainsBusiness

Data

Applications

Technology

Zachman rowsPlanner

Owner

Designer

Builder

38



Timo Itälä

Preliminary Phase: Framework and principles

Framework definition

Architecture principles

Reference to:Business principles

Business Goals

Business Drivers

39



Timo Itälä

Phase A: Architecture VisionApproved SOW

Refined statements ofBusiness principles

Business Goals

Strategic Drivers

Architecture principles

Architecture VisionBusiness baseline V1

Technical baseline V1

Business architecture V1

Technical architecture V1

40



Timo Itälä

Phase B: Business Architecture

Review phase A

Target business architecture V2

Organization structure

Business goals and objectives

Business functions

Business services

Business processes

Business Roles

Gap analysis results

Technical requirements

41



Timo Itälä

Phase C: Data Architecture

Data Baseline description

Target data architectureConceptual data model

Logical data model

Data management processmodels

Data entity/business functionmatrix

Data interoperabilityrequirements

Other relevant viewpoints

Gap analysis results

42



Timo Itälä

Phase C: Applications Architecture

Applications Baselinedescription

Target applicationsarchitecture

Process Systems Model

Systems/Place Model

People/Systems Model

Systems/Time Model

Applications interoperabilityrequirements

Other relevant viewpoints

43



Timo Itälä

Phase D: Technology Architecturestep 1

Create a baselinedescription in the TOGAF format

Technology architectureprinciples

Technology architecture V 0.1

- Constraints

- Architecture principles

- Requirements traceability:- key questions list- criteria for selection of service portfolio

44



Timo Itälä


Consider differentarchitecture referencemodels, viewpoints and tools

Technology architectureV0.2 views

Networked computing

Communications

Processing

Cost

Standards

45



Timo Itälä


Create an architecturalmodel of building blocks


Networked computing

Communications

Processing

Cost

Standards

46



Timo Itälä


Select the services portfoliorequired per building block


Target services

Change requests

47



Timo Itälä


Technology architectureVersion 1

48



Timo Itälä

Composite mapping for phase DTechnology architectureVersion 1

49



Timo Itälä

How to act upon the architecture?

Opportunities and solutions

Migration planning

Implementationgovernance

50



Timo Itälä

Other Frameworks

Focus on different aspects

Come from different background

Serve different purpose

Title: 'A Comparative Survey of Enterprise Architecture Frameworks' can be found at

http://www.enterprise-architecture.info/Presentations%20Jaap%20Schekkerman.htm

51



Timo Itälä

52



Timo Itälä

The journey continues…

John Zachman: Enterprise Architecture: Looking Back and Looking Ahead, 1999In summary of the past

Architecture is counter-culturalIt is not perceived to be a survival issue by the EnterpriseWe don´t know how to actually do all of itIt takes time and actual work

Looking toward the futureArchitecture IS the information age cultureArchitecture IS an enterprise survival issueThere are few theoretical breakthroughs left to be madeThere are no technical obstacles for doing architecture work

53



Timo Itälä

Course Map

13.9: Enterprise Architectures Overview

20.9: ERP and PDM systems

27.9: BI and Data Warehousing

4.10: BPM and SOA

11.10: Content Management Systems

18.10: Enterprise Architecture Summary

54



Timo Itälä

Questions?

lesson 1 v0.2

Documents