ITU-T/SG 17 Mar 14 2004 1

UML for ODP system UML for ODP system specificationsspecifications

Bryan Wood Bryan Wood Convenor, JTC1/SC7/WG19Convenor, JTC1/SC7/WG19

Bryan.Wood@Open-IT.co.ukBryan.Wood@Open-IT.co.uk

ITU-T/SG 17 ITU-T/SG 17 Geneva, 14 March 2004Geneva, 14 March 2004

ITU-T/SG 17 Mar 14 2004 2

Use of UML for ODP system Use of UML for ODP system specifications - X.906 | ISO/IEC 19793specifications - X.906 | ISO/IEC 19793

A A standardstandard coveringcovering::• definition of a set of UML profiles for edefinition of a set of UML profiles for exxpressingpressing a a

system specification in terms of system specification in terms of ODP viewpoint ODP viewpoint specificationsspecifications

• relationships between the resultant ODP viewpoint relationships between the resultant ODP viewpoint specifications specifications

• relationships between a system specification using relationships between a system specification using ODP viewpoint specifications ODP viewpoint specifications and the and the OMG OMG Model Model

Driven ArchitectureDriven Architecture

ITU-T/SG 17 Mar 14 2004 3

The Reference Model of ODPThe Reference Model of ODPA framework for A framework for ODP standardization and system ODP standardization and system specificationspecification covering all aspects of distributed systems covering all aspects of distributed systems (“enterprise” context, functionality, infrastructure, (“enterprise” context, functionality, infrastructure, technology) and comprisingtechnology) and comprising

• a comprehensive and coherent set of object-oriented a comprehensive and coherent set of object-oriented modelling conceptsmodelling concepts

• a structure for specifications in terms of viewpoints a structure for specifications in terms of viewpoints on a systemon a system

• a language (concepts and rules) for expressing each a language (concepts and rules) for expressing each viewpoint specification viewpoint specification

ITU-T/SG 17 Mar 14 2004 4

Modelling conceptsModelling concepts

• Interpretation conceptsInterpretation concepts– entity, abstraction, system, architecture…entity, abstraction, system, architecture…

• Basic modelling conceptsBasic modelling concepts– object, action, environment (of an object), object, action, environment (of an object),

interface, activity, location (in space/time) …interface, activity, location (in space/time) …

• Specification conceptsSpecification concepts– composition/decomposition (of objects), type composition/decomposition (of objects), type

(of an <X>), <X>template, role …(of an <X>), <X>template, role …

ITU-T/SG 17 Mar 14 2004 5

Modelling conceptsModelling concepts• Organisational conceptsOrganisational concepts

– configuration (of objects), <X>group,configuration (of objects), <X>group,<X> domain…<X> domain…

• Properties of systems and objectsProperties of systems and objects– transparency, contracts, QoS, policy and prescriptions transparency, contracts, QoS, policy and prescriptions

on behaviour, …on behaviour, …

• Naming conceptsNaming concepts– Name, identifier, name space,name resolution…Name, identifier, name space,name resolution…

• Behaviour conceptsBehaviour concepts– activity structure, contractual behaviour, causality, activity structure, contractual behaviour, causality,

binding, dependability…binding, dependability…

ITU-T/SG 17 Mar 14 2004 6

ViewpointsViewpoints

• Different abstractions of the same systemDifferent abstractions of the same system– reflect different concernsreflect different concerns– expressed in terms of specific viewpoint concepts expressed in terms of specific viewpoint concepts

and rules (viewpoint languages) based on the and rules (viewpoint languages) based on the foundation modelling conceptsfoundation modelling concepts

• A mechanism for dealing with the complexity A mechanism for dealing with the complexity of distributed systemsof distributed systems

ITU-T/SG 17 Mar 14 2004 7

Viewpoint SpecificationsViewpoint Specifications

• Specifications of a system from different Specifications of a system from different viewpointsviewpoints– related and mutually consistentrelated and mutually consistent

• Using the viewpoint languages and the Using the viewpoint languages and the foundation modelling conceptsfoundation modelling concepts

ITU-T/SG 17 Mar 14 2004 8

ODP viewpoint specifications - ODP viewpoint specifications - different concernsdifferent concerns

SystemSystem

EnterpriseEnterprise

ComputationComputation

InformationInformation

TechnologyTechnologyEngineeringEngineering

ITU-T/SG 17 Mar 14 2004 9

The enterprise specificationThe enterprise specification• Specifies the roles played by an system in its Specifies the roles played by an system in its

organisational environmentorganisational environment• An object model of a social/commercial An object model of a social/commercial

organisation in terms of:organisation in terms of:– enterprise objectsenterprise objects– communities communities (of (of enterprise objectsenterprise objects))

• objectivesobjectives• behaviourbehaviour

– rolesroles – processesprocesses

• policypolicy

ITU-T/SG 17 Mar 14 2004 10

The information specificationThe information specification• Specifies system behaviour abstracted from Specifies system behaviour abstracted from

implementation implementation • An object model of the An object model of the systemsystem describing the describing the

semantics of information and of information semantics of information and of information processing in the processing in the systemsystem in terms of: in terms of:– information objectsinformation objects– invariant schemainvariant schema - predicates on - predicates on information information

objectsobjects that must always be true that must always be true – static schemastatic schema - state of - state of information objectsinformation objects at at

some some location in timelocation in time– dynamic schemadynamic schema - allowable state changes of - allowable state changes of

information objectsinformation objects

ITU-T/SG 17 Mar 14 2004 11

The computational specificationThe computational specification

• Specifies computational structure in terms of units Specifies computational structure in terms of units of distribution and portability and their interactions of distribution and portability and their interactions abstracted from the detail of how distribution is abstracted from the detail of how distribution is accomplishedaccomplished

• An object model of the An object model of the systemsystem describing the describing the structure of processing in terms of:structure of processing in terms of:

• computational objectscomputational objects• interfacesinterfaces: : operations supportedoperations supported• invocationsinvocations:: operations invokedoperations invoked• activitiesactivities:: sequences of invocationssequences of invocations• computational bindingscomputational bindings

ITU-T/SG 17 Mar 14 2004 12

The engineering specificationThe engineering specification• Specifies the mechanisms and services that Specifies the mechanisms and services that

provide the distribution transparencies and QoS provide the distribution transparencies and QoS constraints required by the system constraints required by the system

• An object model of the system describing the An object model of the system describing the infrastructure supporting the computational infrastructure supporting the computational structurestructure– basic engineering objectsbasic engineering objects– (infrastructure) engineering objects(infrastructure) engineering objects – clusters, capsules, nodesclusters, capsules, nodes – channelschannels– functionsfunctions

ITU-T/SG 17 Mar 14 2004 13

The technology specificationThe technology specification

• Specifies the procurable pieces Specifies the procurable pieces from which the system is built. from which the system is built.

• An object model of the systemAn object model of the system– defining the configuration of defining the configuration of technology objectstechnology objects and the and the

interfacesinterfaces between them that comprise between them that comprise the ODP systemthe ODP system

– identifyingidentifying conformance points conformance points

ITU-T/SG 17 Mar 14 2004 14

An ODP system specificationAn ODP system specification

- object configuration- object configuration- interactions- interactions between objects between objects at interfacesat interfaces

ComputationalComputational

EnterpriseEnterprise- business context- business context- business processes - business processes

- information- information- changes to information- changes to information- constraints- constraints

InformationInformation

EngineeringEngineering

- hardware and software componentshardware and software components implementing the system implementing the system

TechnologyTechnology

- mechanisms and services- mechanisms and services to provide the required to provide the required distribution transparencies distribution transparencies and QoS constraints.and QoS constraints.

ITU-T/SG 17 Mar 14 2004 15

ODP system specifications and UMLODP system specifications and UML

• RM-ODP defines clear and comprehensive concepts RM-ODP defines clear and comprehensive concepts and a framework supporting system specificationand a framework supporting system specification

• RM-ODP does RM-ODP does notnot define a notation for expressing a define a notation for expressing a system specificationsystem specification

• UML defines a notation for system specificationUML defines a notation for system specification

• UML does UML does notnot define clear and comprehensive define clear and comprehensive concepts and a framework supporting system concepts and a framework supporting system specificationspecification

ITU-T/SG 17 Mar 14 2004 16

UML Profiles for ODP Viewpoints UML Profiles for ODP Viewpoints

e.g. We don’t say “this class models Fred”We say “this class maps to this EO, whichmodels Fred”

Universeof Discourse

(UOD)

ODPViewpoint specification

UMLViewpoint model

UMLnotation

models

“ models” (notdefined)

maps to(through a profile)

expresses

“expresses” (not explicitly defined)

ITU-T/SG 17 Mar 14 2004 17

ODP system specifications and the ODP system specifications and the OMG Model Driven ArchitectureOMG Model Driven Architecture®®

A system specification that is compliant with the RM-ODP A system specification that is compliant with the RM-ODP also satisfies the requirements of the MDA®. Specifically:also satisfies the requirements of the MDA®. Specifically:

• the enterprise specification is a computation independent model the enterprise specification is a computation independent model (CIM)(CIM)

• the information, computational and engineering specifications the information, computational and engineering specifications together form a platform independent model (PIM), where clause together form a platform independent model (PIM), where clause 8 of the RM-ODP Part 3 defines a virtual machine which is the 8 of the RM-ODP Part 3 defines a virtual machine which is the context for platform independencecontext for platform independence

• the technology specification is a platform specific model (PSM)the technology specification is a platform specific model (PSM)

• the correspondences between the viewpoint specifications express the correspondences between the viewpoint specifications express the transformations by means of which one model is derived from the transformations by means of which one model is derived from another.another.

ITU-T/SG 17 Mar 14 2004 18

Who needs the standard?Who needs the standard?• Needed by system specifiersNeeded by system specifiers• Needed for communication between system Needed for communication between system

specifiersspecifiers• Needed for communication between stakeholders Needed for communication between stakeholders

and implementorsand implementors• Needed for a stable business functionality Needed for a stable business functionality

descriptiondescription– independent of technology and technology changeindependent of technology and technology change

• Needed for mission critical business systemsNeeded for mission critical business systems

ITU-T/SG 17 Mar 14 2004 19

SourcesSources

• Japanese Association of Healthcare Information Japanese Association of Healthcare Information System Industry (JAHSI) of a Japanese Hospital System Industry (JAHSI) of a Japanese Hospital Information Reference Enterprise ModelInformation Reference Enterprise Model

• European research projects:European research projects:– e.g. COMBINE - investigating the organisation and e.g. COMBINE - investigating the organisation and

process for component-based system developmentprocess for component-based system development

• Industrial Practice Industrial Practice • OMG OMG

– UML profile for Enterprise Distributed Object UML profile for Enterprise Distributed Object Computing (EDOC)Computing (EDOC)

ITU-T/SG 17 Mar 14 2004 20

Timetable - TargetsTimetable - Targets

• Start of ProjectStart of Project May 2003May 2003

• SC7 WDSC7 WD May 2004May 2004 SC7 meetingSC7 meeting

• 1st CD1st CD Dec 2004Dec 2004

• FCDFCD May 2005May 2005 SC7 meeting SC7 meeting

• FDISFDIS Dec 2005Dec 2005

• ISIS May 2006May 2006 SC7 meeting SC7 meeting

ITU-T/SG 17 Mar 14 2004 21

Questions ?Questions ?