docEnterprise Systems Architecture and its reference models
download 
Report Transcription
Enterprise Systems Architecture and its reference models
SoberIT Software Business and Engineering Institute Enterprise Architectures Timo Itälä, Paavo Kotinurmi, Matti Hämäläinen HELSINKI UNIVERSITY OF TECHNOLOGY 1 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 2 SoberIT Software Business and Engineering Institute Presenter Introduction: Timo Itälä 1969: Started studies in data processing at Helsinki University 1970: Started half time programmer at Helsinki University Central 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 3 SoberIT Software Business and Engineering Institute Why do we use computers in enterprises? Cost savings Competitive advantage Infrastructure Business Intelligence Enterprise Applications Technology is shaping the enterprise HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 4 SoberIT Software Business and Engineering Institute 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 same employees HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 5 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 6 SoberIT Software Business and Engineering Institute 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 low cost Mission critical systems: operational systems which are needed to run the business Product Data Management: Product structures, Version control, review process, change impact analysis, workflow management E-mail: you cannot survive without it HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 7 SoberIT Software Business and Engineering Institute Business Intelligence Retailers: Who are our customers? What do they buy? What are our best products? What are our best 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) HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 8 SoberIT Software Business and Engineering Institute Enterprise Applications Process Support ERP (Enterprise Resource Planning) SCM (Supply Chain Management) CRM (Customer Relationship Management) HR (Human Resources) Financials Patient Administration System PDM (Product Data Management) Content Management Document Management Portals HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 9 SoberIT Software Business and Engineering Institute Technology is shaping the enterprise Lippupalvelu, verkkopankki, E-kirje Amazon.com Google eBay, Huuto.net Vertaa.com … HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 10 SoberIT Software Business and Engineering Institute 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, web services…) Applications built in-house, tailored, packaged, bought as a service (asp) HELSINKI UNIVERSITY OF TECHNOLOGY 11 Timo Itälä SoberIT Software Business and Engineering Institute Example: A Healthcare organization SATSHP:n POTILASTIETOJÄRJESTELMIEN LIITTYMÄT JOISSA TIETO SIIRTYY FYYSISESTI 21.3.2005/T Seppänen CD postitus (OVT) - synt.lapset CD postitus - hilmotiedot STAKES NordDRG FTP (OVT) - vastasyntyneen tiedot - kuolintiedot VÄESTÖREKISTERI KESKUS - fysiatrian käynnit VRK SatSHP FTP (OVT) - henkilötiedot - henkilötiedot - henkilötiedot Psykiatria - potilasrekisteri - käynti- ja hoitotiedot (Mynla) - potilasmaksut UPO Poliklinikat NOS ksilp luokitustiedot Hoit.luokitus FTP - kyselyt - RTG, KLF, KNF ajanvaraus WEBKERT FTP - potilaat - SIJAINTITIEDOT (ML 2, Radu, Upo, Toti, Puh.kesk.) - HOITOJAKSOT (Hoit.luok.,Infekt.,Maksuli,Mama,Mynla) - sis./ulos kirj. - REIPAS jonot - HILMO hoitoilmoitukset laskutustietoja sairaskertomukset - sairaskertomustekstit FTP - viitesuor - vastasyntyneen tiedot FTP - Potilaslista hoitojaksojen perusteella - Potilaslista ajanvarauste perusteella - pkl toimenpiteet HL7 - lausunto Kuntosoft Fysotools RADU Rtg, Klf, Knf OVT - lähete FTP - puh.maksut LII potilaspuhelut - leikkaussalivaraukset - leikkauslistat - tehdyt leikkaukset - päivystysilmoitus Sosiaalityöntekijät - sosiaalityöntekijöiden käynnit HL7 Ajanvaraukset JUVO Vuodeosastot hoitojaksotiedot FTP - perintä AKTIV KAPITAL TOTI Toimenpideyksiköt SOSIS - POTILASREKISTERI (kaikki käyttävät, paitsi Seniori) - KÄYNTITIEDOT (Mynla, Infekt., Maksuli, Haikara ) - lähetetiedot - ajanvaraus - käyntitiedot - rtg-UPO rtg ajanvaraus SENIORI CD postitus - hilmotiedot -hoitojakso - diagnoosit - toimenpiteet FYSIS Fysiatria ilmoittautumiset OVT - lausunto DNA FTP Radu,ML2,Toti,Fysis,Vertti,Maksuli,My nla - lähetteet, lausunnot - röntgenin sisäinen osuus - ilmoittautumiset ja käyntitiedot - ajanvaraus - kuljetuslista FINA Taloushallinto - laskurivit puhelinvaihde FTP - avohoito tiedot - hoitojaksotiedot -tuotepäätös nro:t - E-osto laskut FTP - HETU, nimi, tutk CASH MANAGER FTP - viitesuor MAKSULI Maksuliikenne - potilasmaksut MYNLA - hinnoittelu KUVANTAMISLAITTEET FTP todist.palkkiot - eml palkkiot PRIMA henkilöstöh. palkanmaksu FTP henkilökunta FTP - palkat FTP - tulokset HL7 - pyyntö FTP - sairaslomat HL7 - tulos MEDREC Dialyysi Haikara Äitiyshuolto ML 2 Kliin.kemian lab. - pyynnöt, tulokset - laboratorion sisäinen osuus - verikortisto HL7 - pyyntö MD-TITANIA AHA - KUNTOUTUS - esitiedot - raskaus - synnytys - vastasyntynyt - tulokset HL7 - tulos TT2000+ Työterveysh. -Pyynnöt tehdääm ML2:een työpäytäintegraation kautta - määrärahaseuranta - kuntoutuspäätökset CD-postitus - E-ostot HYS - OSTOPALVELUT - päätökset - APUVÄLINEET - välineiden vuokraus - väl. luokitusrekisteri FTP - E-ostot TYKS - tilaukset ORDER - äidin tiedot - veriryhmä, vasta-aineet - pyyntö (veriryhmän sopivuus) Tilaukset - lääketilaukset - materiaalitilaukset TERVEYSKESKUS HL7 - tulos (veriryhmän sopivuus) SELITYKSET Sovellukset Liittymät VERTTI Toteutumattomat osajärjestelmät Korvattavat SANOMAT HL7/OVT - M-gate - Datagate LÄÄKITYS Säilytettävät Peräkkäistiedostot Lähete-Palaute Kehitetään/ poistetaan Luettelo järjestelmistä johon on liittymät Epäselvät Anestesia Verikeskus - Verituotteet - tilaukset - verikeskuksen sisäinen osuus Kuva-arkisto HL7 - vastaus HL7 - tilaus QPATI Patologian lab. - patologian laboratorion sisäinen osuus FTP - veritilaukset / varaukset FTP - syöpäilmoitus SPR / Vok SYÖPÄREKISTERI Teho HELSINKI UNIVERSITY OF TECHNOLOGY AROMI/ tilaukset SAMPO varasto / apteekki Materiaalihallinto - saldot -nimikkeet - tilaus OVT - vastaus SAMBA Mikrobiologian lab. - laboratorion sisäinen osuus FTP - tartuntatauti ilmoitus - tulokset FTP Radu, ML2, Toti, Fysis, Upo, Juvo, Mama, Hoit.luok., Seniori, Fina POWERPLAY Tilastot / Raportit Adapterit -UPO, JUVO, Webkert,ML2, Seniori, miten uudet tiedot? ATJ SAIRAALAINFEKTIOT YLEISET REKISTERIT - infektioiden seuranta (kaikki käyttävät) - yksikkö-, osasto-, erikoisala-, laitos- kunta-, postinumerorekisterit - lääkäri-, diagnoosirekisterit-, toimenpiderekisteri .... YKERT Sairaskertomusten hallinta - SIJAINTITIEDOT (Radu, Upo,Juvo, - sairaskertomusten sijainnit (paperit) KANS.TERV.LAIT. KERNEL Muut liittymät - käyttäjähallinta - käyttäjien valikot - TaskMan tausta-ajojen hallinta Ulkopuoliste Timo Itälä 12 SoberIT Software Business and Engineering Institute 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? HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 13 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 14 SoberIT Software Business and Engineering Institute Why do you need IT architecture? An effective IT architecture is critical to business survival and success, and is the indispensable means to achieving competitive 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 technical foundation for an effective IT strategy, which is the core of any succesful modern business strategy ”The Open Group” HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 15 SoberIT Software Business and Engineering Institute 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 questions of different stakeholders/roles: The answers are models or designs or artefacts… HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 16 SoberIT Software Business and Engineering Institute A Framework Predefined set of models and designs Example:Permission to build Report of ownership Extract of cityplan Drawings of the building Floor plans Facade Location on the site Implicit classification of roles and views HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 17 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 18 SoberIT Software Business and Engineering Institute Models by roles and views What How Where Who When Why Planner Owner Designer Builder Subcontractor Can be applied to any complex system, not just information systems HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 19 SoberIT Software Business and Engineering Institute 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 enterprise architecture Is an enterprise a house or a city, which is a collection of houses, roads and other infrastructure How do you integrate? How do you manage change? HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 20 SoberIT Software Business and Engineering Institute 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. Corporation Division of a corporation Single department Government agency Chain of geographically distant organizations linked together by common ownership Extended enterprise may include Partners Suppliers Customers HELSINKI UNIVERSITY OF TECHNOLOGY 21 Timo Itälä SoberIT ENTERPRISE ARCHITECTURE - A FRAMEWORK DATA What FUNCTION How NETWORK Where Software Business and Engineering Institute List of Processes the Business Performs PEOPLE Who TIME When TM MOTIVATION Why SCOPE (CONTEXTUAL) List of Things Important to the Business Planner ENTITY = Class of Business Thing Function = Class of Business Process Node = Major Business Location e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics System Ent = Business Entity Reln = Business Relationship Proc. = Business Process I/O = Business Resources Node = Business Location Link = Business Linkage e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System Architecture e.g. Human Interface Architecture e.g. Processing Structure Ent = Data Entity Reln = Data Relationship Proc .= Application Function I/O = User Views Node = I/S Function (Processor, Storage, etc) Link = Line Characteristics People = Role Work = Deliverable Time = System Event Cycle = Processing Cycle End = Structural Assertion Means =Action Assertion TECHNOLOGY MODEL (PHYSICAL) e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design Builder Ent = Segment/Table/etc. Reln = Pointer/Key/etc. Proc.= Computer Function I/O = Data Elements/Sets Node = Hardware/System Software Link = Line Specifications e.g. Data Definition e.g. Program e.g. Network Architecture Ent = Field Reln = Address Proc.= Language Stmt I/O = Control Block Node = Addresses Link = Protocols People = Identity Work = Job e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION List of Locations in which the Business Operates List of Organizations Important to the Business List of Events Significant to the Business List of Business Goals/Strat Zachman Framework ENTERPRISE MODEL (CONCEPTUAL) Owner SYSTEM MODEL (LOGICAL) Designer DETAILED REPRESENTATIONS (OUT-OFCONTEXT) SubContractor FUNCTIONING ENTERPRISE People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Critical Success Factor e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan People = Organization Unit Work = Work Product People = User Work = Screen Format e.g. Security Architecture Time = Business Event Cycle = Business Cycle Time = Execute Cycle = Component Cycle e.g. Timing Definition Time = Interrupt Cycle = Machine Cycle e.g. SCHEDULE End = Business Objective Means = Business Strategy e.g., Business Rule Model End = Condition Means = Action e.g. Rule Specification End = Sub-condition Means = Step e.g. STRATEGY SCOPE (CONTEXTUAL) Planner ENTERPRISE MODEL (CONCEPTUAL) Owner SYSTEM MODEL (LOGICAL) Designer TECHNOLOGY MODEL (PHYSICAL) Builder DETAILED REPRESENTATIONS (OUT-OF CONTEXT) SubContractor FUNCTIONING ENTERPRISE HELSINKI UNIVERSITY OF TECHNOLOGY John A. Zachman, Zachman International (810) 231-0531 (1987) Timo Itälä 22 SoberIT Software Business and Engineering Institute Zachman Framework The 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. HELSINKI UNIVERSITY OF TECHNOLOGY 23 Timo Itälä SoberIT Software Business and Engineering Institute Examples of models Cell R1-R2:C1 Conceptual Data Model Asiakaspalaute Palvelun maksaja Asiakas/ Potilas Palvelun tilaaja Palveluntuottaja Palveluketju Hoitokokonaisuus Hoitojakso Laskutettu palvelu Hinnaston tuote Kertomus Potilaskertomusmerkintä Hoito- tai palvelutapahtuma Tuotettu suorite Työpanos Materiaali tai palvelu Hankinta Rekisteri Aika Rekisterinpitäjä HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä Palkkatiedot Palveluntuottajan työntekijä Henkilön koulutus- ja työhistoria Henkilö 24 SoberIT Software Business and Engineering Institute Examples of models Cell R1-R2:C2 Core Business Processes HELSINKI UNIVERSITY OF TECHNOLOGY 25 Timo Itälä SoberIT Software Business and Engineering Institute Example: A process map Pkl Pkl Pkl Vos Vos Vos Päiv Lab Rtg Leikk Jne Toiminnanohjaus Potilaan hoitoprosessi Talousprosessi Kustannusseuranta Toiminnan suunnittelu- ja seurantaprosessi JUVO UPO, WEBKERT WEBKERT Y X MULTI- RADU LAB II Seuranta ja raportointi TOTI Z HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 26 SoberIT Software Business and Engineering Institute Primitive and Composite Models A Cell represents a primitive model Combination of Cells represent a Composite Model Cells can be combined horisontally or vertically but not diagonally HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 27 SoberIT Software Business and Engineering Institute Enterprise Architecture IFEAD: Wikipedia: 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. 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. HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 28 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 29 SoberIT Software Business and Engineering Institute Evolution of Frameworks HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 30 SoberIT Software Business and Engineering Institute Survey 2003: What EA are you using? HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 31 SoberIT Software Business and Engineering Institute The Open Group Architecture Framework (TOGAF) structure TOGAF Architecture Development Method The Enterprise Architecture Continuum The TOGAF Foundation Architecture TOGAF Technical Reference Model TOGAF Standards Information Base (SIB) The Integrated Information Infrastructure Reference Model TOGAF Resource Base HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 32 SoberIT Software Business and Engineering Institute The Open Group Architecture Framework (TOGAF) Business Architecture Data Architecture Applications Architecture Technical Architecture ADM Architecture Development Method Principles: How to develop good principles HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 33 SoberIT Software Business and Engineering Institute Architecture Development Cycle ADM is iterative Whole process Between phases Within phases For each iteration: The breath of coverage The level of detail Time horizon The architectural assets HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 34 SoberIT Software Business and Engineering Institute Architecture Development Cycle - Expansion Steps within phases Example phase D Output is generated throughout the process Versioning: Version numbers Early versions may be modified in later phases HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 35 SoberIT Software Business and Engineering Institute Mapping to the Zachman Framework HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 36 SoberIT Software Business and Engineering Institute Scope of TOGAF ADM Architecture domains Business Data Applications Technology Zachman rows Planner Owner Designer Builder HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 37 SoberIT Software Business and Engineering Institute Preliminary Phase: Framework and principles Framework definition Architecture principles Reference to: Business principles Business Goals Business Drivers HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 38 SoberIT Software Business and Engineering Institute Phase A: Architecture Vision Approved SOW Refined statements of Business principles Business Goals Strategic Drivers Architecture principles Architecture Vision Business baseline V1 Technical baseline V1 Business architecture V1 Technical architecture V1 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 39 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Gap analysis results Technical requirements Timo Itälä 40 SoberIT Software Business and Engineering Institute Phase C: Data Architecture Data Baseline description Target data architecture Conceptual data model Logical data model Data management process models Data entity/business function matrix Data interoperability requirements Other relevant viewpoints HELSINKI UNIVERSITY OF TECHNOLOGY Gap analysis results Timo Itälä 41 SoberIT Software Business and Engineering Institute Phase C: Applications Architecture Applications Baseline description Target applications architecture Process Systems Model Systems/Place Model People/Systems Model Systems/Time Model Applications interoperability requirements Other relevant viewpoints HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 42 SoberIT Software Business and Engineering Institute Phase D: Technology Architecture step 1 Create a baseline description in the TOGAF format Technology architecture principles Technology architecture V 0.1 - Constraints - Architecture principles - Requirements traceability: - key questions list - criteria for selection of service portfolio HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 43 SoberIT Software Business and Engineering Institute Phase D: Technology Architecture step 2 Consider different architecture reference models, viewpoints and tools Technology architecture V0.2 views HELSINKI UNIVERSITY OF TECHNOLOGY Networked computing Communications Processing Cost Standards Timo Itälä 44 SoberIT Software Business and Engineering Institute Phase D: Technology Architecture step 3 Create an architectural model of building blocks Technology architecture V0.3 views Networked computing Communications Processing Cost Standards HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 45 SoberIT Software Business and Engineering Institute Phase D: Technology Architecture step 4 Select the services portfolio required per building block Technology architecture V0.4 views Target services Change requests HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 46 SoberIT Software Business and Engineering Institute Phase D: Technology Architecture step 8 Technology architecture Version 1 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 47 SoberIT Software Business and Engineering Institute Composite mapping for phase D Technology architecture Version 1 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 48 SoberIT Software Business and Engineering Institute How to act upon the architecture? Opportunities and solutions Migration planning Implementation governance HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 49 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 50 SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 51 SoberIT Software Business and Engineering Institute The journey continues… John Zachman: Enterprise Architecture: Looking Back and Looking Ahead, 1999 In summary of the past Architecture is counter-cultural It is not perceived to be a survival issue by the Enterprise We don´t know how to actually do all of it It takes time and actual work Looking toward the future Architecture IS the information age culture Architecture IS an enterprise survival issue There are few theoretical breakthroughs left to be made There are no technical obstacles for doing architecture work HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 52 SoberIT Software Business and Engineering Institute 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 HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 53 SoberIT Software Business and Engineering Institute Questions? HELSINKI UNIVERSITY OF TECHNOLOGY Timo Itälä 54
