>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [papers] >> 20050502Outline
[Index] [Contents] [Source] [Notation] [Copyright] [Comment] [Search ]
Fri May 12 15:31:29 PDT 2006

Disclaimer. CSUSB and the CS Dept have no responsibility for the content of this page.

Copyright. Richard J. Botting ( Fri May 12 15:31:29 PDT 2006 ). Permission is granted to quote and use this document as long as the source is acknowledged.

• Changes in the Unified Modeling Language
• : Sources
• : What is the UML?
• : : Structure Diagrams
• : : Behavior Diagrams
• : Who uses the UML?
• : What for?
• : An Example of a Change in Deployment Diagrams and Components
• : An example of a Bad old Collaboration Diagrams
• : Rick Bruner's Conclusions
• : Complex Specification
• : Controlling the Monster
• : A Few Changes in Detail

Changes in the Unified Modeling Language

Sources



1. UML 2.0 specifications, Object Management Group, [ modeling_spec_catalog.htm ]
2. James Rumbaugh, Ivar Jacobson, Grady Booch, The Unified Modeling Language Reference Manual, Addison Wesley 1999, QA76.76 D47 R86
3. Rick Bruner CSci595 Ind Stud Winter 2004
4. Cynthia Farquhar, "An Empirical Study of the Usage of UML in the BS and MS Programs at CSUSB", CSci. Thesis Winter 2005, CSUSB
5. Martin Fowler, "UML distilled", 3rd edition, Addison-Wesley 2004, ISBN 0-321-19368-7
6. Craig Larman, "Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process", 2/E, Prentice-Hall 2005, ISBN: 0-13-092569-1
7. J Arlow & I Neustadt, Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML Addison Wesley Longman Publishing Co, Inc., Redwood City, CA, 2003
8. RJBotting, "On the Co-Evolution of SSADM and the UML" Chapter V in "UML and XML" Idea Books, Hershey PA 2005 [Yang05]
9. Conrad Bock, Journal of Object Technology, [ search_results?PrincipiaSearchSource=Bock ]
10. Dr. Zemoudeh, Report to faculty on CS/CIS CSU Chairs meeting, May 1st 2005



What is the UML?

A set of rules for drawing and interpreting diagrams:

Structure Diagrams	Behavior Diagrams

Structure Diagrams

• Class Diagram
• Composite Structure Diagram
• Component Diagram
• Deployment Diagram
• Object Diagram
• Package Diagram

Behavior Diagrams

• Activity Diagram
• Interaction Diagrams
  • Sequence Diagram
  • Communication (Collaboration) Diagram
  • Interaction Overview Diagram
  • Timing Diagram
• Use Case Diagram
• State Machine Diagram

. . . . . . . . . ( end of section What is the UML?) <<Contents | End>>

Who uses the UML?

1. 46% of our undergraduates and graduates say the use the UML regularly [ Farquhar]

2. All of the CSU CS/CIS depts use it [Dr. Zemoudeh, May 1st 2005]

   What for?

   Purpose	Always	Often	Occasionally	Never
   Sketch	6%	21%	51%	22%
   Blueprint	6%	23%	32%	38%
   Programming language	4%	13%	21%	62%
   Required documentation	12%	33%	38%	17%

   (Sample 2004 of 306 CSUSB CSci students 50/50 undergraduate/graduate)

   An Example of a Change in Deployment Diagrams and Components

   Most of our Masters Projects have a diagram like this.

   
   

   1. The syntax of components has changed.
   2. Components are not put on Deployment diagrams.
   3. Some of these components should be artifacts.
      Some should be Execution Environments.
   
   

   An example of a Bad old Collaboration Diagrams

   The word collaboration developed a new meaning and is now reserved for that use: a parameterized OO Pattern.

   The old diagrams showed little tokens for data being moved between objects:

   

   These would no longer be shown.

   The above diagram needs a complete redrawing.

   Rick Bruner's Conclusions

   "The OMG has engaged in a courageous effort to keep the size of UML 2.0 to a minimum. Despite the fact that it has retired 25 predefined elements and removed 28 other features, it ADDED 56 NEW features and 5 NEW diagram types ( Object, Package, Interaction Overview, Timing, and Composite Structure Diagrams)."

   "The UML documentation went from slightly over 600 pages to a little over 800 pages!"

   Complex Specification

   Two levels: infrastructure and superstructure documents. The infrastructure specification explains the rules for drawing and interpreting the superstructure (I think).

   Controlling the Monster

   UML controls a potentially increasing core size by extending it in four ways:

   Extension	Example
   Stereotypes	<<applet>>
   Tagged Values	{manifests = "PayPacket"}
   Profiles	Data Bases, Real Time, ....
   Metamodel changes	Most published academic papers!

   A Few Changes in Detail

   New	Name	Notes
   +	Object and Package Diagrams	Now Official
   -	Components	Internalized icon
   +	Composite Structure Diagrams	cups & balls
   -	Component Diagrams	Information flows + stereotypes = DFDs
   -	Sequence Diagrams	+ structures
   -	Communication Diagrams	New name. Simplified and clarified.
   -	Activity Diagrams	Flow Charts + Exceptions + Flows
   -	Deployment	+ Execution Environments + Artifacts - Components
   -	Artifact stereotypes:	file document executable library script source
   +	Interaction Overview Diagram	Activity diagram containing Sequence diagrams
   +	Timing Diagrams	The Electronic Engineer's Friend[Babbage]
   -	OCL/MOF/CWMF/...	Too many TLAs(Three Letter Acronyms)
   -	MDA - Model Driven Architecture	Tomorrow the World

   [ 20050502Body.html ]

. . . . . . . . . ( end of section Changes in the Unified Modeling Language) <<Contents | End>>