UML 2'0 Infrastructure Proposal 3rd revision

1
UML 2.0 Infrastructure Proposal(3rd revision)

• U2 Partners(www.u2-partners.org)
• January 2003

2
Overview

• Proposal status
• Requirements recap
• Submission overview
• Pragmatics

3
Proposal Status

• Third revised submission
• UML Infrastructure v. 2.0 (3rd revision)
• ad/03-01-01 in response to ad/00-09-01
• supporting artifacts
• ad/03-01-03 Abstract Syntax (MDL format)
• ad/03-01-05 XMI (XMI format)
• Reused by
• UML Superstructure v. 2.0 (2nd revision)
• ad/03-01-02 in response to ad/00-09-02
• MOF 2.0 Core submission
• ad/02-12-10 in response to ad/01-11-14

4
U2 Partners

• Submitters
• Alcatel, CA, Ericsson, HP, IBM, I-Logix, IONA,
  Kabira, Motorola, Oracle, Rational, SOFTEAM,
  Telelogic, Unisys
• Supporters
• Advanced Concepts Center LLC, Ceira Technologies,
  Commissariat à L'Energie Atomique, Compuware,
  DaimlerChrysler, Embarcadero Technologies, Enea
  Data, France Telecom, Fraunhofer FOKUS, Fujitsu,
  Gentleware, Intellicorp, Jaczone, Kennedy Carter,
  Klasse Objecten, KLOCwork, Lockheed Martin,
  Mercury Computer, MSC.Software, Northeastern
  University, Popkin Software, Proforma, Sims
  Associates, Syntropy Ltd., Sun Microsystems,
  University of Kaiserslautern, University of Kent,
  VERIMAG, WebGain, and 88solutions

5
Requirements Recap

• General requirements
• separation of concerns between semantics and
  notation
• specify XMI for UML
• Architectural alignment and restructuring
• align UML and MOF
• package structure that flexibly supports
  compliance points
• Extensibility
• profiles
• first-class extension mechanism

6
Relationships to OMG Standards
MOF 2.0
InfrastructureLibrary
UML 2.0
The InfrastructureLibrary is self-contained
7
Infrastructure Updates

• Updates since 2nd revision (ad/02-09-01)
• more detailed semantics and constraints
• simplified abstract syntax
• fewer fine-grained packages
• Completed alignment between UML and MOF
• resolved remaining alignment issues

8
The Infrastructure Library

• Purposes
• define the common concepts between UML and MOF
• allow concepts to be reused by metamodels (CWM,
  UML, MOF, etc.)
• define the constructs that are used to
  instantiate metamodels
• align UML extensibility with MOF extensibility

Core
PrimitiveTypes
Abstractions
Basic
Constructs
Profiles
9
Core Packages

• PrimitiveTypes
• a set of primitive types used in the
  specification
• Basic
• a few basic metaclasses on which we base XMI
  generation
• basis for EMOF

• Abstractions
• a set of metaclasses (and packages) intended to
  be reused by various metamodels
• Constructs
• alignment between UML and MOF
• basis for CMOF
• basis for UML 2.0

10
Extensibility

• MOF-based extensibility
• any metamodel with elements created as instances
  of MOF elements can be extended without
  restriction

• Profiles-based extensibility
• restricted version of MOF-based extensibility
• any metamodel based on the InfrastructureLibrary
  can be extended

11
MOF-Based Extensions
UML
UML_4_Me
metaclass Classifier
metaclass Classifier
metaclass MyProperties
metaclass Class
metaclass Class
metaclass MyConstruct
isSpecial Boolean
property String
0..1
mc

12
Profiles-Based Extensions
UML
profile My_UML_Profile
metaclass Classifier
metaclass Class
stereotype MyClass
reference
feature String
metaclass Class
apply
MyModel
myClass Bar
myClass Foo
feature A
feature B
13
Profile limitations

• In a profile, it is not allowed to have
• generalizations or specializations of reference
  metaclasses
• properties typed by referenced metaclasses or
  stereotypes
• it is allowed to have properties typed by
  ordinary classifiers
• Furthermore
• a profile cannot define new metaclasses
• a stereotype cannot be used standalone, but must
  always be used in conjunction with a referenced
  metaclass that it extends

14
Profiles Walkthrough (i)

• Define profile(s)
• based on reference metamodel
• may use other packages for its definition

Extension
Metamodel
profile RT-UML
UML
JavaTypes
metaclass Class
stereotype Clock
reference
reference
resolution Integer
import
profile RT-UML
profile Java
15
Profiles Walkthrough (ii)

• Specify model
• based on same metamodel

Instances of metaclass Class
Race
timer
Starter
StopWatch

16
Profiles Walkthrough (iii)

• Apply profile(s) to model
• make it possible to apply stereotypes of the
  profile to the model elements

profile RT-UML
apply
Race
Starter
timer
StopWatch

17
Profiles Walkthrough (iv)

• Apply stereotypes to model elements as desired

Race
Starter
timer
clock StopWatch

resolution 3
18
Profiles walkthrough (v)

• Instance model example

Clock
Class
resolution 3
name StopWatch
19
Pragmatics

• Proof of concept (RFP section 4.8)
• validated by multiple vendors with prototypes and
  implementations
• Other verification validation
• strict reuse by U2P Superstructure and MOF 2.0
  Core
• automated generation of XMI
• partial automated verification of model

20
Pragmatics (contd)

• Compliance
• each InfrastructureLibrary subpackage constitutes
  a separate compliance point
• Changes to OMG adopted specifications
• NA

21
Support for MDA

• Appendix B addresses how U2P proposals support
  MDA concepts
• family of languages
• specifying platform independent models (PIMs) and
  platform specific models (PSMs)
• specifying platforms
• transforming PIMs ? PSMs

22
Requirements Recap (revisited)

• General requirements
• separation of concerns between semantics and
  notation ?
• specify XMI for UML ?
• Architectural alignment and restructuring
• align UML and MOF ?
• package structure that flexibly supports
  compliance points ?
• Extensibility
• profiles ?
• first-class extension mechanism ?

23
Wrap Up

• 3rd revised Infrastructure satisfies all RFP
  mandatory requirements and most optional
  requirements (RFP sections 6.5 6.6)
• summary provided in submission Preface
• Proofs of concept include prototypes and
  implementations (RFP section 4.8)
• Submission is architecturally aligned with
• U2P Superstructure 2.0 (2nd revision)
• MOF 2.0 Core and MOF 2.0 XMI submissions
• Next steps
• provide technical errata and a convenience
  document NLT 3 weeks prior to the Orlando meeting
• all other corrections can be made in an FTF

24
Further Info

• www.u2-partners.org
• mailtou2p-info_at_yahoogroups.com
• mailtou2p-issues_at_yahoogroups.com