Enterprise Architecture (EA) Service-Oriented Architecture (SOA) Web Services Architecture (WSA)

Transcription

1 Enterprise Architecture (EA) Service-Oriented Architecture (SOA) Web Services Architecture (WSA) NorStella SOA-seminar Brian Elvesæter ICT 1

2 Outline What is an architecture? Enterprise architecture and enterprise modelling Interoperability Enterprise architecture and SOA Integration, SOA and Web services References ICT 2

3 What is an architecture? ICT 3

4 Different kinds of architectures Enterprise architecture Business architecture Conceptual architecture Functional architecture Architecture framework Realisation architecture Serviceoriented architecture ICT architecture Integration architecture Information architecture Knowledge architecture Logical architecture Web services architecture ICT 4

5 EA SOA WSA Enterprise architecture (EA) is the practice of applying a method for describing a current and/or future structure and behaviour 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. Holistic view of the enterprise and all its important assets. Service-oriented architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. [OASIS 2006] Architectural style for designing (technical) systems. Web services architecture (WSA) intends to provide a common definition for understanding Web services. A Web services architecture involves many layered and interrelated technologies. [W3C 2004] A set of enabling Web technologies for implementing software systems. ICT 5

6 IEEE Std IEEE Std IEEE Recommended Practice for Architectural Description of Software- Intensive Systems Adopted September 2000 Architecture definition Structure(s) of a system in terms of components, their externally visible properties, their relations, and the underlying principles Common frame of reference for architectural descriptions Common terminology architecture, architectural description, model, view, viewpoint, system, stakeholder, concern, ICT 6

7 Mission fulfills 1..* The fundamental organisation of a system embodied in its components, their relationships to each other and to the environment, and the principles guiding its design and evolution. Environment inhabits influences System has an Architecture provides Rationale Has interest in, or concerns relative to the system. has 1..* Concern identifies is important to 1..* used to cover 1..* 1..* Those interests which pertain the system s development, operation and other aspects that are critical or otherwise important to one or more stakeholders. 1..* is addressed to has Stakeholder Viewpoint has source 1..* Library viewpoint identifies selects 1..* conforms to * described by Architectural description organized by 1..* View participates in consists of establishes methods for 1..* 1..* Model The expression of a systems architecture with respect to a particular viewpoint. Addresses one or more of the concerns of the system stakeholder. participates in 1..* aggregates 1..* Developed using the methods established by its viewpoint, consisting of views expressing an architectural description. ICT 7

8 Architecture of what and for whom? Bus2 Bus1 Bus3 Bus4 Decomposition Virtual enterprise EA Actor1 SW syst1 Actor2 SW syst2 Business Decomposition SOA Comp2 Comp1 Comp3 Comp4 Software system Decomposition WSA Object2 Object1 Object3 Object4 Software component Datatype2 Datatype1 Operation1 Datatype3 Decomposition Software object ICT 8

9 Enterprise architecture and enterprise modelling ICT 9

10 History of enterprise architecture The major pioneering efforts: Zachman Framework - initiated 1978 ARIS tool set First Metis tool set Troux Knowledge Repository Four major approaches: Systems development case tools IT process modelling Product and process modelling Business process management Enterprise architecture modelling ICT 10

11 Why enterprise architecture? How can I involve my people in improving the performance of the business? How can I use best practices to ensure the success of the business?? How can I ensure that the IS technology helps the work of my people?? ICT 11

12 Governance with enterprise architecture Architecture is a strategic tool not just high-level design Architecture goes beyond ICT Enterprise architecture is a key component of the IT governance process at any organization of significant size. Stability and flexibility Seem to be contradictory, but a good architecture facilitates change! Communication with stakeholders architects, managers, customers, engineers, Analysis impact-of-change cost and performance Enterprise Architecture (EA) is a generic, abstracted and aggregated representation of the core structures and competences of an enterprise. EA supports laying out the main characteristics of the enterprise to be analysed and agreed before detailed technical design is started. It is shared and discussed enterprise-wide between all stakeholders as a common description forms, functions and features, components, properties and relationships. ICT 12

13 Role of enterprise architecture Mission Vision Strategy as is Goals to be enterprise architecture domain/aspect architectures Actions culture leadership people products processes Operations people IT Mark Lankhorst et al., "Enterprise Architecture at Work: Modelling, Communication and Analysis", Springer, 2005, ISBN: ICT 13

14 Describing coherence Information architecture? Product architecture Process architecture?? Application architecture? Technical architecture? Mark Lankhorst et al., "Enterprise Architecture at Work: Modelling, Communication and Analysis", Springer, 2005, ISBN: ICT 14

15 Enterprise modelling Enterprise modelling (EM) is a capability for externalising, making and sharing enterprise knowledge. EM tools can either be: used stand-alone to produce various kinds of model views, integrated as front-ends to other systems, part of an environment providing a contextual userenvironment. ICT 15

16 Enterprise modelling languages Enterprise modelling languages should allow building the model of an enterprise according to various points of view such as: function, process decision, economic, etc. in an integrated way. Languages defined at high level of abstraction as constructs for EM are independent of the technology of implementation Examples are: IEM Metis Enterprise Arcitecture Framework (MEAF) CIMOSA GRAI IDEF PSL WPDL XPDL BPML EDOC BPDM EPC Archimate ICT 16

17 Enterprise architecture frameworks Enterprises architecture frameworks are fundamental structures which allows defining the main sets of concepts to model and to build an enterprise. Architectural frameworks are designed to define views of specific enterprise domains. Frameworks lack capabilities for meta-data management role-driven viewing integration with platforms model-driven design generation of interoperable solutions Examples are: ZACHMAN GERAM GRAI ARIS CIMOSA DoDAF TOGAF TEAF Troux/Metis/AKM ISO MISSION ICT 17

18 Representations of architecture ARIS ZACHMAN GERAM EKA - POPS EN/ISO ATHENA NIST ICT 18

19 VA Enterprise Architecture DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why Based on work by John A. Zachman SCOPE (CONTEXTUAL) Things Important to the Business Processes Performed Business locations Important Organizations Ev ents Significant to the Business Business Goals and Strategy SCOPE (CONTEXTUAL) Zachman Framework Planner ENTERPRISE MODEL (CONCEPTU AL) Owner SYSTEM MODEL (LOGICAL) Designer TECHNOLOGY MODEL (PHYSICAL) Builder Entity = Class of Business Thing Function = Class of Business Process Node = Major Business Locations People = Major Organizations Semantic Model Business Process Business Logistics Work Flow Model Model System Ent = Business Entity Proc = Business Process Node = Business Location People = Organization Unit Rel = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Logical Data Model Application Architecture Distributed System Architecture Human Interface Architecture Ent = Data Entity Proc = Application Function Node = IS Function People = Role Rel = Data Relationship I/O = User Views Link = Line Characteristics Work = Deliv erable Physical Data System Technology Presentation Model Design Architecture Architecture Ent = Segment/Table Proc = Computer Function Node = Hardware/Softw are People = User Rel = Pointer/Key I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format DETAILED Data Program Network Security REPRESENTATIONS Definition (OUT-OF-CONTEXT) Architecture Architecture Sub-Contractor Ent = Field Proc = Language Statement Node = Addresses People = Identity Rel = Address I/O = Control Block Link = Protocols Work = Job FUNCTIONING ENTERPRISE Data Function Network Organization Time = Major Business Event Master Schedule Time = Business Event Cycle = Business Cycle Processing Structure Time = System Event Cycle = Processing Cycle Control Structure Time = Ex ecute Cycle = Component Cycle Timing Definition Time = Interrupt Cycle = Machine Cycle Schedule Ends/Means = Major Business Goals Business Plan End = Business Objective Means = Business Strategy Business Rule Model End = Structural Assertion Means = Action Assertion Rule Design End = Condition Means = Action Rule Design End = Sub-Condition Means = Step Strategy Planner ENTERPRISE MODEL (CONCEPTU AL) Owner SYSTEM MODEL (LOGICAL) Designer TECHNOLOGY MODEL (PHYSICAL) Builder DETAILED REPRESENTATIONS (OUT-OF-CONTEXT) Sub-Contractor FUNCTIONING ENTERPRISE Ent = Rel = DATA What Proc = I/O = FUNCTION How Node = Link = NETWORK Where People = Work = PEOPLE Who Time = Cycle = TIME When End = Means = MOTIVATION Why ICT 19

20 Enterprise Unified Process (EUP) ICT 20

21 Interoperability ICT 21

22 Interoperability research Project type: Network of Excellence (NoE) Full title: Interoperability Research for Networked Enterprises Applications and Software Project duration: 3 years Project budget: 12.0 M EU IST funding: 6.5 M Partners/contractors: 50 Start date: Nov 1, 2003 Web page: Project type: Integrated Project (IP) Full title: Advanced Technologies for Interoperability of Heterogeneous Enterprise Networks and their Applications Project duration: 3 years Project budget: 26.5 M EU IST funding: 14.4 M Partners/contractors: 19 Start date: Febr. 1, 2004 Web page: ICT 22

23 Rationale for interoperability Interoperability is the key to increase competitiveness of enterprises. Enterprise systems and applications need to be interoperable to achieve seamless operational and business interaction, and create networked organizations European Group for Research on Interoperability, 2002 Application integration license revenue System implementation budget B$ Misc. 20% Integration 40% Hardware 10% Imp. Services 20% Software 10% The cost of non-interoperability are estimated to (Source: the Yankee Group 2001) 40% of enterprises IT budget. ICT 23

24 Knowledge integration The originality of the projects are to take a multidisciplinary approach by merging three research areas supporting the development of Interoperability of Enterprise Applications and Software: Architecture & Platforms: to provide implementation frameworks, Enterprise Modelling: to define Interoperability requirements and to support solution implementation, Ontology: to identify Interoperability semantics in the enterprise. Architectures & Platforms ATHENA & INTEROP Enterprise Modelling Ontology ICT 24

25 4-layered view of an enterprise Business Operational Architecture Operations Strategy Governance Laws, rules, principles Agreed norms and practices Procedures and routines Business terms Enterprise Knowledge Architecture (EKA) Enterprise methodology Metamodels and languages Enterprise models Product models Enterprise templates Reference architectures Semantics Dictionaries Ontologies Nomenclatures Classifications Information and Communication Technology (ICT) Architecture Business and user services Infrastructure services EKA services Ontology tools Software platforms Modeling tools Management tools Ontology services ICT 25

26 Holistic approach to interoperability Enterprise A Enterprise B ICT Business Knowledge Application Data Semantics Business Knowledge Application Data Semantics Interoperability (def.) is the ability of two or more systems or components to exchange information and to use the information that has been exchanged IEEE Standard Computer Dictionary Communication To achieve meaningful interoperability between enterprises, interoperability must be achieved on all layers: Business layer: business environment and business processes Knowledge layer: organisational roles, skills and competencies of employees and knowledge assets ICT layer: applications, data and communication components Semantics: support mutual understanding on all layers ICT 26

27 Enterprise architecture and SOA ICT 27

28 Motivation for SOA Enterprise Challenges Business agility Flexibility and adaptability Enterprise architecture frameworks + Holistic approach + Different views of an enterprise as related (visual) knowledge models - Current enterprise architectures are only blueprints Requirements Enterprises require operational enterprise architectures ICT solutions must be designed to be inherently interoperable ICT Challenges Inflexible and difficult to adapt Enterprise application integration (EAI) Service-oriented architecture (SOA) + Architectural style + Loosely coupled systems + Horizontal integration between different business domains + Use case oriented service composition +/- Web services (enabling technology) ICT 28

29 Business and technology alignment Business Services can be seen as business capabilities that support the enterprise. Services usually represent a business function or domain. Services provide the units of business that represent value propositions within a value chain or within business processes. Traceability between the service as a business capability and its technical implementation. Services will improve delivery methods that are an integral part of the business product. Technology Modular design Compositions and granularity Services are loosely coupled From compile-time and deployment-time dependencies to run-time dependencies Dynamic discovery and binding Services are standardized ( platform independent ) Standard Internet and Web protocols as the common glue to provide syntactical interoperability ICT 29

30 Problems with current EA frameworks User's problems A lot of enterprise architecture proposals on the "market" However, it is usually difficult to understand, compare and choose Researcher's problems There is no justification, nor evaluation of existing enterprise architectures No adequate architecture representation language, too many different views and levels of detail Confusing notions between Enterprise Architecture, Enterprise Model, Enterprise Infrastructure Lack of standardized terminology and collaboration between different EA communities (system engineers, software engineering, ) Engineer's problems There is no "architecture continuity", it is difficult to transform an architecture from conceptual to implementation levels, and vice versa There is no "architecture interoperability", enterprise applications built on different architectures are not interoperable There is no scientific "architecture principles" like we have in the construction or shipbuilding domains, enterprise architecting is still a matter of experience ICT 30

31 ATHENA's approach to operational EA EA is the holistic expression of the enterprise s key business knowledge, information, application and technology strategies and their impact on business functions and processes, that: Guides investment strategies and decisions Provides the framework needed to innovate the business Consists of the current targeted Enterprise Knowledge Models (EKMs): EBA: Enterprise Business Architecture EKA: Enterprise Knowledge Architecture EIA: Enterprise information Architecture EAA: Enterprise Application Architecture ETA: Enterprise Technology Architecture Oversees integration across the core architectures that provides a synchronized set of EA artefacts that needs to be created, collected, organized and communicated to enable adaptation to change business and technology Is defined and deployed through the company-wide process councils ICT 31

32 Enterprise architecture viewpoints Integrates Across EBA,EKA,EIA, EAA (EA) Enterprise Business Architecture (EBA) Enterprise Knowledge Architecture (EKA) Enterprise Application & Architecture (EAA) Business Processes Information Flows (between processes) People, Teams, RAA Business Policy & Strategy Business Information Information Policy & Strategy Applications Application Data Data Flows (between Apps) Application Policy & Strategy Enterprise Technical Architecture (ETA) IT Platform and Infrastructure Hardware & OS SW Services & Middleware Productivity Apps. Technical Policy & Strategy ICT 32

33 From EM to Enterprise Visual Scenes (EVS) Utilizing the powers of visual enterprise knowledge scenes Redefining Enterprise Knowledge Modelling EM is externalizing and sharing enterprise knowledge, developing the enterprise knowledge architecture and enabling EVS. EKM is extending EM by Intelligent Infrastructure and knowledge architectures to support continuous enterprise architecting, business management and more. Different kinds of views to support process roles. Many kinds of diagrams Views can also be turned into and be models Four types of views: meta.- data, content, functional and context. Views have their specific view styles, and dependencies. ICT 33

34 Visual enterprise architecture management ICT 34

35 Enterprise architecture layers Integrated by intelligent infrastructures Inter-related reflective views of key roles replacing frameworks as mosaics of static kinds and types of views (the knowledge legacy from paper carriers) Layers, aspects: Logic and content: Business layer: Methods, models, operations, strategy, governance, Enterprise Knowledge Architecture (EKA) layer: POPS methods, EIS templates, UEML +++ EKA- POPS Law, rules, principles, agreed practices and norms, day to day routines User views (types and kinds), Enterprise-models and submodels, Meta-models: Languages, Structures and Type-hierarchies ICT architecture layer: Services as reusable tasks, servers and EKM repositories Access services, capabilities to integrate legacy systems, extract data, handle parameterised sub-models ICT 35

36 POP* dimensions The Process Dimension includes constructs related to activities, tasks and processes going on in the enterprise or between enterprises. The Organisation Dimension focuses on organisational structures, as well as members and positions thereof. Also, focus is set on interaction between structures, both as a whole and between members. The Decision Dimension is concerned with the collection of concepts and constructs that allow describing the decision-making structure in terms of decision centres and decision activities. The Product Dimension is used to model product architectures or product structures, for the purpose of design, development and engineering or product data management. The purpose of the Infrastructure Dimension is to support modelling of infrastructures and the services they provide. ICT 36

37 Mutually reflective views An object in one view will have reflections in other dimensions No orthogonal, layered meta-hierarchy No difference between modelling and metamodelling View connections and dependencies are designed or automatically created Types and kinds of views for each design role A content view for role A may be a definition view or functional view for role B Process Complex relationships, tasks, decisions Product ICT 37

38 Enterprise knowledge spaces Enterprise Knowledge Spaces (EKSs) are externalised knowledge spaces of four or more knowledge dimensions that contain mutual and complex dependencies of domains and elements in the four dimensions. ICT 38

39 Modelling Platform for Collaborative Enterprises (MPCE) Model-designed and generated working environments supporting concurrent design, planning and execution. Modelling tools Modelling Administration support services Services Administration Modelling support services services Repository management services The integrator of all systems and provider of new solutions Model-generated workplaces with business and user services. POP* enterprise model repository Integration Services Enterprises ICT infrastructures The ICT infrastructure is a platform of software component services. ICT 39

40 Model-designed and generated Workplaces Roles, users, pages, permissions, projects Modelling clients Client Menus Navigation Modules with Web UI - Page editor & runtime - Dynamic forms ed. & runtime - Problem tracker - Document uploader - Simple EKA text browser Reference models as EKA structures New Models POP* metamodel Server Storage MPCE Server (non-ui) modules -Permissions, users, groups, roles -Projects, portals, menus, navigation -File storage and retrieval -Model transformation services -EKA load, save, merge, etc MPCE Storage - with models as EKA structures -files -internal MPCE data as models File Repository (Blobs) EKA Object repository MPCE Web Services -update users, projects, roles, -update dynamic forms etc -load, save EKA etc Web Service Enactment -call other systems -return results for viewing ICT 40

41 Integration, SOA and Web services ICT 41

42 The waves of client/server technology First Wave Second Wave Third Wave Fourth Wave Fifth Wave File Servers Base Source: Client/Server Survival Guide, 1994 Robert Orfali, Dan Harkey OS/2 Edition, VNR Computer library + AJB update 2004 MDA, Web Services,.Net Distributed Server-side Service-oriented Objects componentsc Architecture OMG CORBA J2EE/EJB SOAP, XML COM/OLE COM+ WSDL/WSFL Web/Internett Corba Comp Java Agents, P2P FIPA Grid ICT 42

43 Web service Web service Applications identified by a URI, whose interfaces and bindings are capable of being defined, described and discovered as XML artefacts. A Web service supports direct interactions with other software agents using XML-based messages exchanged via Internet-based protocols. (W3C) SOA ~ architectural style Web services stack ~ technology/protocol standards SOA =/= Web services ICT 43

44 Web services architecture Web services can be used to implement serviceoriented solutions They adhere to the set of roles and operations specified by the service oriented model. They have also managed to establish a standardized protocol stack. ICT 44

45 WS-* stack to-be Simplified version of the to-be WS-* stack Families of related specs not expanded Competing spec families not shown Historical or abandoned specs not shown WS-Notification WS-Coordination WS-Addressing SOAP WSDL XML BPEL UDDI WS-Policy WS-ReliableMessaging WS-Federation WS-Security WS-CDL WS-Transfer WS-MetadataExchange WS-Resource ICT 45

46 WS-* stack as-is Complete version of the as-is WS-* stack The 3 widely-accepted specs today are the same as 5 years ago BPEL and WS-Security is gaining momentum Orchestration, discovery and brokering do not exist in today s world WS-Notification WS-Coordination WS-Addressing SOAP WSDL XML BPEL UDDI WS-Policy WS-ReliableMessaging WS-Federation WS-Security WS-CDL WS-Transfer WS-MetadataExchange WS-Resource ICT 46

47 Application architecture vs. SOA Segmented business areas Collaborative business areas a b c r x s x t SOA a r y b s y c t z y 1 y 2 z a b c r s t z x y z Application architecture Service-oriented architecture (SOA) ICT 47

48 SOA and integration Fundamental change for integration: X <-> Y Pre-SOA: outside, after development Post-SOA: inside, integral part of development / computational model Consequences How should integration be done? Innovation and experience Competition, expansion, consolidation Not understood: IDC Directions 2006 (3/2/06): SOA important but not understood or deployed as claimed Gartner (2/15/06): Globally, organizations placing minor emphasis on understanding the role of data integration in SOA and creation of data services at the foundation of their architectures ICT 48

49 History of integration : Integration = develop then integrate 1950s-1970s: Simple, manual integration 1970s-1980s: Distributed Computing Applications (interoperation) Databases (integrate) 1990s: Business Driven Integration concepts, technologies, and tools increased automation, internet-based computing Concepts: Workflows, Processes, Web, Integration solutions blossom (diverge): ETL, EAI, BPM, 2000: SOA Emerges 2000: Web services 2003: Integration solution evolution accelerates, vendor chaos ensues 2005: Growth in all integration categories ICT 49

50 Integration in SOA : Integration = dominant programming model : Wrapping : Re-Engineering : Consolidation : Research on Semantic SOA : Emergence of SOA Platforms and Solutions : Problem Solving Era: IT/integration relegated to low level function ICT 50

51 ICT 51

52 SOA platform consolidation Data and information integration Information Fabric EII: Enterprise information integration ETL: Extract, transform and load Application integration Integration Suite EAI: Enterprise application integration B2Bg: Business-to-business gateway ESB: Enterprise service bus Applications and Processes Business Process Management Suite BPM: Business process management B2Bi: Business-to-business integration Enterprise workplace Interaction Platform ICT 52

53 ICT 53

54 Integration suite services Goal: Composite applications Components: EAI, BPM, B2B, B2Bi Extensions: Adapter, collaboration, analysis, reporting, development, monitoring, contracts, SOA standards, ICT 54

55 Business process management suite & interaction services Goal: Continuous process improvement Components: BPM human-centric: people-intensive processes Integration-centric: system-intensive processes ICT 55

56 Information fabric services Goal: Holistic view of data (information virtualisation) Components: DBMS, EII + ETL + replication Extensions: Distributed meta-data repository, distributed data access, integrated data management ICT 56

57 Trends Consolidation comprehensive platforms Merging of Human Workflow and System Orchestration/Process services Integration of Business Rules Engines Support for Event Notification services (publish and subscribe) Integration of Model-generated workplaces and role/taskoriented user interfaces, user interaction services, portals, and multi-device interfaces Explicit use of models (Enterprise and System) Enterprise architecture + SOA ICT 57

58 References ICT 58

59 References [ATHENA] ATHENA, "ATHENA Home Page", ATHENA IP. [DnD] DnD, "Faggruppen for applikasjonsintegrasjon metoder og arkitektur", Den norske dataforening (DnD). [Elvesæter, et al. 2005] B. Elvesæter, R. K. Rolfsen, F. Lillehagen, and D. Karlsen, "Integrated Enterprise Service Architecture", in Proc. of the 12th ISPE International Conference on Concurrent Engineering (CE 2005), Fort Worth, Texas, USA, 2005, M. Sobolewski and P. Ghodous (Eds.), International Society for Productivity Enhancement, Inc., NY, USA, pp [INTEROP] INTEROP, "INTEROP Home Page", INTEROP NoE. [Lillehagen, et al. 2005] F. Lillehagen, D. Karlsen, H. G. Solheim, H. D. Jørgensen, H. Smith-Meyer, B. Elvesæter, and R. K. Rolfsen, "Enterprise Architecture - from Blueprints to Design Services", in Proc. of the 12th ISPE International Conference on Concurrent Engineering (CE 2005), Fort Worth, Texas, USA, 2005, M. Sobolewski and P. Ghodous (Eds.), International Society for Productivity Enhancement, Inc., NY, USA, pp [NESSI] NESSI, "Networked European Software & Services Iniative (NESSI)". [OASIS 2006] OASIS, "Reference Model for Service Oriented Architecture 1.0", OASIS, OASIS Standard, 12 October [W3C 2004] W3C, "Web Services Architecture", World Wide Web Consortium (W3C), W3C Working Group Note, 11 February ICT 59