BryanWood@Open-ITcouk.ppt

UML for ODP system specificationsBryan Wood ConvenorConvenor,JTC1/SC7/WG19,JTC1/SC7/WG19Bryan.WoodOpen-IT.co.ukBryan.WoodOpen-IT.co.ukITU-T/SG 17 ITU-T/SG 17 Geneva,14 March 2004Geneva,14 March 2004ITU-T/SG 17 Mar 14 20041Use of UML for ODP system specifications-X.906|ISO/IEC 19793A standard covering:definition of a set of UML profiles for edefinition of a set of UML profiles for ex xpressingpressing 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 20042The 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 comprisinga comprehensive and coherent set of object-oriented a comprehensive and coherent set of object-oriented modelling modelling conceptsconceptsa structure for specifications in terms of viewpoints a structure for specifications in terms of viewpoints on a systemon a systema 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 20043Modelling conceptsInterpretation conceptsentity,abstraction,system,architectureentity,abstraction,system,architectureBasic modelling conceptsobject,action,environment(of an object),object,action,environment(of an object),interface,activity,location(in space/time)interface,activity,location(in space/time)Specification conceptscomposition/decomposition(of objects),type composition/decomposition(of objects),type(of an),template,role(of an),template,role ITU-T/SG 17 Mar 14 20044Modelling conceptsOrganisational conceptsOrganisational concepts configuration(of objects),group,configuration(of objects),group,domain domainProperties of systems and objectsProperties of systems and objects transparency,contracts,transparency,contracts,QoSQoS,policy and prescriptions,policy and prescriptions on behaviour,on behaviour,Naming conceptsNaming concepts Name,identifier,name space,name resolutionName,identifier,name space,name resolutionBehaviour conceptsBehaviour concepts activity structure,contractual behaviour,causality,activity structure,contractual behaviour,causality,binding,dependabilitybinding,dependabilityITU-T/SG 17 Mar 14 20045ViewpointsDifferent abstractions of the same systemreflect different concernsreflect different concernsexpressed 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 foundationfoundation modelling modelling conceptsconceptsA mechanism for dealing with the complexity of distributed systemsITU-T/SG 17 Mar 14 20046Viewpoint SpecificationsSpecifications of a system from different viewpointsrelated and mutually consistentrelated and mutually consistentUsing the viewpoint languages and the foundation modelling conceptsITU-T/SG 17 Mar 14 20047ODP viewpoint specifications-different concernsSystemEnterpriseEnterpriseComputationComputationInformationInformationTechnologyTechnologyEngineeringEngineeringITU-T/SG 17 Mar 14 20048The enterprise specificationSpecifies the roles played by an system in its Specifies the roles played by an system in its organisational organisational environmentenvironmentAn object model of a social/commercial An object model of a social/commercial organisation organisation in terms of:in terms of:enterprise objectsenterprise objects communities communities(of(of enterprise objectsenterprise objects)objectivesobjectives behaviourbehaviour rolesroles processesprocesses policypolicyITU-T/SG 17 Mar 14 20049The information specificationSpecifies system Specifies system behaviour behaviour abstracted from 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 200410The computational specificationSpecifies computational structure in terms of units of Specifies computational structure in terms of units of distribution and portability and their interactions distribution and portability and their interactions abstracted from the detail of how distribution is abstracted from the detail of how distribution is accomplishedaccomplishedAn 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 200411The engineering specificationSpecifies the mechanisms and services that Specifies the mechanisms and services that provide the distribution transparencies and provide the distribution transparencies and QoS 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 functionsfunctionsITU-T/SG 17 Mar 14 200412The technology specificationSpecifies 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 pointsITU-T/SG 17 Mar 14 200413An ODP system specification-object configuration-object configuration-interactions-interactions between objects between objects at interfaces at interfacesComputationalComputationalEnterpriseEnterprise-business context-business context-business processes-business processes-information-information-changes to information-changes to information-constraints-constraintsInformationInformationEngineeringEngineering-hardware and software componentshardware and software components implementing the system implementing the systemTechnologyTechnology-mechanisms and services-mechanisms and services to provide the required to provide the required distribution transparencies distribution transparencies andand QoS QoS constraints.constraints.ITU-T/SG 17 Mar 14 200414ODP system specifications and UMLRM-ODP defines clear and comprehensive concepts RM-ODP defines clear and comprehensive concepts and a framework supporting system specificationand a framework supporting system specificationRM-ODP does RM-ODP does notnot define a notation for expressing a define a notation for expressing a system specificationsystem specificationUML defines a notation for system specificationUML defines a notation for system specificationUML does UML does notnot define clear and comprehensive define clear and comprehensive concepts and a framework supporting system concepts and a framework supporting system specificationspecificationITU-T/SG 17 Mar 14 200415UML Profiles for ODP Viewpoints e.g.We dont say“this class models Fred”We say“this class maps to this EO,whichmodels Fred”Universeof Discourse(UOD)ODPViewpoint specificationUMLViewpoint modelUMLnotationmodels“models”(notdefined)maps to(through a profile)expresses“expresses”(not explicitly defined)ITU-T/SG 17 Mar 14 200416ODP system specifications and the OMG Model Driven ArchitectureA A system system specification specification that that is is compliant compliant with with the the RM-ODP RM-ODP also satisfies the requirements of the MDA.Specifically:also satisfies the requirements of the MDA.Specifically:the the enterprise enterprise specification specification is is a a computation computation independent independent model model(CIM)(CIM)the the information,information,computational computational and and engineering engineering specifications specifications together together form form a a platform platform independent independent model model(PIM),(PIM),where where clause clause 8 8 of of the the RM-ODP RM-ODP Part Part 3 3 defines defines a a virtual virtual machine machine which which is is the 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 the correspondences correspondences between between the the viewpoint viewpoint specifications specifications express express the the transformations transformations by by means means of of which which one one model model is is derived derived from from another.another.ITU-T/SG 17 Mar 14 200417Who needs the standard?Needed by system Needed by system specifiersspecifiersNeeded for communication between system Needed for communication between system specifiersspecifiersNeeded for communication between stakeholders Needed for communication between stakeholders and and implementorsimplementorsNeeded for a stable business functionality Needed for a stable business functionality descriptiondescription independent of technology and technology changeindependent of technology and technology changeNeeded for mission critical business systemsNeeded for mission critical business systemsITU-T/SG 17 Mar 14 200418SourcesJapanese 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 developmentIndustrial 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 200419Timetable-TargetsStart of ProjectStart of Project May 2003May 2003SC7 WDSC7 WDMay 2004May 2004SC7 meetingSC7 meeting1st CD1st CDDec 2004Dec 2004FCDFCDMay 2005May 2005 SC7 meeting SC7 meetingFDISFDISDec 2005Dec 2005ISISMay 2006May 2006 SC7 meeting SC7 meetingITU-T/SG 17 Mar 14 200420Questions?ITU-T/SG 17 Mar 14 200421