SC32 Liaison report to SC38 2010 Sept Plenary
Denise Warzel
JTC 1/SC 32/WG 2 Convenor
SC 32 Liaison to SC 38
SC 32 to SC 38 Liaison Notes
• The following presentation was discussed at SC 38 Plenary meeting in NY. Meeting notes are provided in WG2 N1471.
• Summary of the meeting is that SC 38 agreed that they would not reinvent any metamodel standards that are already part of SC 32 programme of work.
"Would you tell me, please, which way I ought to go from here?”
"That depends a good deal on where you want to get to," said the Cat.
-Lewis Carroll: Alice’s Adventures in Wonderland, 1865
Day 1 Objectives
• Develop a understanding regarding how SC 7, SC 38 and SC 32 standardization activities support Software Services
• Develop understanding of where SC 32/WG 2 Standards apply to SOA, Web Services and Cloud Computing (SaaS) standardization activities
ISO/IEC JTC 1/SC 32/WG 2 11179 Metadata Registries (MDR)19763 Metamodel Framework for Interoperability (MFI)
SC 07 ”Software Engineering"
SC 32 "Data management and interchange"
SC 38 ”Distributed Applications and Services"
Interoperability in SOA
“The capability to communicate, execute programs, or transfer data among various functional units in a manner that requires the user to have
little or no knowledge of the unique characteristics of those units". • ISO/IEC 2382, Information Technology Vocabulary – Part 1:
Fundamental Terms
Organizational Profiles Ripe for SOA:• Distributed systems that must interoperate• Systems are heterogeneous from a technology and/or ownership perspective• Costs (time and resources) for re-inventing or re-implementing is
no longer necessary or is unacceptable for any number of reasons
How do these ISO standardization programmes support SOA? Do they compliment each other?
• SC 7 Software Engineering
• ISO/IEC 10746 Reference Model for Open Distributed Processing (RM-ODP)
• Viewpoint Framework for designing Open Distributed Systems
• ISO/IEC UML4ODP • UML Profiles for ODP Viewpoint modeling
• ISO/IEC 12207 Software Lifecycle Management
• SC 32 Data Management and Interchange
• ISO/IEC 11179 Metadata Registries (MDR)• Registration and Classification of Data Semantics
• ISO/IED 19763 Metamodel Framework for Interoperability (MFI)
• Metamodels for interoperability for registration of Role, Goal, Process, Service and Services on Demand
What should SC 38 WG Web Services, SOA and Cloud Computing Focus on?
• SC38 Standard Language/Terms and definitions
• What is the difference between a (WG1) Web Service and an (WG2) SOA? Can either be hosted in the(WG3) Cloud?
• SC32 Standard Metamodel for Web, SOA and Cloud Computing Services
• How will customers know the difference?
• What attributes are needed?
What is a Service?
Information Science (eServices)• an interactive, content-centered and Internet-based customer service,
driven by the customer and integrated with related organizational customer support processes . [Ruyter, 2001]
• modular, nimble, electronic services that perform work, achieve tasks, or complete transactions. [Piccinelli, 2001]
In Computer Science (Web service)• loosely coupled, reusable software components that semantically
encapsulate discrete functionality and are distributed and programmatically accessible over standard Internet protocols. [The Stencil Group, 2001]
Which of these is SaaS?
From WG2 Discussion of MFI-7 Metamodel for Service Registration Wang Jian, He Keqing, He Yangfan, Wang Chong, SKLSE, Wuhan University, China 2009.8.21
SC 32 MFI-7 Service Definition
Modular functionality entity with provision of value that can be invoked by accessing its interface – 2009-09-08
From WG2 Discussion of MFI-7 Metamodel for Service Registration Wang Jian, He Keqing, He Yangfan, Wang Chong, SKLSE, Wuhan University, China 2009.8.2
SOA Characteristics SaaS, IaaS, PaaS, RaaS, …
• Standard Contracts• Coarse Grained
(Abstraction)• Appropriately Stateless• Loosely Coupled• Autonomous• Reusable• Discoverable• Composeable
SC 7 – Service Design
• RM-ODP and UML4ODP
(10746) (19763)
Meta Data
SC 32 WG 2 – Metamodels for Service and Data Semantics (Runtime)• Metadata Registry Standard – MDR (11179)• Metamodel Framework for Interoperability - MFI (19763)
Domain Specific Ontologies
* Service Profile Metadata (recorded in registry)
• Service Name• Purpose Description (Short)• Purpose Description (Detailed)• Service Model Type
• i.e. Entity Service, Utility Service, Task Service, Orchestration Task
• QoS Requirements • Performance, availability, transactions requirements
• Capabilities (see next slide)• Keywords (from domain specific ontology)• Version• Status
• currently provided, being worked on, planned, tentative
• + Estimated Delivery Date
• Custodian• ** Service Description Language• ?
* SOA Principals of Service Design, Thomas Erl 2008** from SC 32/WG 2 19763-7
* Capability Profile Metadata (recorded in registry)
• Capability Name• Purpose Description (Short)• Logic Description – step-by-step description of the logic (process)
• Algorithms, workflow diagrams, business process definitions• **Choreography, Exceptions, Resources]
• Input/Output • Reference to Schemas (annotated by 11179 URIs?)
• Composition role• Composition member capabilities
• Cross reference to other services this capability is dependent upon• **PreConditions/PostConditions]
• Mapped to business logic (Logic description)
• QoS Requirements• Keywords• Version• Status• Custodian
• ?* SOA Principals of Service Design, Thomas Erl 2008** from SC 32/WG 2 19763-7
Please think about how SC 7, SC 32, SC 38 can work in unison on these important emerging standards~
Thank you for coming! We hope to have a very productive meeting!
JTC 1/SC 32/WG 2 web site where current drafts Of 11179 and 19763 can be found:
http://www.metadata-standards.org
RGPS AND ON DEMAND MODEL SELECTION (ODMS)
SC 32 Liaison Report to SC 38 Cloud Computing WG
SC 32 Requests Liaison from SC 38 WG on Cloud Computing to SC 32
• Metamodels for describing services will be useful in the cloud to support service discovery. SC 32/WG 2 is working on ISO/IEC 19763 MFI family of standards that pertain to descriptions of services in a registry, RGPS (Role & Goal (Part 8), Process (Part 5), Service (Part 7)) and a methodology (On Demand Model Selection (ODMS) Part 9) for discovering services. The approach is to describe all services with a common metamodel, annotated with domain specific ontology to facilitate service discovery and reuse.
SC 32/WG 2 ISO/IEC 19763 Metamodel Framework for Interoperability (MFI) Family of Standards
RGPS
ODMS
Goal
- annotation
Operation
- annotation
Object
Service
Process
accomplishes
achieves
has
has
Role
serves for
0..*
0..*
0..*
0..1
0..*
0..10..*
1..1
1..1
Relationship with other parts in MFIRelationship with other parts in MFI
• Service metamodel is from MFI-7
• Process metamodel is from MFI-5
• annotation attributes are annotated by domain specific Ontology_Atomic_Construct from MFI-3
• Service metamodel is from MFI-7
• Process metamodel is from MFI-5
• annotation attributes are annotated by domain specific Ontology_Atomic_Construct from MFI-3
MFI-7MFI-7
MFI-5MFI-5
MFI-3MFI-3
MFI-8MFI-8
22
RGPS metamodel framework
Service
realizes
1..*
1..1
Actor Role
Goal
Role GoalPersonal Goal
Process
Functional Goal
NonFunctional Goal
takesCharge
achievescontributes
1..11..1
1..*
1..*
1..*
1..*
prefers
plays
1..1
1..*
1..*
1..*
RRRR
GGGG
PPPP
SSSS
RM-ODP
OMG-BMM
FOAF
NFRF
KAOS
…
Registration
Interoperation
Role & Goal Registry based on MFI-8
Common Facilities in MFI
Scope of MFI-8 (2/2)Scope of MFI-8 (2/2)
i*
register
Role & Goal Specifications
Models
Semantic annotation of models leads toOn Demand Model Selection (ODMS) 19763 Part-9
R&G
S
Service
Goal
Process
P
Domain Ontology
Object
hasOperation
Input
hasInput
Output
Semantic Annotation
Operation
Contribute to• mapping between models• semantic discovery of models
Resource
24
hasObject
hasOutput
hasResource
MFI-3MFI-8
MFI-5
MFI-7
Role
plays
Typical Model Selection Typical Model Selection Process (Case 1)Process (Case 1)
S
RG
P
Role
Goal
Process
ServiceUserUser
Input ： GoalExpected Output ：Service
25
How MFI-8 is constructedHow MFI-8 is constructed
• Harmonization of various Role & Goal models for registration
• FOAF (Friend of a Friend, FOAF project)
• RM-ODP (Reference Model of Open Distributed Processing, ISO-19793)
• NFRF (Non-functional Requirement Framework, Open Group)
• OMG-BMM (Business Motivation Model, OMG)
• KAOS (Keep All Objects Satisfied, Université catholique de Louvain)
• i* (Goal-oriented requirements modeling, University of Toronto)
• …
Decomposition
And
-annotation:Ontology_Atomic_Construct
Operation
-annotation:Ontology_Atomic_Construct
Object
Manner
0..*
1..1
1..1 0..*
1..1
0..1
-id : string-goal_type : Goal_Type-is_operational : bool
Goal
hasObject
Role_Goal
Personal_Goal
hasOperation
hasManner
Or
Constraint
ExcludeDepend
0..* 0..*
lower
source target
-id : string
Actor
-id : string
Role
1..1
1..*
1..*1..*
0..*
0..*
prefers
plays
takesCharge
upper
0..*interacts
-id : string
Organization
1..*
1..*
Equal Contribute
0..*
-description_language : string-namespace:URI
Role_Goal_Model
0..1
1..1 1..1
0..1
describes
describes
+Functional Goal+Nonfunctional Goal
<<Enum>> Goal_Type
Metamodel of Role & Goal Metamodel of Role & Goal registrationregistration
RoleRole
GoalGoal
Goal elementsGoal elements
Goal decompositionGoal decomposition
Constraint of GoalsConstraint of Goals
