ISO/IEC 19793:2008
(Main)Information technology — Open Distributed Processing — Use of UML for ODP system specifications
Information technology — Open Distributed Processing — Use of UML for ODP system specifications
ISO/IEC 19793:2008 defines use of the Unified Modeling Language (UML 2.1.1 Superstructure Specification, OMG document formal/07-02-05) for expressing system specifications in terms of the viewpoint specifications defined by the Reference Model of Open Distributed Processing (ISO/IEC 10746, Parts 1 to 4) and the Enterprise Language (ISO/IEC 15414). It covers 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.) and relationships between the resultant RM-ODP viewpoint specifications. ISO/IEC 19793:2008 is intended to be used by ODP modellers who want to use the UML notation for expressing their ODP specifications in a graphical and standard way, UML modellers who want to use the RM-ODP concepts and mechanisms to structure their UML system specifications, and modelling tool suppliers, who wish to develop UML-based tools that are capable of expressing RM-ODP viewpoint specifications.
Technologies de l'information — Traitement réparti ouvert — Utilisation de l'UML pour les spécifications de système ODP
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19793
First edition
2008-12-15
Information technology — Open
Distributed Processing — Use of UML for
ODP system specifications
Technologies de l'information — Traitement réparti ouvert — Utilisation
de l'UML pour les specifications de système ODP
Reference number
ISO/IEC 19793:2008(E)
©
ISO/IEC 2008
---------------------- Page: 1 ----------------------
ISO/IEC 19793:2008(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2008
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2008 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19793:2008(E)
CONTENTS
Page
1 Scope. 1
2 Normative references . 1
2.1 Identical Recommendations | International Standards. 1
2.2 OMG specifications. 1
3 Definitions . 2
3.1 Definitions from ODP standards . 2
3.2 Definitions from the Enterprise Language. 2
3.3 Definitions from the Unified Modeling Language. 2
3.4 Definitions from ODP standards refined or extended in this Recommendation | International
Standard. 3
4 Abbreviations . 3
5 Conventions . 3
6 Overview of modelling and system specification approach . 4
6.1 Introduction . 4
6.2 Overview of ODP concepts (extracted from RM-ODP Part 1). 4
6.3 Overview of UML concepts . 8
6.4 Universes of discourse, ODP specifications and UML models. 9
6.5 Modeling concepts and UML profiles for ODP viewpoint languages and correspondences . 10
6.6 General principles for expressing and structuring ODP system specifications using UML . 10
6.7 Correspondences between viewpoint specifications . 11
7 Enterprise specification. 12
7.1 Modelling concepts . 12
7.2 UML profile. 16
7.3 Enterprise specification structure (in UML terms). 24
7.4 Viewpoint correspondences for the enterprise language . 25
8 Information specification . 26
8.1 Modelling concepts . 26
8.2 UML profile. 28
8.3 Information specification structure (in UML terms) . 30
8.4 Viewpoint correspondences for the information language. 31
9 Computational specification . 31
9.1 Modelling concepts . 31
9.2 UML profile. 36
9.3 Computational specification structure (in UML terms) . 42
9.4 Viewpoint correspondences for the computational language . 42
10 Engineering specification. 43
10.1 Modelling concepts . 43
10.2 UML profile. 52
10.3 Engineering specification structure (in UML terms). 56
10.4 Viewpoint correspondences for the engineering language. 57
11 Technology Specification. 58
11.1 Modelling concepts . 58
11.2 UML profile. 58
11.3 Technology specification structure (in UML terms) . 59
11.4 Viewpoint correspondences for the technology language . 60
12 Correspondences specification . 60
12.1 Modelling concepts . 60
12.2 UML profile. 61
13 Modelling conformance in ODP system specifications. 62
13.1 Modelling conformance concepts . 62
13.2 UML profile. 62
© ISO/IEC 2008 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19793:2008(E)
Page
14 Conformance and compliance to this document . 63
14.1 Conformance. 63
14.2 Compliance. 63
Annex A – An example of ODP specifications using UML . 64
A.1 The Templeman Library System . 64
A.2 Enterprise specification in UML . 65
A.3 Information specification in UML . 79
A.4 Computational specification in UML . 87
A.5 Engineering specification in UML. 93
A.6 Technology specification in UML . 102
iv © ISO/IEC 2008 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19793:2008(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 19793 was prepared jointly by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 7, Software and systems engineering in collaboration with ITU-T. The identical text is
published as ITU-T Rec. X.906.
© ISO/IEC 2008 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 19793:2008(E)
0 Introduction
The rapid growth of distributed processing has led to the adoption of the Reference Model of Open Distributed
Processing (RM-ODP), which provides a coordinating framework for the standardization of Open Distributed
Processing (ODP). RM-ODP creates an architecture within which support of distribution, interworking, and portability
can be integrated. This architecture provides a framework for the specification of ODP systems.
RM-ODP is based on precise concepts derived from current distributed processing developments and, as far as possible,
on the use of formal description techniques for specification of the architecture. It does not recommend any notation.
®
The Unified Modeling Language™ (UML ) was developed by the Object Management Group™ (OMG™). It provides
a notation for modelling in support of information system design and is widely used throughout the IT industry as the
language and notation of choice.
This Recommendation | International Standard refines and extends the definition of how ODP systems are specified by
defining the use of the Unified Modeling Language for the expression of ODP system specification.
0.1 RM-ODP
The RM-ODP consists of:
– Part 1 (ITU-T Rec. X.901 | ISO/IEC 10746-1): Overview, which contains a motivational overview of
ODP, giving scoping, justification and explanation of key concepts, and an outline of the ODP
architecture. It contains explanatory material on how the RM-ODP is to be interpreted and applied by its
users, who may include standards writers and architects of ODP systems. It also contains a categorization
of required areas of standardization expressed in terms of the reference points for conformance identified
in ITU-T Rec. X.903 | ISO/IEC 10746-3. Part 1 is not normative.
– Part 2 (ITU-T Rec. X.902 | ISO/IEC 10746-2): Foundations, which contains the definition of the
concepts and analytical framework for normalized description of (arbitrary) distributed processing
systems. It introduces the principles of conformance to ODP standards and the way in which they are
applied. This is only to a level of detail sufficient to support ITU-T Rec. X.903 | ISO/IEC 10746-3 and to
establish requirements for new specification techniques. Part 2 is normative.
– Part 3 (ITU-T Rec. X.903 | ISO/IEC 10746-3): Architecture, which contains the specification of the
required characteristics that qualify distributed processing as open. These are the constraints to which
ODP standards shall conform. It uses the descriptive techniques from ITU-T Rec. X.902 | ISO/IEC
10746-2. Part 3 is normative.
– Part 4 (ITU-T Rec. X.904 | ISO/IEC 10746-4): Architectural semantics, which contains a formalization
of the ODP modelling concepts defined in clauses 8 and 9 of ITU-T Rec. X.902 | ISO/IEC 10746-2. The
formalization is achieved by interpreting each concept in terms of the constructs of one or more of the
different standardized formal description techniques. Part 4 is normative.
In the same series as the RM-ODP are a number of other Standards and Recommendations, and, of these, the principal
one that concerns this Recommendation | International Standard is:
– The Enterprise Language (ITU-T Rec. X.911 | ISO/IEC 15414), which refines and extends the enterprise
language defined in ITU-T Rec. X.903 | ISO/IEC 10746-3 to enable full enterprise viewpoint
specification of an ODP system.
0.2 UML
The Unified Modeling Language (UML) is a visual language for specifying and documenting the artifacts of systems. It
is a general-purpose modelling language that can be used with all major object and component methods and that can be
applied to all application domains (e.g., health, finance, telecom, aerospace) and implementation platforms (e.g., J2EE,
®
CORBA , .NET).
The version of UML currently adopted as an International Standard (ISO/IEC 19501) is UML 1.4, which is basically
the language that was originally adopted by the OMG in the 1990s. UML was substantially extended by the OMG in
2005 to produce version 2, which offers significant enhancements, particularly in the way the language and notation
handle structured classifiers. These enhancements have been found to be essential for expressing many of the more
complex concepts in the RM-ODP computational and engineering language. As a result, this Recommendation |
International Standard takes UML version 2 as its baseline.
UML version 2 has been structured modularly, with the ability to select only those parts of the language that are of
direct interest. It is extensible, so it can be easily tailored to meet the specific user requirements. The UML specification
defines thirteen types of diagram, divided in two categories that represent, respectively: the static structure of the
objects in a system (structure diagrams) and the dynamic behaviour of the objects in a system (behaviour diagrams). In
vi © ISO/IEC 2008 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 19793:2008(E)
addition, UML incorporates extension mechanisms that allow the definition of new dialects of UML (managed using
UML profiles) to customize the language for particular platforms and domains.
The UML specification is defined using a metamodelling approach (i.e., a metamodel is used to specify the model that
comprises UML). That metamodel has been constructed so that the resulting family of UML languages is fully aligned
®
with the rest of the OMG specifications (e.g., MOF™, OCL, XMI ) and to allow the exchange of models between
tools.
0.3 Overview and motivation
ITU-T Rec. X.903 | ISO/IEC 10746-3 defines a framework for the specification of ODP systems comprising:
a) five viewpoints, called enterprise, information, computational, engineering and technology, which
provide a basis for the specification of ODP systems;
b) a viewpoint language for each viewpoint, defining concepts and rules for specifying ODP systems from
the corresponding viewpoint.
This Recommendation | International Standard defines:
– use of the viewpoints prescribed by the RM-ODP to structure UML system specifications;
– rules for expressing RM-ODP viewpoint languages and specifications with UML and UML extensions
(e.g., UML profiles).
It allows UML tools to be used to process viewpoint specifications, facilitating the software design process.
Currently there is growing interest in the use of UML for system modelling. However, there is no widely agreed
approach to the structuring of such specifications. This adds to the cost of adopting the use of UML for system
specification, hampers communication between system developers and makes it difficult to relate or merge system
specifications where there is a need to integrate IT systems.
The RM-ODP defines essential concepts necessary to specify open distributed processing systems from five prescribed
viewpoints and provides a framework for the structuring of specifications for distributed systems.
However, the RM-ODP prescribes neither a notation, nor a model development method.
This Recommendation | International Standard provides the necessary framework for ODP system specification using
UML. It defines both a UML based notation for the expression of such specifications, and an approach for their
structuring using the notation, thus providing the basis for model development methods.
By defining how UML and UML extensions should be used to express RM-ODP viewpoint specifications, the standard
enables the ODP viewpoints and ODP architecture to provide the needed framework for system specification using
UML.
This Recommendation | International Standard contains the following annexes:
– Annex A: An example of ODP specifications using UML.
This annex is not normative.
© ISO/IEC 2008 – All rights reserved vii
---------------------- Page: 7 ----------------------
ISO/IEC 19793:2008 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
Information technology – Open distributed processing –
Use of UML for ODP system specifications
1 Scope
This Recommendation | International Standard defines use of the Unified Modeling Language (UML 2.1.1
Superstructure Specification, OMG document formal/07-02-05) for expressing system specifications in terms of the
viewpoint specifications defined by the Reference Model of Open Distributed Processing (RM-ODP, ITU-T Recs
X.901 to X.904 | ISO/IEC 10746 Parts 1 to 4) and the Enterprise Language (ITU-T Rec. X.911 | ISO/IEC 15414). It
covers:
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.
This document is intended for the following audiences:
– ODP modellers who want to use the UML notation for expressing their ODP specifications in a graphical
and standard way;
– UML modellers who want to use the RM-ODP concepts and mechanisms to structure their UML system
specifications; and
– modelling tool suppliers, who wish to develop UML-based tools that are capable of expressing RM-ODP
viewpoint specifications.
2 Normative references
The following Recommendations and International Standards contain provisions which, through reference in this text,
constitute provisions of this Recommendation | International Standard. At the time of publication, the editions indicated
were valid. All Recommendations and Standards are subject to revision, and parties to agreements based on this
Recommendation | International Standard are encouraged to investigate the possibility of applying the most recent
edition of the Recommendations and Standards listed below. Members of IEC and ISO maintain registers of currently
valid International Standards. The Telecommunication Standardization Bureau of the ITU maintains a list of currently
valid ITU-T Recommendations.
2.1 Identical Recommendations | International Standards
– ITU-T Recommendation X.725 (1995) | ISO/IEC 10165-7:1996, Information technology – Open Systems
Interconnection – Structure of management information: General Relationship Model.
– ITU-T Recommendation X.902 (1995) | ISO/IEC 10746-2:1996, Information technology – Open
Distributed Processing – Reference Model: Foundations.
– ITU-T Recommendation X.903 (1995) | ISO/IEC 10746-3:1996, Information technology – Open
Distributed Processing – Reference Model: Architecture.
– ITU-T Recommendation X.904 (1997) | ISO/IEC 10746-4:1998, Information technology – Open
Distributed Processing – Reference Model: Architectural semantics.
– ITU-T Recommendation X.911 (2001) | ISO/IEC 15414:2002, Information technology – Open
Distributed Processing – Reference model – Enterprise language.
2.2 OMG specifications
– OMG Unified Modeling Language: Superstructure, version 2.1.1, formal/07-02-05.
ITU-T Rec. X.906 (11/2007) 1
---------------------- Page: 8 ----------------------
ISO/IEC 19793:2008 (E)
3 Definitions
For the purposes of this Recommendation | International Standard, the following definitions apply.
3.1 Definitions from ODP standards
3.1.1 Modelling concept definitions
This Recommendation | International Standard makes use of the following terms as defined in ITU-T Rec. X.902 |
ISO/IEC 10746-2:
abstraction; action; activity; architecture; atomicity; behaviour (of an object); binding; class; client
object; communication; composition; component object [2-5.1]; composite object; configuration (of
objects); conformance point; consumer object; contract; creation; data; decomposition; deletion;
distributed processing; distribution transparency; domain; entity; environment; environment
contract; epoch; error; establishing behaviour; failure; fault; group; identifier; information; initiating
object; instance; instantiation (of an template); internal action; interaction; interchange reference
point; interface; interface signature; interworking reference point; introduction; invariant; location in
space; location in time; name; naming context; naming domain; notification; object; obligation; ODP
standards; ODP system; open distributed processing; perceptual reference point; permission; persistence;
producer object; programmatic reference point; prohibition; proposition; quality of service; reference
point; refinement; role; server object; spawn action; stability; state (of an object); subdomain; subtype;
supertype; system; template; term; terminating behaviour; trading; type (of an ); viewpoint (on
a system).
3.1.2 Viewpoint language definitions
This Recommendation | International Standard makes use of the following terms as defined in ITU-T Rec. X.903 |
ISO/IEC 10746-3:
binder; capsule; channel; cluster; community; computational behaviour; computational binding object;
computational object; computational interface; computational viewpoint; dynamic schema; engineering
viewpoint; distributed binding; enterprise object; enterprise viewpoint; federation; information
object; information viewpoint; interceptor; invariant schema; node; nucleus; operation; protocol object;
static schema; stream; stub; technology viewpoint; language.
3.2 Definitions from the Enterprise Language
This Recommendation | International Standard makes use of the following terms as defined in ITU-T Rec. X.911 |
ISO/IEC 15414:
actor (with respect to an action); agent; artefact (with respect to an action); authorization; commitment;
community object; declaration; delegation; evaluation; field of application (of a specification); interface
role; objective (of an ); party; policy; prescription; principal; process; resource (with respect to an
action); scope (of a system); step; violation.
3.3 Definitions from the Unified Modeling Language
This Recommendation | International Standard makes use of the following terms as defined in OMG document
formal/07-02-05:
abstract class; action; activity; activity diagram; aggregate; aggregation; association; association class;
association end; attribute; behaviour; behaviour diagram; binary association; binding; call; class;
classifier; classification; class diagram; client; collaboration; collaboration occurrence; communication
diagram; component; component diagram; composite; composite structure diagram; composition;
concrete class; connector; constraint; container; context; delegation; dependency; deployment diagram;
derived element; diagram; distribution unit; dynamic classification; element; entry action; enumeration;
event; exception; execution occurrence; exit action; export; expression; extend; extension; feature; final
state; fire; generalizable element; generalization; guard condition; implementation; implementation class;
implementation inheritance; import; include; inheritance; initial state; instance; interaction; interaction
diagram; interaction overview diagram; interface; internal transition; lifeline; link; link end; message;
metaclass; metamodel; method; multiple classification; multiplicity; n-ary association; name; namespace;
node; note; object; object diagram; object flow state; object lifeline; operation; package; parameter;
parent; part; partition; pattern; persistent object; pin; port; postcondition; precondition; primitive type;
profile; property; pseudo-state; realization; receive [a message]; receiver; reception; refinement;
relationship; role; scenario; send [a message]; sender; sequence diagram; signal; signature; slot; state;
2 ITU-T Rec. X.906 (11/2007)
---------------------- Page: 9 ----------------------
ISO/IEC 19793:2008 (E)
state machine diagram; state machine; static classification; stereotype; stimulus; structural feature;
structure diagram; subactivity state; subclass; submachine state; substate; subpackage; subsystem;
subtype; superclass; supertype; supplier; tagged value; time event; time expression; timing diagram;
trace; transition; type; usage; use case; use case diagram; value; visibility.
3.4 Definitions from ODP standards refined or extended in this Recommendation | International
Standard
This Recommendation | International Standard refines or extends the following terms from ITU-T Rec. X.902 |
ISO/IEC 10746-2, ITU-T Rec. X.903 | ISO/IEC 10746-3, or ITU-T Rec. X.911 | ISO/IEC 15414:
– Policy (see [7.1.3]).
4 Abbreviations
For the purposes of this Recommendation | International Standard, the following abbreviations apply.
MOF Meta Object Facility
OCL Object Constraint Language
ODP Open Distributed Processing
OMG Object Management Group
RM-ODP Reference Model of Open Distributed Processing
UML Unified Modeling Language
XMI XML Metadata Interchange
NOTE – UML, CORBA, XMI, MOF, OMG, Object Management Group, and Unified Modeling Language are either registered
trademarks or trademarks of Object Management Group, Inc. in the United States and/or other countries.
5 Conventions
In the text that follows, the following conventions apply.
This Recommendation | International Standard is referred to as "this document".
ITU-T Rec. X.902 | ISO/IEC 10746-2 (RM-ODP Part 2: Foundations) and ITU-T Rec. X.903 | ISO/IEC 10746-3 (RM-
ODP Part 3: Architecture) are referred to as "Part 2" and "Part 3" of the RM-ODP, respectively.
ITU-T Rec. X.911 | ISO/IEC 15414 (RM-ODP Enterprise Language) is referred to as "the Enterprise Language".
The UML Superstructure Specification (see [2.2]) is referred to as "the UML specification". The UML notation defined
in the UML specification is referred to as "UML".
References to the normative text of this document, to the text of Parts 2 and 3 of the RM-ODP, to the Enterprise
Language and to UML are expressed in one of these forms:
[n.n] – a reference to clause n.n of this document.
[Part 2 – n.n] – a reference to clause n.n of RM-ODP Part 2;
[Part 3 – n.n] – a reference to clause n.n of RM-ODP Part 3;
[E/L – n.n] – a reference to clause n.n of the Enterprise Language;
[UML – n.n] – a reference to clause n.n of the UML specification.
For exam
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.