caBIG

1
caBIG Architecture/ VCDE Joint WS F2F Meeting
Supporting ECCF and Service Semantics with ISO
Standards

• Oct. 21, 2009

2
Background/Introduction to BOF Session

• The goal of BOF is to introduce participants to
  ISO standards for software development that
  support ECCF 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 10746
• What is UML4ODP and what would you use it for?
• ISO 19793
• What is Metamodel Framework for Interoperability
  (MFI) RGPS (Role/Goal/Process/Service) and what
  would you use it for?
• ISO 19763
• Would they work together to support ECCF?
• Feeback?

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
• 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

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 and best
  practices?
• MDA? UML? BAM? DAM? 11179? 21090?
• What are the risks/weaknesses?

5
Introduction RM-ODP Reference Model-Open
Distributed Processing ISO 10746 5 Viewpoints
6
RM-ODP ISO 10746

• 4 Part Standard
• ISO/IEC 10746-1 Overview - a categorization of
  required areas of standardization expressed in
  terms of the reference points for conformance
  identified
• ISO/IEC 10746-2 Foundations - the definition of
  the concepts and analytical framework
• ISO/IEC 10746-3 Architecture - the specification
  of the required characteristics that qualify
  distributed processing as open.
• ISO/IEC 10746-4 Architectural semantics - a
  formalization of the ODP modelling concepts
• caBIG Standards wiki page https//wiki.nci.nih.g
  ov/x/IyAhAQ

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
  10746-1)
• 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.

8
Purpose of Viewpoint modeling

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

9
5 RM-ODP ViewpointsSupport different concerns
System
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 SpecificationCommunity Concepts
17
RM-ODP Enterprise SpecificationPolicy Concepts
18
Introduction UML4ODP ISO 19793
19
ISO 19793 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 https//wiki.nci.nih.g
  ov/x/IyAhAQ

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

21
RM-ODP and MDA
22
As a UML Specification
23
UML Profiles for each of the Viewpoints
Enterprise Viewpoint Profile
24
RM-ODP Enterprise Viewpoint metamodel
Process
Step
Role
Behaviour
Artifact
25
Enterprise Viewpoint UML constructs
Process
Role
Artifact
Step
Behaviour
26
(No Transcript)
27
Example of UML Profile/Sterotypes (ISO UML4ODP
19793)for Information Viewpoint
28
Introduction Metamodel Framework For
Interoperability (MFI) ISO 19763 RPGS
29
MFI-ISO 19763 RGPS

• Multi-Part Standard
• ISO/IEC 19763-1 Reference Model - a
  categorization of required areas of
  standardization expressed in terms of the
  reference points for conformance identified
• ISO/IEC 19763-3 Metamodel for Ontology
  Registration
• ISO/IEC 19763-5 Metamodel for Process Model
  Registration - facility to register
  administrative structural information and
  meaningful semantics of process models, including
  workflows, business processes, software processes
  etc.
• ISO/IEC 19763-7 Metamodel for Service
  Registration - facility to register
  administrative structural information and
  meaningful semantics of services
• ISO/IEC 19763-8 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/!EC19763-9 On Demand Service Selection
• caBIG Standards wiki page https//wiki.nci.nih.g
  ov/x/IyAhAQ

30
What would you use it for? On Demand Service
Selection

• Characterize services according to their purpose
• Make descriptions available programmatically
• Extend UDDI type service metadata
• Support SOA and Cloud service discovery and reuse

31
MFI RGPS 19763 metamodel framework
R
G
caGrid Service Index
P
S
32
MFI RGPS ISO 19763 Metamodel of Service
Registration
Capability_Related
Interface_Related
Interaction_Related
33
Metamodel of Role and Goal
33
34
Relationship between RGPS/ROR/Service
IaaS
PaaS
SaaS
XaaS
RGPS Registry
COPPA Service
End user
Service Index
caTissue Service
Developer
caArray Service
ROR
Registry
Registry
Registry
Registry
34
Manufacturing
Transportation
Healthcare
35
Applying RGPS for ServiceDiscovery ? Derived
from EV
Functional Goal
consistsOf
plays
Actor
Role
Organization
R
Semantic Annotation
prefers
takesCharge
Personal Goal
Role Goal
Entity Ontology
Goal
Nonfunctional Goal
Functional Goal
Operation Ontology
G
achieves
contributes
Context Ontology
Domain Ontologies
realizes
S
36
From the Perspective of W5H
consistsOf
plays
Actor
Role
Organization
Who
R
prefers
takesCharge
Semantic Annotation
Personal Goal
Role Goal
Goal
Entity Ontology
Why
Nonfunctional Goal
Functional Goal
Operation Ontology
G
achieves
contributes
When
Context Ontology
What
Where
realizes
Domain Ontologies
How
S
37
How might these work together?
38
ISO Project Editors meeting to harmonize 19763
MFI and 19793 UML4ODP
39
ISO 10746 RM-ODP
Enterprise Viewpoint
Information Viewpoint
Computational Viewpoint
Engineering Viewpoint
Technology Viewpoint
Masaharu OBAYASHI, HL7 WGM in Atlanta
(2009/09/24)
40
RM-ODP --- RGPS --- MDA
Role
Enterprise Viewpoint
Goal
Information Viewpoint
Computational Viewpoint
Process
Engineering Viewpoint
Service
Technology Viewpoint
Masaharu OBAYASHI, HL7 WGM in Atlanta
(2009/09/24)
41
Mapping UML4ODP (19793) to RGPS (19763)
42
ECCF for Software Specification?
Query/Discover/Compare
LexEVS Annotation
Create UML4ODP
Service Portfolio
Transform to XMI
19763 RGPS Service Metadata
Parse
Service Index
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-to-human interoperability, not
  machine-to-machine.
• A Future semantic infrastructure
• improving humanlt-gtmachine 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 ltgt 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 ?
• 1UML as an Ontology Modelling Language,
  Cranefield and Purvis