UML Conclusion

1
UML Conclusion

• CS 6300
• Fall, 2001

2
Overview

• Sequence diagrams
• Statechart activity diagrams
• Packaging, stereotypes, annotations and
  constraints
• Summary

3
Activity Diagrams

• An activity diagram shows flow control within a
  system
• An activity diagram is a special case of a state
  chart diagram in which states are activities
  (functions)

4
Activity Diagrams

• Two types of states
• Action state
• Cannot be decomposed any further
• Happens instantaneously with respect to
• level of abstraction used in the model
• Activity state
• Can be decomposed further
• Activity is modeled by another activity diagram
• (cf. DFDs?)

5
Activity Diagram Modeling Decisions
6
Activity Diagrams Modeling Concurrency

• Synchronization of multiple activities
• Splitting the flow of control into multiple
  threads

7
Activity Diagrams Swimlanes

• Actions may be grouped into swimlanes to denote
  the object or subsystem that implements the
  actions.

8
Packages Packaging use cases into feature sets
Report

Emergency
Dispatcher
OpenIncident
FieldOfficer
AllocateResources
ArchiveIncident
ManageUsers
Librarian
SysAdmin
SearchArchive
ManageTerminals
9
(No Transcript)
10
Packages Packaging classes into sub-domains or
subsystems
11
Annotations
12
ltltStereotypes in UMLgtgt
E.g. Jacobsons categories of classes in Use-Case
Oriented OOA - Entity objects represent part of
problem domain - Control objects represent
encapsulated behavior - Boundary objects
encapsulate interfaces
13
Constraints in UML
1. Association multiplicity and participation can
be shown directly. - E.g Library patron doesnt
have to borrow books, but can borrow at most six
at a time. 2. Other semantic constraints must be
shown throughannotations or footnotes (or
formally in OCL), e.g - ordering of
collections - constraints on values (e.g. patron
cant borrow more than one copy of a book at
same time)
14
Summary

• UML provides a wide variety of notations for
  representing many aspects of software
  development
• We concentrate only on a few notations
• Functional model use case diagram
• Object model class diagram
• Dynamic model sequence diagrams, statechart and
  activity diagrams
• UML is not a methodology, but the textbook
  describes a methodology that uses UML