lesson 1 2007 v0.3 - aaltoend = business objective means = business strategy list of business...
TRANSCRIPT
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY1
Enterprise Architectures
Timo Itälä, Paavo Kotinurmi, MattiHämäläinen
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
In the early days...
Automation of manual tasksPayroll
Bookkeeping
Order entry
Invoicing
Statistics
2
Input Output
Data Program
Computer
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
The next steps...Application packages
Personnell
Economy administration
Production Control
Material Requirements
Inventory-Orders-Shipping-Invoicing
Purchasing
Product development
...
3
User tasks
Databases
Applications
Platforms
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä4
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
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
Example: Larger organization
5
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
Business processes...
Application suitesERP: Enterprise ResourcePlanning
CRM: Customer RelationshipManagement
SCM: Supply Chain Management
HR: Human Resources
Financials
PDM: Product Data Management
ECM: Enterprise ContentManagement
DSS: Decision Support Systems...
6
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä7
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?
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
Enterprise Architecture
Alignment of IT and business
Organization´s strategy, goals and operations
Business Processes
Organizational charts
Conceptual models, data models
Application suites
Software and hardware platforms
8
Business
Information Applications
Technology
Inte
gra
tion
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä9
Course Map 2007
12.9: EA (Enterprise Architecture) Overview
19.9: ERP (Enterprise Resource Planning) systems
26.9: BI (Business Intelligence) and Data Warehousing
3.10: BPM (Business Process Management) and SOA (Service Oriented Architecture)
10.10: Governance
17.10: ECM (Enterprise Content Management) and PDM (Product Data Management)
24.10: Enterprise Architecture Summary
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä10
Enterprise Architectures Outline
Evolution of IT within enterprises
EA Frameworks
EA Methodologies
Tools
Operating Model
Maturity Stages
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
Enterprise Architecture
Frameworks
11
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 NETW ORK
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. NETW ORK
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-conditionMeans = 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 CycleT ime = Execute
e.g. T iming Definition
Cycle = Machine CycleT ime = Interrupt
e.g. SCHEDULE
e.g. Master Schedule
Time = Business EventCycle = Business Cycle
List of Organizations
People = Major Organizations
e.g. W ork Flow Model
People = Organization UnitW ork = W ork Product
e.g. Human Interface
People = RoleW ork = Deliverable
e.g. Presentation Architecture
People = UserW ork = Screen Formate.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 Methods
Tools
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä12
Why do we need 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
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä13
Evolution of Frameworks
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä14
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
Can be applied to any complex system, not just information systems
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä15
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-conditionMeans = 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 Formate.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)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä16
Examples of models
Cell R1-R2:C1 ConceptualData Model
Palveluntilaaja
Hoitojakso Laskutettupalvelu
Hinnastontuote
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
Rekisteri Materiaali taipalvelu Hankinta
Rekisterin-pitäjä
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä17
Examples of models
Cell R1-R2:C2 Core Business Processes
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä18
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
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä19
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
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä20
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
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä21
The Open Group Architecture Framework(TOGAF)
Business Architecture
Data Architecture
Applications Architecture
Technical Architecture
ADM Architecture Development Method
Principles: How to develop good principles
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä22
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
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä23
Architecture Development Cycle- Expansion
Steps within phasesExample phase D
Output is generatedthroughout the process
Versioning: Version numbers
Early versions may bemodified in later phases
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä24
Why do we need tools?
Most models are visualModels should share a common repositoryArchitecture development teamhas a consistent set of modelsModels can be published for a large audienceModels can be used to generatedefinitions and codeVersion management automation
Repository
Palveluntilaaja
Hoitojakso Laskutettupalvelu
Hinnastontuote
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
Rekisteri Materiaali taipalvelu Hankinta
Rekisterin-pitäjä
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä25
Who are involved in EA?
Source: Schekkerman, 2004
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
Operating Model of an enterprise
26
Source: Ross, 2005
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
IT Architecture Stages
An application silo architectureThe architecture consists of architectures of individual applicationsrather than an architecture for the entire enterprise
A standardized technology architectureThe IT architecture becomes enterprise-wide and provides efficienciesthrough technology standardization and in most cases centralization
A rationalized data architectureThe enterprise wide IT architecture expands to include standardizationof data and processes
A modular architectureThe architecture builds onto enterprise-wide global standards withloosely coupled applications, data and technology components to preserve the global standards while enabling local differences
27
Source: Ross, 2003
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä
Architecture Maturity Stages
28
Source: Ross, 2004
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä29
Course Map 2007 (preliminary)
12.9: EA (Enterprise Architecture) OverviewEnterprise Architect’s work in practise: Case of a financial company
Sakari Lehtonen, IDS Scheer
19.9: ERP (Enterprise Resource Planning) systems
26.9: BI (Business Intelligence) and Data Warehousing
3.10: BPM (Business Process Management) and SOA (Service Oriented Architecture)
10.10: Governance
17.10: ECM (Enterprise Content Management) and PDM (Product Data Management)
24.10: Enterprise Architecture Summary
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä30
Questions?
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Timo Itälä31
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, BPM & SOA