EXPLOIT THE POWER OF UML

ACCELERATE SOFTWARE DEVELOPME

Class Association Class Diagram: Interfaces

Abstract interface

role B Client
Identify candidate classes.
Class Name Class A Class B Class Interface
dependency Class
Document analysis classes.
Problem {abstract}
Populate
role A
Statement
a Sequence

K E Y N O TAT I O N S
Diagram with
analysis classes. Add

Identify use
Select priority
use case.
a note with interaction text Class Name Multiplicities
cases and Identify preconditions,
from the use case. Find new
realization
document with Use postconditions,
classes and respon-sibilities
by drawing messages.
attribute:Type = initialValue
Case Diagram. Include Name, scenarios, and interactions.
1 Implementing
Description, and Priority for each
use case.
operation(arg list):return type Class exactly one Class
Interface Name
Client
many Class
Generalization * Class (zero or more)
dependency

Implementing
ITERATIVE AND INCREMENTAL Develop Class Diagram
from Sequence
Diagram. Refine by
Supertype 0..1 Class
optional
(zero or one) Class
adding inheritance,
multiplicity, and
Activity Diagram
additional detailed
discriminator Class Diagram:
Refine
remaining
DEVELOPMENT BASED ON design
information.
m..n
Class
numerically
specified
start
use cases Pa ra m e t e r i ze d C l a s s
template class
PRIORITIZED USE CASES Subtype 1 Subtype 2 Class aggregation T Activity

Set fork
Constraint Class composition
{description of constraint}
Class
{ordered} * ordered role bound element
[condition] [else]
Test

Integrate
Generate code from
Class Diagram.
Stereotype
Dynamic *
Set<Integer> branch Concurrent
stereotype name
Qualified Association Activity

Note Class qualifier Activity Activity

Deploy Implement/ Unit Test
merge
some useful text Navigability Association Class
role name
Source Target Class Class join
Object
Dependency
object name: Class Name
Association
Class A Class B Class end

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
Use Case include

Class 1 extension
Use Case Model Design Model Package Name Class 3 points
dependency Class 2
Actor Generalization
Use Case Diagram Class Diagram extend

Use Cases Classes (extension points)
Actors Sequence Diagrams
(one or more per use case) Sequence Diagram
State Diagrams an Object
(to clarify intra- and inter-object behavior) State Diagram
create Deployment Diagram
new Object
Superstate Name
Analysis Model Implementation Model node
message
self-delegation
Domain Model Class Diagram Component Diagrams Component 2 State Name
Temporary Analysis Classes Deployment Diagrams entry/action event(arguments)[condition]/action
return do/activity State Name
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
1: simple message
) (
asynchronous message
State State
1.1*: iteration message
) (
1.2: [condition] message
) (
role name
UNIFIED :class role name object name State State
MODELING
Describe LANGUAGE
UML Diagrams from UML Distilled, Second Edition by Martin Fowler with Kendall Scott with permission of the publisher, Addison Wesley