ITU-T X.906 | ISO/IEC 19793: UML for ODP system specification -- Current status -- Antonio Vallecillo Universidad de Málaga Dpto. Lenguajes y Ciencias

ITU-T X.906 | ISO/IEC 19793:UML for ODP system specification

-- Current status --

Antonio Vallecillo

Universidad de MálagaDpto. Lenguajes y Ciencias de la Computación

[email protected]

http://www.rm-odp.net/

WODPEC 2006 - Hong Kong 2

“UML4ODP”

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

A standard defining:a set of UML Profiles for expressing a system specification in terms of viewpoint specifications

possible relationships between the resultant ODP viewpoint specifications and how they are represented

the structure of a system specification expressed as a set of UML models using ODP viewpoint profiles

“A standard that enables the use of MDA tools in developing and maintaining ODP system specifications”


UML4ODP

Why?RM-ODP is notation- and methodology- independent

Which is an advantage (a-priori) ...

...but hampers its widespread adoption and use

Target audiencesUML Modelers

• who need to structure (somehow) their LARGE system specifications

ODP Modelers• who need some (graphical) notation for expressing their ODP

specifications and tool support

Modeling tool suppliers • who wish to develop UML-based tools that are capable of expressing

RM-ODP viewpoint specifications.


UML4ODP

This Recommendation | International Standard defines:a UML based notation for the expression of ODP specifications

an approach for structuring of them using the notation, thus providing the basis for model development methods

It provides:The expression of a system specification in terms of RM-ODP viewpoint specifications using defined UML concepts and extensions

• A set of UML 2.0 profiles (one for each viewpoint)• A way of using these profiles (structuring rules)

relationships between the resultant RM-ODP viewpoint specifications; • A way of modelling ODP correspondences• A profile for correspondences

A way for modelling conformance of implementations to specifications; • A profile for conformance (reference points, conformance staments, etc.)

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


UML4ODP – Document structure

Foreword0 Introduction1 Scope2 Normative references3 Definitions4 Abbreviations5 Conventions6 Overview of modelling and system specification approach7 Enterprise Specification8 Information Specification9 Computational Specification10 Engineering Specification11 Technology Specification12 Correspondences specification13 Modelling conformance in ODP system specifications14 Conformance and compliance to this documentAnnex A UML profiles for ODP languages using ITU-T guidelines for UML profile designAnnex B An example of ODP specifications using UMLAnnex C Relationship with MDA®Annex D Architectural Styles


UML4ODP Clause 6

6 Overview of modelling and system specification approach

6.1 Introduction

6.2 Overview of ODP concepts (extracted from RM-ODP-1)

6.3 Overview of UML concepts

6.4 Universes of discourse, ODP specs and UML models

6.5 General principles for expressing and structuring ODP system specifications using UML

6.6 Correspondences between viewpoint specifications


UML4ODP Clause 6.4 (UoD, ODP specifications and UML models)

Universe

of Discourse

(UOD)

ODP

specification UML

model

The UML notation

models (see RM-ODP)

expresses

(UML4ODP)

represents (see UML spec)


UML4ODP Clause 6.5(Principles for expressing and structuring ODP specs using UML)

The DSLs used to represent the viewpoint languages are defined using the UML lightweight extension mechanism (UML Profiles)

The ODP system specification will consist of a single UML model stereotyped as «ODP_SystemSpec», that contains a set of models, one for each viewpoint specification, each stereotyped as «<X>_Spec», where <X> is the viewpoint concerned

Stereotypes are used to represent domain specific specializations of UML metaclasses in order to express the semantics of the RM-ODP viewpoint language concerned

Each viewpoint specification uses the appropriate UML profile for that language, as described in Clauses 7 to 11


ODP System specification structure


UML4ODP Clause 6.5(Principles for expressing and structuring ODP specs using UML)

The DSLs used to represent the viewpoint languages are defined using the UML lightweight extension mechanism (UML Profiles)

The ODP system specification will consist of a single UML model stereotyped as «ODP_SystemSpec», that contains a set of models, one for each viewpoint specification, each stereotyped as «<X>_Spec», where <X> is the viewpoint concerned

Stereotypes are used to represent domain specific specializations of UML metaclasses in order to express the semantics of the RM-ODP viewpoint language concerned

Each viewpoint specification uses the appropriate UML profile for that language, as described in Clauses 7 to 11


Enterprise metamodel (excerpt 1)


Enterprise metamodel (excerpt 2)


Enterprise Profile: Classifiers (excerpt)


Information Language metamodel


Information Profile


UML4ODP Clause 6.6(Correspondences)

Correspondences are key to viewpoint modeling

They form part of the ODP specification of a system

Correspondences are not part of any viewpoint specification

Correspondences are expressed in UML too


UML4ODP Clauses 7-11

X <Viewpoint> Specification

X.1 Modelling concepts• A brief description of the <viewpoint> language

• Summary of the <viewpoint> MOF-metamodel

X.2 UML Profile• Description on how the language concepts are mapped to UML, by

extending the appropriate metaclasses

• UML specification of the profile

X.3 <Viewpoint> specification structure (in UML terms)• UML packages and grouping rules

X.4 Viewpoint correspondences for the <Viewpoint> language• Description of the correspondences to other viewpoints

• Not in UML (clause 12)


UML4ODP Clauses 12-14

12 Correspondences specification

12.1 Modelling concepts

12.2 UML Profile

13 Modelling conformance in ODP system specifications

13.1 Modelling concepts

13.2 UML profile

14 Conformance and compliance to this document

14.1 Conformance

14.2 Compliance


Correspondence metamodel


Correspondence Profile


Conformance Profile


UML4ODP Annexes

Annex A:

UML profiles for ODP languages using ITU-T guidelines for UML profile design

Annex B

An example of ODP specifications using UML

Annex C

Relationship with MDA

Annex D Architectural Styles


Annex C: Relation with MDA


MDA

An approach to system development using models as a basis for understanding, design, construction, deployment, operation, maintenance and modificationThree essential elements:

specifying a system independently of the platform that supports it,specifying platforms,transforming the system specification into one for a particular choice of platform.

Goals: portability, interoperability and reusabilityPrescribes the kinds of model to be used in specifying a system, how those models are prepared and the relationships between them


What MDA does

Identifies different viewpoints on a system different abstractions - reflecting different concernsproviding a way of dealing with system complexity

Specifies 3 kinds of viewpoint model for a system:a computation independent model (CIM): a view of a system that specifies its function without specifying details of its structure a platform independent model (PIM): a view of a system that specifies its computational structure independent of any specific platform - usable with different platforms of similar type. a platform specific model (PSM): a view of a system that combines the specifications in the PIM with a specification of the use of a particular type of platform.

Specifies types of transformations between models


What MDA does not do

MDA does not offer:

a definition of the concerns and design decisions to be covered by each MDA model

language constructs to express the concerns and decisions covered by each MDA model

…but ODP can offer:

a definition of the concerns and design decisions to be covered by each MDA model

language constructs to express the concerns and decisions covered by each MDA model


ODP Specifications and the MDA

Business Needs

Enterprise Spec

Computational Spec

Engineering Spec

Technology Spec

Information Spec

CIM*

PIM*

PSM*

Platform Model*

Note: Terms with “*” are from MDA Guide

Transparencies

Choice of technology

Business Needs

Enterprise Spec

Computational Spec

Engineering Spec

Technology Spec

Information Spec

CIM*

PIM*

PSM*

Platform Model*

Note: Terms with “*” are from MDA Guide

Transparencies

Choice of technology


ODP and MDA together offer

separating and integrating different system concerns

combining skills and experience

assigning responsibilities

automating development

An IT based approach to system An IT based approach to system development that provides a framework for:development that provides a framework for:


Annex D: Architectural styles

Describes some common architectural styles used in the design of distributed systems, and provides the corresponding UML Profiles

The architectural styles that described are client-server,

n-tier,

Model-View-Controller (MVC), and

Service-Oriented Architecture (SOA)


Client-server Profile


Progress and Targets

Start of Project May 2003

SC7 WD May 2004 SC7 meeting

1st CD Dec 2004

2nd CD May-Oct 2005 SC7 meeting

FCD May 2006 WG19 meeting

FDIS? Dec 2006 WG19 meeting

Current WD is available as ISO-stds/04-06-01


Current status

Clauses 6 – 14 (almost) finishedStill to decide how to represent some E/L elements

Very minor adjustments to all viewpoints

Annexes A, C, D – done

Annex B – In progress (still work to do…)It serves as a proof-of-concept, validation, and example of use

Although it is not critical to the standard itself as a document…

… it is key to have a “usable” standard

A lot of help is neededTo finish the missing parts (specially the example)

To proof-read the document

To use the proposed way of modeling ODP systems using UML (more examples, feedback, validation,…)


Thank you

For more informationBryan Wood (WG19 convenor)

Sandy-Tyndale Biscoe (UML4ODP co-editor)

Antonio Vallecillo (UML4ODP co-editor)

Resourceswww.rm-odp.net


OPD viewpoints

EnterpriseEnterpriseBusiness Aspects

The purpose, scope and policies for theorganization that will own the system

What for? why? who? when?

ComputationalComputationalApplication Design Aspects

Functional decomposition of the systeminto objects suitable for distribution

How does each bit work?

EngineeringEngineeringSolution Types & Distribution

Infrastructure required to support distributionHow do the bits work together?

TechnologyTechnologyImplementation

System hardware & softwareand actual distribution

With what?

ODPSystem

Information System AspectsInformation handled by the system andconstraints on the use and interpretation

of that information

What is it about?

InformationInformation


Enterprise metamodel (1)












Enterprise Profile: General


Enterprise Profile: Classifiers


Enterprise Profile: Activities


Enterprise Profile: Relations


Information Language metamodel


Information Profile


Computational Language metamodel


Computational Profile (1)


Computational Profile (2)


Engineering Metamodel (1)






Engineering Profile (1)


Engineering Profile (2)


Technology metamodel


Technology Profile


Correspondence metamodel


Correspondence Profile


Conformance Profile

Documents

ITU-T X.906 | ISO/IEC 19793: UML for ODP system specification -- Current status -- Antonio Vallecillo Universidad de Málaga Dpto. Lenguajes y Ciencias