Arkkitehtuurisuunnittelun haasteet: tänään SOA ja Web Services, mitä huomenna?

Transkriptio

1 Arkkitehtuurisuunnittelun haasteet: tänään SOA ja Web Services, mitä huomenna? Sytyke laivaseminaari Lauri Keltikangas TietoEnator Digital Innovations

2 Agenda Esittäytyminen Arkkitehtuurisuunnittelun perusteet Mistä näkökulmasta asioita tarkastellaan Arkkitehtuurisuunnittelun nykyiset haasteet SOA ja Web Services mitä muuta? Arkkitehtuurisuunnittelun tulevat haasteet Mitä SOA:n ja Web Service:n jälkeen? Yhteenveto

3 TietoEnator Management Consulting Digital Innovations Management Consulting IT Strategy & Governance IT Architecture Project Management Banking & Insurance Telecom & Media Public & Healthcare Processing & Network Resource Management Production & Logistics Other units in Digital Innovations concentrate on: Digital Media Collaboration & content management support Management information EAI Project management methodologies Software Centres

4 Arkkitehtuurisuunnittelun perusteet

5 Asuinrakennusten kosteusvauriot esimerkki vääristä rakenneratkaisuista Sisällysluettelo Johdanto Sisäilma ja terveys Rakentaminen, rakennusmateriaalit ja remontointi Rakennusosat ja rakentaminen Ilmanvaihtojärjestelmät Remontointi Kosteusvaurioiden tunnistaminen ja korjaaminen Lämmitys Asiantuntija-apua Lisätietoja

6 Viikinranta ympäristöineen esimerkki liian raskaasta rakenneratkaisusta Kivimursketta 20m luvulla Savea 5m Peruskallio betonipaalut

7 IT/Process Development S Cycles Total business productivity architecture development old processes new processes Core system generation N+1 Phases of IT change cycle: Core system generation N I II III IV I Governance & sourcing actions II Core system renewal III Business process re-engineering IV Value capturing Time, years

8 Arkkitehtuurin kulmakivet Ydinprosessien tarpeisiin vastaavat liiketoimintasovellukset, joiden toiminnalliset päällekkäisyydet on karsittu minimiin Hyvin hallitut tietokannat (asiakkaat, tuotteet, tilaus/toimitus-tiedot) Viestinnän ja tietämyksenhallinnan verkko Sisäiset ja ulkoiset integrointipalvelut Liiketoiminnan joustavuus- ja hallintavaatimuksiin vastaavat alustat (ohjelmistot, laitteistot, tietoliikenne)

9 Enterprise IT Architecture All these aspects should be considered together - otherwise only very general guidelines can be given to a single issue Enterprise IT Architecture Information Systems Architecture Technical Architecture Applications & Databases What kind of applications and databases there are and what are their roles IT Service Architecture What are the required IT service components and how they are governed Technology & Infrastructure What are the standards and principles in application technology and infrastructure

10 Architecture Planks & Pillars Case:TietoEnator Processes TE common solutions Business applications BU specific DFR Common business components TE ERP Focus -intranet Application related infrastructure services Platforms, Infrastructure Technology, architecture

11 Enterprise IT Architecture Issues System of systems architecture Domain architect decisions Application architect decisions Enterprise architecture decisions Enterprise Scope Enterprise Architecture Domain Domain A Scope Domain B Scope Group IT Domain IT Application scope Component (Service) scope Component (Service) owner decisions System of components architecture IT Vendor Application Architecture Domain

12 Arkkitehtuurisuunnittelun nykyiset haasteet SOA ja Web Services mitä muuta?

13 In Our Hands Today in terms of acronyms ERP2 SME ERP EAI DW SOA web services J2EE /.NET XML Application integration Application & data data harmonization Networked components External networking Thick infrastructure services ebxml XML EDI access mgmt directories document mgmt SOA = Service-Oriented Archictecture DW = Data Warehouse EAI = Enterprise Application Integration SME ERP = Small & Medium Enterprise ERP

14 Service Oriented Architecture Motivation: Process integration Collaboration across borders Processes Scope Tasks Inter-enterprise XML/HTTP XML/HTTP Enterprise Large-grain bus. objects E-Services messaging messaging An application A Program Components Objects Tight Services Reuse Loose Coupling Typical access method Service-oriented architecture has been the best practice of systems engineering for long time. However, it has lacked standards and tools but web services are now changing the situation.

15 Framework for Architecture Development Real Time Enterprise Zero Latency Agility On Demand IT Utility IT Agility IT Service Market service components, service level agreements, vendor management Enterprise IT Architecture IT IT Service Service Architecture Architecture Web Services Business Business Development Development Priorities Priorities for for IT IT Development Development Information InformationSystems Architecture Architecture Technical TechnicalArchitecture Information Information & Communications CommunicationsTechnology SOA How are enterprises approaching these issues? ESB applicationmaps, key information sets, ownerships, development responsibilities data management, development tools, system management, data communication, security, hardware, operating systems

16 Architecture layers Case: TietoEnator Business applications Applications, application development, databases Security, I*Net (intra, inter, extra, portal), directories, integration, doc mgmt Workstations, servers, communication networks CIO i3o Identify common functional requirements -> Rationalise / Harmonise implementation roadmaps Application related infrastructure services SSO EAI Share CDS AD Portal Point Implement and enforce common application services IBB Platforms, Infrastructure MS Exchange MS Office Implement common infrastructure

17 Architect for IT Agility / IT Simplification IT Principles Architecture Patterns Source: HP

18 Architecture Patterns High volume transaction processing Real-time response Analytical & decision support Work group support Enterprise system Strategic drivers Product efficiencies Customer responsiveness Market segmentation Risk mgmt Knowledge sharing Integration & standardization Targets Cost savings Flexibility & growth Profitability Innovation Speed to market reuse Process improvement Key characters Integrating technology Paradigm Low unit cost Reliability Scalability Performance Data access Publish & subscribe Redundancy Ease of use Analytic engine Processing power Data convergence New code Middleware Data warehouse OLTP Digital services Ease of use Reliability High bandwidth Peer to peer Shared technology platform Vendor provided Data visibility Standardized processes Application module BI Groupware ERP source: MIT, Center of Information Systems Research

19 Arkkitehtuurisuunnittelun tulevat haasteet Mitä SOA:n ja Web Service:n jälkeen

20 DI Architecture Barometer - August 2004 BPM BPM B2B B2B digital digital services services ICT ICT governancnance gover- infra infra re-eng. re-eng. DW DW PMI PMI EAI EAI General interest Zone of serious planning Full-scale implementation

21 New Age BPM B2B e-business Business Process Fusion partner integration long processes new age BPM? web services EAI BPEL SOA

22 Hype Cycle for Application Integration and Platform Middleware, 2004 Source: Gartner Group 6/2004

23 Application Integration Landscape Methodologies and concepts Portals and BPM Business Processes Integration Products EAI/ETL Brokers and Adapters Orchestration - Composite applications ESOA Web Services Development environments Legacy applications New applications

24 Source: SAP

25 High-level vision of Business Process Management

26 Yhteenveto

27 Arkkitehtuurityön osa-alueet Right Things - Things Right Ymmärtäminen Kuvaaminen Ohjaaminen Miksi Mitä Miten analysis synthesis communication Tehdään oikeita asioita Tehdään asiat oikein Miten löydetään riittävä käsitys siitä mitkä ovat kokonaisuuden kannalta keskeisiä asioita? Miten arkkitehtuuripäätökset saadaan ohjaamaan yksittäisten kehittäjien ja projektien toimintaa?

28 Kiitokset mielenkiinnosta!