UML for ODP viewpoint
specifications
Bryan Wood
Convenor, JTC1/SC7/WG19
[email protected]
ITU-T/SG 17 Geneva, 27 November 2002
ITU-T/SG 27 Nov-27-02
1
Standardization for Open
Distributed Processing (ODP)
• Initiated in JTC 1/SC 21 (Open Systems Interconnection,
Database and Open Distributed Processing) and ITU-T
SG7 (Data networks and open system communications)
• Now the responsibility of JTC 1/SC 7 (Software and
System Engineering) and ITU-T SG 17
• Close collaboration with the Object Management Group
(OMG)
– OMG PAS submissions in the context of ODP standardization
– RM-ODP a specification framework for domain groups
– ODP concepts reflected in MDA
ITU-T/SG 27 Nov-27-02
2
What is RM-ODP?
Reference Model of Open Distributed Processing
( ISO/IEC 10746 | ITU-T Rec. X.901-5)
• Part 1 : Introduction
• Part 2: Foundations
• precise object modelling concepts
• Part 3: Architecture
• viewpoints, viewpoint specifications and
transparencies
• Part 4: Architectural semantics
• formalism
• Part 5: QoS in ODP (under development)
ITU-T/SG 27 Nov-27-02
3
What is RM-ODP?
A framework for ODP standardization and
system specification covering all aspects of
distributed systems - “enterprise”, system,
technology
• comprehensive and coherent object-oriented
modelling concepts
• viewpoints
• viewpoint specifications
ITU-T/SG 27 Nov-27-02
4
Modelling concepts
• Underlying concepts
– entity, abstraction, system, architecture…
• Basic modelling concepts
– action, object, environment (of an object),
interface, location (in space/time) …
• Specification concepts
– composition/decomposition (of objects), type
(of an <X>), <X>template, role …
ITU-T/SG 27 Nov-27-02
5
More modelling concepts
• Organisational concepts
– configuration (of objects), <X> domain…
• Policy concepts
– contract, QoS, environment contract,
prescriptions on behaviour (obligations,
permissions, prohibitions), policy …
ITU-T/SG 27 Nov-27-02
6
Viewpoints
• Different abstractions of the same system
– reflect different concerns
– expressed in terms of specific viewpoint
concepts
• Powerful mechanism for dealing with the
complexity of distributed systems
ITU-T/SG 27 Nov-27-02
7
Different Concerns
Information
Enterprise
System
Computation
Engineering
ITU-T/SG 27 Nov-27-02
Technology
8
Viewpoint Specifications
• Descriptions of different viewpoints on a
system
– related and mutually consistent
• Using specific viewpoint languages
– based on the foundation modelling concepts
ITU-T/SG 27 Nov-27-02
9
Viewpoint specifications
- business context
- business processes
Enterprise
ITU-T/SG 27 Nov-27-02
10
The enterprise specification
• Specifies the roles played by an IT system in its
organisational environment
• An object model of a social/commercial
organisation in terms of:
– enterprise objects
– community (of enterprise objects)
•
•
•
•
objectives
structure (roles)
behaviour
policy
ITU-T/SG 27 Nov-27-02
11
Viewpoint specifications
- business context
- business processes
Enterprise
- information
- changes to information
- constraints
Information
ITU-T/SG 27 Nov-27-02
12
The information specification
• Specifies system behaviour abstracted from
implementation
• An object model of the IT system describing the
information and processing of information in terms
of:
– information objects
– invariant, static and dynamic schema
• behaviour: actions
• actions: changes of state
• activities (use cases): sequences of actions
ITU-T/SG 27 Nov-27-02
13
Viewpoint specifications
- business context
- business processes
Enterprise
- information
- changes to information
- constraints
Information
- object configuration
- interactions
between objects
at interfaces
Computational
ITU-T/SG 27 Nov-27-02
14
The computational specification
• Specifies computational objects - units of
distribution and portability
• An object model of the IT system describing
the structure of processing in terms of:
•
•
•
•
•
computational objects (interfaces and invocations)
interfaces: operations supported
invocations: operations invoked
activities: sequences of invocations
computational binding
ITU-T/SG 27 Nov-27-02
15
Viewpoint specifications
- business context
- business processes
Enterprise
- information
- changes to information
- constraints
Information
- object configuration
- interactions
between objects
at interfaces
Computational
- e.g. realisation in
CORBA
- use of ORB
- use of CORBA services
Engineering
ITU-T/SG 27 Nov-27-02
16
The engineering specification
• Specifies the mechanisms and services that
provide the required distribution
transparencies and QoS constraints.
• An object model of the system describing
the infrastructure supporting
the computational structure
– infrastructure objects
– basic engineering objects
ITU-T/SG 27 Nov-27-02
17
The technology specification
• Specifies the procurable pieces
from which the system is built.
• An object model of the system describing
the configuration of hardware and
software components that comprise
the system
ITU-T/SG 27 Nov-27-02
18
A System specification
- business context
- business processes
Enterprise
- information
- changes to information
- constraints
Information
- object configuration
- interactions
between objects
at interfaces
Computational
- e.g. realisation in
CORBA
- use of ORB
- use of CORBA services
Engineering
- hardware and software components
Technology
ITU-T/SG 27 Nov-27-02
19
UML for ODP viewpoint
specifications
A proposed standard covering:
1) the expression of a system specification in terms of
RM-ODP viewpoint specifications using defined
UML/UML extensions and concepts (e.g. structuring
rules, technology mapping, relationship with MDA
etc.);
2) relationships between the resultant RM-ODP
viewpoint specifications;
3) relationships between RM-ODP viewpoint
specifications and model driven architectures such as
the OMG MDA
ITU-T/SG 27 Nov-27-02
20
Why UML for ODP viewpoint
specifications?
• RM-ODP defines concepts and framework for
system specification
• RM-ODP does not define notation for
specification (modelling)
• UML defines notation for specification
(modelling)
• UML does not define concepts and framework
for system specification
ITU-T/SG 27 Nov-27-02
21
Why a Specification Framework?
• Needed by system specifiers
• Needed for communication between system
specifiers
• Needed for communication between stakeholders
and implementors
• Needed for a stable business functionality
description
– independent of technology and technology change
• Needed for mission critical business systems
ITU-T/SG 27 Nov-27-02
22
Sources
• UML profile for Enterprise Distributed Object
Computing (EDOC)
• European research projects:
– Synapses - developing a distributed architecture bsaed
on the RM-ODP to enable healthcare
– COMBINE - investigating the organisation and
process for component-based system developed
• Japanese Association of Healthcare Information
System Industry (JAHSI) of a Japanese Hospital
Information Reference Enterprise Model
• Industrial Practice
ITU-T/SG 27 Nov-27-02
23
Timetable - Targets
• Start of Project May 2003
• SC7 WD
May 2004
• 1st CD
Dec 2004
• FCD
May 2005
• FDIS
Dec 2005
• IS
May 2006
ITU-T/SG 27 Nov-27-02
SC7 meeting
SC7 meeting
SC7 meeting
24
Questions ?
- SG 17 interest?
ITU-T/SG 27 Nov-27-02
25