Towards an Interoperability Framework for Model-Driven Development of Software Systems

Transcription

1 Towards an Interoperability Framework for Model-Driven Development of Software Systems INTEROP-ESA 05 Session IT1 : Industrial Track Brian Elvesæter 1, Axel Hahn 2, Arne-Jørgen Berre 1, Tor Neple 1 1 SINTEF, P. O. Box 124 Blindern, N-0314 Oslo, Norway {brian.elvesater, arne.j.berre, tor.neple}@sintef.no 2 Wirtschaftsinformatik Universität Oldenburg, D Oldenburg, Germany hahn@wi-ol.de

2 Background Research sponsored by ATHENA IP INTEROP NoE Challenges To address interoperability for enterprise applications and software. Research focus on Model-Driven Development (MDD), in particular OMG s Model Driven Architecture (MDA ) Interoperability Framework for MDD To provide guidance on how MDD should be applied to address interoperability.

3 Motivation We believe that there is a need for an interoperability framework that provides guidance on how MDD should be applied to address interoperability. The interoperability framework integrates principles of model-driven, service-oriented and adaptive architectures: Model-driven architectures focus on design-time aspects of system engineering. Model-driven development methodologies describe how to develop and utilise (visual) models as an active aid in the analysis, specification, design and implementation phases of an system. Service-Oriented Architecture (SOA) specifies systems composed of services offered by various service providers, which provides the basis for supporting new business models, such as virtual organisations. Adaptive interoperability architectures focus on run-time aspects of system engineering. Agent and P2P technologies enrich an system with dynamic and adaptive qualities.

4 Model -Driven Model -Driven & Architecture -Driven Architecture -Driven Model-Driven Model -Driven & Interoperability Framework The interoperability framework itself is structured according to three main integration areas defined in ATHENA: 1. Conceptual integration which focuses on concepts, meta-models, languages and model relationships to systemise software model interoperability. 2. Technical integration which focuses on the software development and execution environments. 3. Applicative integration which focuses on methodologies, standards and domain models. It provides us with guidelines, principles and patterns that can be used to solve software interoperability issues. Conceptual Integration Enterprise System A (MDD Abstraction) Computational Independent Model (CIM) Ontologies Computational System A Technical Integration Applicative Integration For each of these three areas we developed a reference model to describe and support the application of model-driven development of software systems. Platform Independent Model (PIM) Platform Specific Model (PSM) Execution Platform A Model Transformation Enterprise A (Technical World) Transactions Tasks Collaborations Processes Users Vertical Integration User Interface Services UserServices Services Resource Services Software System Reference Ontology Process Aspects Service Aspects Horizontal MI Vertical Integration MI Interoperability Patterns Information Aspects Integration Non - Functional Aspects Model Interoperability Infrastructure Model Service Exec. Data Mgmt. Mgmt. Mgmt. Mgmt. Registry/Repository Infrastructure Services Enterprise System B (MDD Abstraction) Computational Independent Model (CIM) Ontologies Platform Independent Model (PIM) Platform Specific Model (PSM) Execution Platform B Computational System B Model Transformation Enterprise B (Technical World) Transactions Collaborations Tasks Processes Users Vertical Integration Resource Services Services UserServices User Interface Services Software System Model Transformation Models of Service, Information Process and Non-Functional Aspects Models of other Enterprise Aspects Software System Computational System A Realisation Models Execution Platform A Platform Specific Model (PSM) Software Model Resource Services Services User Services User Interface Services Specification Models Model -Driven Vertical Integration Platform Independent Model (PIM) Users Context Models Processes Collaborations Tasks Ontologies Model -Driven & Enterprise Model Transactions Computational Independent Model (CIM) Enterprise System A (MDD Abstraction) Enterprise Architecture A (Model World) Enterprise A (Technical World)

5 Conceptual Integration Overview Developed from a MDD point of view focusing on the enterprise applications and software system. A Computation independent model (CIM) corresponds to a view defined by a computation independent viewpoint. It describes the business context and business requirements for the software system(s). A platform independent model (PIM) corresponds to a view defined by a platform independent viewpoint. It describes software specifications independent of execution platforms. A platform specific model (PSM) corresponds to a view defined by a platform specific viewpoint. It describes the realisation of software systems.

6 Conceptual Integration: Reference Model Enterprise System A (MDD Abstraction) Enterprise System B (MDD Abstraction) Ontologies Computational Independent Model (CIM) Model-Driven & Reference Ontology Interoperability Patterns Ontologies Computational Independent Model (CIM) Model-Driven & Model-Driven Platform Independent Model (PIM) Platform Specific Model (PSM) Service Aspects Horizontal Process Aspects Vertical Integration MI Information Aspects Integration Non - Functional Aspects Model-Driven Platform Independent Model (PIM) Platform Specific Model (PSM) Execution Platform A Computational System A Execution Platform B Computational System B Model Transformation MI Model Interoperability Model Transformation

7 Conceptual Integration: System Aspects We have identified four categories of system aspects where specific software interoperability issues can be addressed. These four aspects can be addressed at all three CIM, PIM and PSM levels. 1. Service aspects: Services are an abstraction and an encapsulation of the functionality provided by an autonomous entity,. 2. Information aspects: Information aspects are related to the messages or structures exchanged, processed and stored by software systems or software components. 3. Process aspects: Processes describe sequencing of work in terms of actions, control flows, information flows, interactions, protocols, etc. 4. Non-functional aspects: Extrafunctional qualities that can be applied to services, information and processes. We have been studying the following metamodels. CIM level Process Definition Metamodel (BPDM) Software Process Engineering Metamodel (SPEM) POP* (being defined within ATHENA) PIM level EDOC UML Profile for Enterprise Distributed Object Computing Specification QoS UML Profile for Modelling Quality of Services and Fault Tolerance Characteristics and Mechanisms PSM level Web Services Web Services Process Execution Language (WSBPEL) Agents Architectures Peer2Peer Architectures

8 Technical Integration Overview Developed from a service-oriented point of view where a software system provides a set of services required by the businesses and users of the enterprise. The architecture of the enterprise applications and software systems can be described according to a 4-tier reference architecture where each tier provides different software services required by the enterprise. The software system itself is coupled to a service bus that provides the necessary communication infrastructure. Infrastructure services such as composition, mediation, matchmaking and transformation that enables interoperability between software systems should be provided. Model repository for managing models of various kinds. Service registry for managing naming, directory and location of services Execution repository for managing information and state needed in the execution of software services and processes Data repository for managing results and traces of the executions.

9 Technical Integration: Reference Model Enterprise A (Technical World) Enterprise B (Technical World) Transactions Transactions Tasks Processes Collaborations Processes Collaborations Tasks Users Infrastructure Users Vertical Integration Vertical Integration Model Mgmt. Service Mgmt. Exec. Mgmt. Data Mgmt. User Interface Services User Services Services Resource Services Registry/Repository Resource Services Services User Services User Interface Services Software System Infrastructure Services Software System

10 Technical Integration: 4-tier reference architecture User Service Domain User Interface Tier User Service Tier LA LS Service Domain Service Tier Resource Service Tier RA RA Legend LA Service Local Adapter LS RA Local Storage Resource Adapter Database Inter-service communication (Middleware Services)

11 Applicative Integration Overview Developed based on work related to enterprise architecture frameworks and software architecture frameworks. Enterprise and software models can be related in a holistic view, regardless of modelling language formalisms, by the use of metamodels. The MDD methodology needs to follow a structured approach where interoperability requirements from business operations in a networked enterprise drive the development of software solutions. An enterprise model describes a set of enterprise aspects, which includes descriptions of the business operations of the business models. Software models describe how software systems are used to support the businesses of an enterprise. All these models should include descriptions of the four system aspects identified in the reference model for conceptual integration.

12 Applicative Integration: Reference Model Enterprise System A (MDD Abstraction) Enterprise Architecture A (Model World) Enterprise A (Physical World) Ontologies Computational Independent Model (CIM) Model-Driven & Platform Independent Model (PIM) Context Models Enterprise Model Transactions Processes Collaborations Tasks Users Model-Driven Specification Models Vertical Integration Platform Specific Model (PSM) Execution Platform A Computational System A Model Transformation Realisation Models Software Model Models of Service, Information Process and Non-Functional Aspects Models of other Enterprise Aspects Resource Services Services User Services User Interface Services Software System

13 SOI - emittertype COP Addressee Main frequencies cryptokeys Frequency requirements -usage[send,receive,...] - securitylabel[(nato) unclassified, restricted, confidential, secret] - class of station(mobile, point-point, ground-air) Telephone Directory Decoding list Frequencies - nettid Subnet Applicative Integration: Three Basic Viewpoints ARCADE system COPdistributor Lower Echelon Unit Joint Level FOFAS bør kunne oppdatere ARCADE ARCADE data : COP Actual and planned draft TASKORG : Frequency requirements From Div 6, FO/I, KA mobile avd, LV final TASKORG : Frequency requirements verified list : Frequencies temp verified list : Frequencies Receive ARCADE data Establish/maintain frequency pool Receive COP new operation Frequency Verify list list : Frequencies newcampaign Verify security level Receive from frequency lower level requirements Generate Frequency list temporary list : Frequencies newcampaign new operation Distribute Distribute temporary Frequency list Frequency list View Analyst Viewpoint e.g. Process Model Specification Viewpoint Realisation Viewpoint Deployed Unit #1 Command Center InformationService#1 Radio InformationService#2 Satelite e.g. Service & Interface Model Information Deployed Unit #2 NotificationService inotification ipublish ProcessingService iprocess Information Ethernet Specification View System Architect Legend Networked Enterprise Software System e.g. Interaction & Data Model - emissointype - area - class of station[mobile, point-point, ground-air] - timerange - emittertype - frequency - emissiontype - area(polygon, circle) op1 op2 - netttype - name - frequency - frequencychangetime - newfrequency - frequencyfmprai - frequencydigpray - areacode - KVTid - KVTchangeTime Realisation View Software Developer

14 Future Work (1/2) Conceptual Integration We will develop a metamodel for Service-Oriented Architectures and a corresponding UML 2.0 Profile at the PIM level. The metamodel will address the four system aspects identified: 1. Service aspects 2. Information aspects 3. Process aspects 4. Non-functional aspects Applicative Integration We will develop interoperability profiles that provide specific guidelines for how to apply model-driven development of software systems in four different business domains: 1. Supply chain management where stable supply chains and dynamic supply networks will be considered. 2. Collaborative product development in which cross-functional and crossorganisational teams collaborate in product development. 3. e-procurement focusing on electronic purchasing and selling of goods and services. 4. Portfolio management focusing on project classifications, selection, prioritisation, and resource allocation.

15 Future Work (2/2) Technical Integration We will develop an integrated execution infrastructure that enables different platforms to interoperate in a Service-Oriented Architecture. Service Wrappers (Enterprise X) Service Wrappers (Enterprise Y) Public Infrastructure Services Crossorg. Registry Repository Service Wrappers (Enterprise A) Evaluation & Negotiation of Available Functionality Intraorg. Internal Infrastructure Services Process Execution Platform (BPEL) Goal-oriented Adaptive Execution Platform (Agents) Active Model Platform (AKMii) Composed WebService Platform (WebServices) Legend Adaptive Distributed Resource Mgt Platform (P2P) Enhanced Service Interconnection Bus Process/Agent Active () Model Web/Server Component Server-side Component Platform (.NET, J2EE) Message- Oriented Platform (MQSeries) Existing Enterprise Applications Middleware Process/Agent Middleware Component

16 Questions?