"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

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

Ripe for SOA?• Organizational profiles that fit SOA:• Distributed systems that must interoperate• Systems are heterogeneous from a technology and/or ownership perspective• For which the 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 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

SOA Characteristics SaaS

• Standard Contracts• Coarse Grained• Appropriately Stateless• Loosely Coupled• Autonomous• Reusable• Discoverable• Composeable

SC 7 – Service Design

• RM-ODP and UML4ODP

(10746) and (19763)

Meta Data

SC 32 WG 2 – Registration, 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

• ?

* SOA Principals of Service Design, Thomas Erl 2008

Capability Profile Metadata (recorded in registry)

• Capability Name• Purpose Description (Short)• Logic Description – step-by-step description of the logic

• Algorithms, workflow diagrams, business process definitions

• Input/Output • Reference to Schemas (annotated by 11179 URIs?)

• Composition role• Composition member capabilities

• Cross reference to other services this capability is dependent upon• Mapped to business logic (Logic description)

• QoS Requirements• Keywords• Version• Status• Custodian• ?

* SOA Principals of Service Design, Thomas Erl 2008

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!