cabig Architecture/ VCDE Joint WS F2F Meeting: Service Semantics Oct. 21, 2009

Transcription

1 cabig Architecture/ VCDE Joint WS F2F Meeting: Supporting ECCF and Service Semantics with ISO Standards Oct. 21,

2 Background/Introduction to BOF Session The goal of BOF is to introduce participants to ISO standards forsoftware development that supporteccf and facilitate the designing and building semantically interoperable systems What is Remote Open Distributed Processing (RM ODP) and what would you use it for? ISO What is UML4ODP and what would you use it for? ISO What is Metamodel Framework for Interoperability (MFI) RGPS (Role/Goal/Process/Service) and what would you use it for? ISO Would they work together to support ECCF? Feeback? 2

3 Supporting ECCF using ISO Standards BOF Session Goal of an Enterprise Conformance and Compliance Framework (ECCF) An approach to specifying software that enables independently developed systems to be quantitatively measured for conformance to a given specification ca Leverage what software developers already understand MDA and Unified Modeling Language (UML) Automatically derive services semantics from the software artifacts spit out metadata to be used to populate registries that support service discovery and use 3

4 Supporting ECCF using ISO Standards BOF Session Main Objective: How do we make it easy to understand and implement ECCF for internal and external software developers? Can ECCF artifacts be used to derive semantic infrastructure artifacts? Can ISO standards help? RM ODP (ISO 10746) and complimentary standard UML4ODP (ISO 19793) possible approach to produce machine formalized artifacts to populate semantic infrastructure Metamodel Framework for Interoperability (MFI/RGPS) (ISO 19763) metamodels for (Role, Goal, Process, Service) to support SOA and ECCF using artifacts from UML4ODP Can these with our existing standards d and best practices? MDA? UML? BAM? DAM? 11179? 21090? What are the risks/weaknesses?

5 Introduction RM-ODP Reference Model-Open Distributed ib t Processing ISO Viewpoints 5

6 RM-ODP ISO Part Standard: ISO/IEC : 1: Overview a categorization of required areasof standardization expressed in terms of the reference points for conformance identified ISO/IEC : Foundations the definition of the concepts and analytical framework ISO/IEC : Architecture the specification of the required characteristics that qualify distributed processing as open. ISO/IEC : Architectural semantics a formalization of the ODP modelling concepts cabig Standards wiki page: 6

7 What would you use it for? ECCF Software Specification Realize benefits of open systems Heterogeneous IT resources and multiple organizational domains Growing need to interconnect systems - Working Interoperability Environment characterized by Complexity (ISO ) Remoteness of the system i.e. Cloud Concurrency parts can execute concurrently Lack of global state state cannot be determined Partial Failures parts may fail at different times Asychrony cannot assume that parts will execute at a particulary/same time Heterogeneity different implementation platforms that can change over time Autonomy no single point of control Evolution parts change over time Moreover, since a single vendor will not have all of the answers, it is essential that the architecture, and any functions necessary to implement the architecture, be defined in a set of standards, so that multiple vendors can collaborate in the provision of distributed systems. 7

8 Purpose of Viewpoint modeling Different stakeholders see a system from different perspectives Managers, developers, maintainers, users, owner Many concerns that t need to be addressed d to achieve WI and shared services Functionality, security, distribution, heterogeneity, Viewpoint modeling is commonly used in other (more mature) engineering disciplines 1 Different maps for a building (floor plants, electricity, water conductions, heating system, etc.) Different maps for a city (physical, metro, buses, etc.) 8

9 5 RM-ODP Viewpoints Support different concerns System 9

10 How do the viewpoints interact?

11 RM-ODP Enterprise Viewpoint

12 RM-ODP Information Viewpoint

13 RM-ODP Computational Viewpoint

14 RM-ODP Engineering Viewpoint

15 RM-ODP Technology Viewpoint

16 RM-ODP Enterprise Specification Community Concepts 16

17 RM-ODP Enterprise Specification Policy Concepts 17

18 Introduction UML4ODP ISO

19 ISO UML4ODP Single Part Standard: ISO/IEC 19793: UML4ODP the expression of a system specification in terms of RM ODP viewpoint specifications using defined UML concepts and extensions cabig Standards wiki page: 19

20 What would you use it for? Formalize Software Specification Simplify creation of RM ODP specification Leverage MDA UML is widely adopted for information and systems design Utilize existing skills Use familiar technology to create UML formalism of software specification 20

21 RM-ODP and MDA

22 As a UML Specification

23 UML Profiles for each of the Viewpoints Enterprise Viewpoint Profile 23

24 RM-ODP Enterprise Viewpoint metamodel Process Step Role Behaviour Artifact

25 Enterprise Viewpoint UML constructs Process Role Artifact Step Behaviour

26

27 Example of UML Profile/Sterotypes (ISO UML4ODP 19793) for Information Viewpoint

28 Introduction Metamodel Framework For Interoperability (MFI) ISO RPGS 28

29 MFI-ISO RGPS Multi Part Standard: ISO/IEC : Reference Model a categorization of required areas of standardization d expressed in terms of the reference points for conformance identified ISO/IEC : Metamodel for Ontology Registration ISO/IEC : Metamodel for Process Model Registration facility to register it administrative structural information and meaningful semantics of process models, including workflows, business processes, software processes etc. ISO/IEC : Metamodel for Service Registration facility to register administrative structural information and meaningful semantics of services ISO/IEC : Metamodel for Role and Goal Registration facility to register administrative structural information and meaningful semantics of roles and goals [from RM ODP] enterprise viewpoint for services ISO/!EC : On Demand Service Selection cabig Standards wiki page: 29

30 What would you use it for? On Demand On Demand Service Selection Characterize services according to their purpose Make descriptionsavailable programmatically Extend UDDI type service metadata Support SOA and Cloud service discovery and reuse 30

31 MFI RGPS metamodel framework R G cagrid Service Index P S 31

32 MFI RGPS ISO Metamodel of Service Registration Capability_Relat ed Interface_Relate d Interaction_Related 32

33 Metamodel of Role and Goal 33 33

34 Relationship between RGPS/ROR/Service SaaS PaaS IaaS XaaS End user RGPS Registry COPPA Service Developer Service Index ROR catissue Service caarray Service Registry 34 Registry Healthcare Registry Transportation Registry Manufacturing 34

35 Applying RGPS for Service Discovery Derived from EV R G Actor Dynamic Context prefers Personal Goal Contextual Depend plays Profile Nonfunctional Goal contributes Contextual Expectation Role Goal consistsof Organization takescharge Role Goal Operation Object hasobject hasoperation Functional Goal achieves Input hasinput Process hasoutpu t Output Semantic Annotation Entity Ontology Operation Ontology ogy Context Ontology Functional Goal P S Atomic Process Message Contextual Property hasmessage Atomic Service Composite Process realizes Service Composite Service Domain Ontologies 35

36 From the Perspective of W5H Actor plays Role consistsof Organization Who R prefers Personal Goal takescharge Role Goal Semantic Annotation Goal Entity Ontology Why G Nonfunctional Goal contributes Functional Goal achieves Process Operation Ontology Context Ontology When What P Atomic Process Composite Process realizes Service Domain Ontologies Where How S Atomic Service Composite Service 36

37 How might these work together?

38 ISO Project Editors meeting to harmonize MFI and UML4ODP 38

39 ISO RM-ODP Enterprise Viewpoint Information Viewpoint Computational Viewpoint Engineering Viewpoint Technology Viewpoint Context (Environment) Interface among IT system IT system Interface between IT system and Context Conceptual Distributed and Collaborative PIM Platform Independent Model PSM Platform Specific Model 1 Implementation Masaharu OBAYASHI, HL7 WGM in Atlanta (2009/09/24)

40 RM-ODP --- RGPS --- MDA Enterprise Viewpoint Information Viewpoint Computational Viewpoint Role Goal Process IT system Context (Environment) Interface between IT system and Context Conceptual Distributed and Collaborative Engineering Viewpoint Technology Viewpoint Service Interface among IT system PIM Platform Independent Model PSM Platform Specific Model 1 Implementation Masaharu OBAYASHI, HL7 WGM in Atlanta (2009/09/24)

41 Mapping UML4ODP (19793) to RGPS (19763) 41

42 ECCF for Software Specification? Create UML4ODP LexEVS Annotation Query/Discover /Compare Transform to XMI Service Portfolio Parse RGPS Service Metadata Service Index 42

43 Motivation Factors and Background: Q: Why do we have to worry about interoperability? Why can't we just build stuff that works? The internet works. The internet is human-tohuman interoperability, not machine-to-machine. A: Future semantic infrastructure: improving human< >machine interactions providing the ability to query over open and dynamic collections of heterogeneous and distributed information sources increasing the accuracy of searches Reducing/transforming Data into Information, Knowledge Humans will build systems Cost and accuracy dependent on availability of metadata: Specification, information model, data dictionary, service descriptions, etc. Requires a formalism to enable human < > machine representation and interpretation ECCF is supposed to help us address the above the End Result is to Enable discovery of reusable and interoperable services Google search: Results 1 10 of about 20,600,000 for lung cancer More is not better