UML 2.0 Infrastructure Submission 3rd revision

1
UML 2.0 Infrastructure Submission (3rd revision)

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

2
Overview

• Proposal status
• Change summary
• Satisfaction of Requirements
• 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
• Change summary
• ad/03-03-07 changes apply to ad/03-01-01
• Convenience documents ad/03-03-01 (PDF),
  ad/03-03-03 (XMI), and ad/03-03-05 (MDL)
• Abstract syntax changes detailed in ad/03-03-36

4
U2 Partners

• Submitters
• Alcatel, CA, Ericsson, HP, IBM, I-Logix, IONA,
  Kabira, Motorola, Oracle, Rational, SOFTEAM,
  Telelogic, Unisys
• New Adaptive, Borland, Domain Architects, MEGA
  International, Project Technology
• 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
Change Summary

• Minor changes
• model corrections to produce XMI
• bug fixes
• types
• expressions
• Changes are within normal scope of technical
  errata
• See ad/03-03-07 for details

6
Expressions
TypedElement
operand
ValueSpecification
ordered, subsets ownedElement

expression
0..1
subsets owner
Expression
OpaqueExpression
LiteralSpecification
InstanceValue
body String language String 0..1
symbol String
7
Types
NamedElement
MultiplicityElement
type
TypedElement
Type
0..1
/feature
/featuringClassifier
union
union
Classifier
Feature
1..

8
Satisfaction of Requirements

• 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 ?

9
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

10
Pragmatics (contd)

• Compliance
• each InfrastructureLibrary subpackage constitutes
  a separate compliance point
• compliance options no, partial, compliant
  interchange
• Changes to OMG adopted specifications
• NA for itself (as a reusable library)
• UML Infrastructure UML Superstructure
  recommended to completely replace UML 1.x and UML
  1.y with Action Semantics

11
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

12
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
• vote to recommend to adopt

13
Further Info

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