EXPLOIT THE POWER OF UML
ACCELERATE SOFTWARE DEVELOPME
Class Class Diagram: Interfaces
Association
«interface
»
Abstract Client
role B
Interface
Class
Identify candidate classes.
Class A Class B
Class Name
dependency Class
Document analysis classes.
Problem {abstract}
role A
Populate
Statement
a Sequence
K E Y N O TAT I O N S
Diagram with
analysis classes. Add
Multiplicities
Class Name
Select priority a note with interaction text
Identify use use case.
realization
from the use case. Find new
cases and Identify preconditions,
attribute:Type = initialValue
classes and respon-sibilities
document with Use postconditions, by drawing messages.
Implementing
1
Case Diagram. Include Name, scenarios, and interactions.
Class exactly one
operation(arg list):return type
Description, and Priority for each
Class
use case.
Interface Name
Client
Class
many
* dependency
Generalization Class (zero or more)
Implementing
ITERATIVE AND INCREMENTAL optional
Develop Class Diagram
Supertype 0..1 Class
Class
from Sequence
(zero or one)
Diagram. Refine by
Activity Diagram
adding inheritance,
multiplicity, and
discriminator
additional detailed
Class Diagram:
DEVELOPMENT BASED ON numerically
m..n start
design
Class
Refine information.
specified
remaining
Pa ra m e t e r i ze d C l a s s
use cases
template class
PRIORITIZED USE CASES Activity
T
Subtype 1 Subtype 2 aggregation
Class
Set fork
composition
Class
Constraint
* ordered role
{description of constraint} {ordered} bound element
Class [condition] [else]
Test
*
Generate code from
Dynamic
Class Diagram.
Stereotype
Integrate
Concurrent
Set<Integer> branch
Qualified Association
«stereotype name
» Activity
Activity Activity
Note Class qualifier
Deploy Implement/ Unit Test
merge
Navigability
some useful text
Association Class
role name
Source Target Class Class join
Object
Dependency
Association
object name: Class Name end
Class
Class A Class B
The following artifacts are created and maintained in Describe™. Each model is represented as a
package. Reverse-engineered code is created and maintained in a separate system, with the package Pa ck a g e D i a gra m
names consistent with implementation. Use Case Diagram
Package
Name
«include
»
Use Case
Class 1 extension
Package Name points
Class 3
Use Case Model Design Model dependency Class 2
Actor Generalization
• Use Case Diagram • Class Diagram «extend
»
• Use Cases • Classes (extension points)
• Actors • Sequence Diagrams
Sequence Diagram
(one or more per use case)
• State Diagrams an Object
(to clarify intra- and inter-object behavior) State Diagram
Deployment Diagram
create
new Object
Superstate Name
node
Implementation Model
Analysis Model
message
self-delegation
State Name
Component 2
• Component Diagrams
• “Domain Model” Class Diagram
• Deployment Diagrams entry/action event(arguments)[condition]/action
• Temporary Analysis Classes
State Name
do/activity
return
exit/action
Component 1 event/action (arguments)
delete
For additional resources and tools, visit Concurrent States
Collaboration Diagram
Superstate Name
www.e m b a r c a d e ro.c o m object name: class
asynchronous message
State State
1: simple message (
)
1.1*: iteration message (
)
1.2: [condition] message (
)
role name
State State
:class object name
UNIFIED role name
MODELING
Describe™ LANGUAGE
UML Diagrams from UML Distilled, Second Edition by Martin Fowler with Kendall Scott with permission of the publisher, Addison Wesley