ITU-T/SG 17 Mar UML for ODP system specifications Bryan Wood Convenor, JTC1/SC7/WG19 ITU-T/SG 17 Geneva, 14 March 2004

ITU-T/SG 17 Mar Use of UML for ODP system specifications - X.906 | ISO/IEC A standard covering: definition of a set of UML profiles for expressing a system specification in terms of ODP viewpoint specificationsdefinition of a set of UML profiles for expressing a system specification in terms of ODP viewpoint specifications relationships between the resultant ODP viewpoint specificationsrelationships between the resultant ODP viewpoint specifications relationships between a system specification using ODP viewpoint specifications and the OMG Model Driven Architecturerelationships between a system specification using ODP viewpoint specifications and the OMG Model Driven Architecture

ITU-T/SG 17 Mar The Reference Model of ODP A framework for ODP standardization and system specification covering all aspects of distributed systems (enterprise context, functionality, infrastructure, technology) and comprising a comprehensive and coherent set of object-oriented modelling conceptsa comprehensive and coherent set of object-oriented modelling concepts a structure for specifications in terms of viewpoints on a systema structure for specifications in terms of viewpoints on a system a language (concepts and rules) for expressing each viewpoint specificationa language (concepts and rules) for expressing each viewpoint specification

ITU-T/SG 17 Mar Modelling concepts Interpretation conceptsInterpretation concepts –entity, abstraction, system, architecture… Basic modelling conceptsBasic modelling concepts –object, action, environment (of an object), interface, activity, location (in space/time) … Specification conceptsSpecification concepts –composition/decomposition (of objects), type (of an ), template, role …

ITU-T/SG 17 Mar Modelling concepts Organisational conceptsOrganisational concepts –configuration (of objects), group, domain… Properties of systems and objectsProperties of systems and objects –transparency, contracts, QoS, policy and prescriptions on behaviour, … Naming conceptsNaming concepts –Name, identifier, name space,name resolution… Behaviour conceptsBehaviour concepts –activity structure, contractual behaviour, causality, binding, dependability…

ITU-T/SG 17 Mar Viewpoints Different abstractions of the same systemDifferent abstractions of the same system –reflect different concerns –expressed in terms of specific viewpoint concepts and rules (viewpoint languages) based on the foundation modelling concepts A mechanism for dealing with the complexity of distributed systemsA mechanism for dealing with the complexity of distributed systems

ITU-T/SG 17 Mar Viewpoint Specifications Specifications of a system from different viewpointsSpecifications of a system from different viewpoints –related and mutually consistent Using the viewpoint languages and the foundation modelling conceptsUsing the viewpoint languages and the foundation modelling concepts

ITU-T/SG 17 Mar ODP viewpoint specifications - different concerns System Enterprise Computation Information Technology Engineering

ITU-T/SG 17 Mar The enterprise specification Specifies the roles played by an system in its organisational environmentSpecifies the roles played by an system in its organisational environment An object model of a social/commercial organisation in terms of:An object model of a social/commercial organisation in terms of: –enterprise objects –communities (of enterprise objects) objectivesobjectives behaviourbehaviour –roles –processes policypolicy

ITU-T/SG 17 Mar The information specification Specifies system behaviour abstracted from implementationSpecifies system behaviour abstracted from implementation An object model of the system describing the semantics of information and of information processing in the system in terms of:An object model of the system describing the semantics of information and of information processing in the system in terms of: –information objects –invariant schema - predicates on information objects that must always be true –static schema - state of information objects at some location in time –dynamic schema - allowable state changes of information objects

ITU-T/SG 17 Mar The computational specification Specifies computational structure in terms of units of distribution and portability and their interactions abstracted from the detail of how distribution is accomplishedSpecifies computational structure in terms of units of distribution and portability and their interactions abstracted from the detail of how distribution is accomplished An object model of the system describing the structure of processing in terms of:An object model of the system describing the structure of processing in terms of: computational objectscomputational objects interfaces: operations supportedinterfaces: operations supported invocations:operations invokedinvocations:operations invoked activities:sequences of invocationsactivities:sequences of invocations computational bindingscomputational bindings

ITU-T/SG 17 Mar The engineering specification Specifies the mechanisms and services that provide the distribution transparencies and QoS constraints required by the systemSpecifies the mechanisms and services that provide the distribution transparencies and QoS constraints required by the system An object model of the system describing the infrastructure supporting the computational structureAn object model of the system describing the infrastructure supporting the computational structure –basic engineering objects –(infrastructure) engineering objects –clusters, capsules, nodes –channels –functions

ITU-T/SG 17 Mar The technology specification Specifies the procurable pieces from which the system is built.Specifies the procurable pieces from which the system is built. An object model of the systemAn object model of the system –defining the configuration of technology objects and the interfaces between them that comprise the ODP system –identifying conformance points

ITU-T/SG 17 Mar An ODP system specification - object configuration - interactions between objects between objects at interfaces at interfacesComputational Enterprise - business context - business processes - information - changes to information - constraints Information Engineering - hardware and software components implementing the system Technology - 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 ODP system specifications and UML RM-ODP defines clear and comprehensive concepts and a framework supporting system specificationRM-ODP defines clear and comprehensive concepts and a framework supporting system specification RM-ODP does not define a notation for expressing a system specificationRM-ODP does not define a notation for expressing a system specification UML defines a notation for system specificationUML defines a notation for system specification UML does not define clear and comprehensive concepts and a framework supporting system specificationUML does not define clear and comprehensive concepts and a framework supporting system specification

ITU-T/SG 17 Mar UML Profiles for ODP Viewpoints e.g. We dont say this class models Fred We say this class maps to this EO, which models Fred Universe of Discourse (UOD) ODP Viewpoint specification UML Viewpoint model UML notation models models (not defined) maps to (through a profile) expresses expresses (not explicitly defined)

ITU-T/SG 17 Mar ODP system specifications and the OMG Model Driven Architecture® A system specification that is compliant with the RM-ODP also satisfies the requirements of the MDA®. Specifically: the enterprise specification is a computation independent model (CIM)the enterprise specification is a computation independent model (CIM) the information, computational and engineering specifications together form a platform independent model (PIM), where clause 8 of the RM-ODP Part 3 defines a virtual machine which is the context for platform independencethe information, computational and engineering specifications together form a platform independent model (PIM), where clause 8 of the RM-ODP Part 3 defines a virtual machine which is the context 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 transformations by means of which one model is derived from another.the correspondences between the viewpoint specifications express the transformations by means of which one model is derived from another.

ITU-T/SG 17 Mar Who needs the standard? Needed by system specifiersNeeded by system specifiers Needed for communication between system specifiersNeeded for communication between system specifiers Needed for communication between stakeholders and implementorsNeeded for communication between stakeholders and implementors Needed for a stable business functionality descriptionNeeded for a stable business functionality description –independent of technology and technology change Needed for mission critical business systemsNeeded for mission critical business systems

ITU-T/SG 17 Mar Sources Japanese Association of Healthcare Information System Industry (JAHSI) of a Japanese Hospital Information Reference Enterprise ModelJapanese Association of Healthcare Information System Industry (JAHSI) of a Japanese Hospital Information Reference Enterprise Model European research projects:European research projects: –e.g. COMBINE - investigating the organisation and process for component-based system development Industrial PracticeIndustrial Practice OMGOMG –UML profile for Enterprise Distributed Object Computing (EDOC)

ITU-T/SG 17 Mar Timetable - Targets Start of ProjectMay 2003Start of ProjectMay 2003 SC7 WDMay 2004SC7 meetingSC7 WDMay 2004SC7 meeting 1st CDDec 20041st CDDec 2004 FCDMay 2005 SC7 meetingFCDMay 2005 SC7 meeting FDISDec 2005FDISDec 2005 ISMay 2006 SC7 meetingISMay 2006 SC7 meeting

ITU-T/SG 17 Mar Questions ?