International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.

International Telecommunication Union

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

New New RecommendationsRecommendations

on ODPon ODPArve MeisingsetRapporteur Q15

2dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Two Parts

o Rev Rec. X.911 for Consent• Enterprise Language

o Draft X.906 for review and comments

• Use of UML for ODP system specifications

3dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Part I

o X.911 Enterprise Language• Ad. 1 Rev.• Rev + Annex A and B

4dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Enterprise Viewpoint

o An enterprise specification of an ODP system is a description of that system and relevant parts of its environment.

o The enterprise specification focuses on the scope and purpose of that system and the policies that apply to it in the context of its environment.

5dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Enterprise Language

o Concepts, o structures, and o rules for o developing, representing, and reasoning

about o a specification of an ODP system from the

enterprise viewpoint

6dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

System Concepts

7dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Community and Behav. Concepts

8dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Accountability Concepts

9dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Policy Concepts

10dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Viewpoint correspondences

The specifier shall provide:– for each enterprise object in the enterprise

specification, a list of those information objects (if any) that represent information or information processing concerning the entity represented by that enterprise object;

– for each role in each community in the enterprise specification, a list of those information object types (if any) that specify information or information processing of an enterprise object fulfilling that role;

ETC. to inf., comp. and engin. viewpoints

11dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Annex B Examples

o e.como Library

12dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Questions

o Is URN an Enterprise Language?o May SDL and MSC be used to specify an

Enterprise Viewpoint?o May eODL be used to specify every

correspondence between Viewpoints?o Have we done enough to position the ITU

languages?o Have we ensured compliance?o Is ODP relevant for ITU?

13dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Part II

o Committee Draft o X.906 Use of UML for ODP system

specifications o The RM-ODP family of standards is notation free,

as well as model development method free. o There is no widely agreed approach to the

structuring of UML specifications. o ISO/IEC 19501 is technically identical to the OMG

specification formal/03-02-04, UML 1.4.1 - ISO format.

o As an example, the UML Profile for EDOC (using the UML extensions mechanism) provides a bridge between the RM-ODP architecture for distributed systems and specific technologies, such as components, workflow, messaging, and web services.

14dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Scope

a) the expression of a system specification in terms of RM-ODP viewpoint specifications using defined UML concepts and extensions (e.g. structuring rules, technology mappings, etc.);

b) relationships between the resultant RM-ODP viewpoint specifications;

c) relationships between RM-ODP viewpoint specifications and model driven architectures such as the OMG MDA.

15dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Relationships between UOD, ODP specifications, and UML models

16dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

RM-ODP viewpoints

17dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Correspondences between RM-ODP viewpoints

18dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

MDA viewpoints and models

o a computation independent viewpoint (CIM) that focuses on the requirements for the system; the details of the system are hidden or as yet undetermined;

o a platform independent viewpoint (PIM) that focuses on the application specific behaviour of a system while hiding the details necessary for a particular platform. A platform independent view shows the part of the complete specification that does not change from one platform to another. A platform independent view may use a general purpose modelling language, or a language specific to the area in which the system will be used;

o a platform specific viewpoint (PSM) that combines the platform independent viewpoint with an additional focus on the detail of the use of a specific platform by a system.

19dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

ODP system specifications and MDA models

20dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Enterprise LanguageSee part I plus details, eg.

21dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Enterprise Language7.2 UML mappings

o An ODP System is a special kind of enterprise object. It maps to UML with a class stereotyped as «EV_ODPSystem», see [7.2.5].

o The scope of an ODP system is the set of behaviours that the system is expected to exhibit, e.g. its roles. It does not, therefore, map to a single UML model element, but to the set of elements that represent its behaviour.

o The field of application is a property of the enterprise specification as a whole, and maps to a text attribute (comment) of the UML model stereotyped as «Enterprise_Spec» which maps to the enterprise specification.

o A community maps to a subsystem stereotyped as «EV_Community», in the name space of which will be the UML model elements mapping to its roles and the associated behaviour (communications, actions, steps and processes), as well as the UML model elements mapping to the policy and accountability concepts specific to the community.

o ETC

22dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Enterprise Language7.3 UML profile

23dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Information LanguageConcepts

24dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Computational LanguageConcepts

25dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Computational Language Coreography

26dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Computational Language Composition

27dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

DataDocument model

28dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Computational languageModel management

29dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering languageBasic concepts

30dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering languageChannels

31dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering languageIdentifiers

32dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering languageCheckpoints

33dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Logical and physical viewpoints

34dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering LanguageEngineering objects

35dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering LanguageClusters and capsules

36dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering LanguageDomains

37dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering LanguageNodes, components and objects

38dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Engineering LanguageDistribution tiers

39dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Technology LanguageModel

40dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Annex BExample specification

41dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

StrategicQuestions

profile

profileUML

ODP

ITU

?

Is UML just used as a meta-language – like BNF?Are ITU and ODP languages compeeting? Have they overlapping application domains?Should ITU and ODP lamguages be better co-ordinated?

42dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

DataQuestions

Is ASN.1 least affected?Should ASN.1 be extended by class diagrams?Is ODP Information viewpoint too weak for a Data architecture?

Layout SchemaContents SchemaExternal Terminology SchemaConcept SchemaInternal Terminology SchemaDistribution SchemaPhysical Schema

43dates

ITU-T

ITU-T Study Group 17, Moscow, 30 March – 8 April 2005

Repetitions and RefinementsQuestions

o Is URN an Enterprise Language?o May SDL and MSC be used to specify an

Enterprise Viewpoint?o Do SDL and MSC qualify as Computational

languages?o May eODL be used to specify every/any

correspondence between Viewpoints?o Have we done enough to position the ITU

languages within ODP?o Have we ensured compliance?o Is ODP relevant for ITU?