Software Design Center

HOW TO DRAW JACOBSON'S OOSE DIAGRAMS (cont'd)


Jacobson's Use Case Diagrams
Use case diagrams illustrate how the outside world interacts with elements of the application system.

A Jacobson use case diagram
A Jacobson use case diagram


To see the basic use case notations and learn how to construct a use case diagram, visit the UML section on use case diagrams.



Jacobson's Analysis Model
Jacobson's analysis model defines three types of objects in a system: interface objects, entity objects, and control objects.

Entity Object

Entity object
Information about an entity object is stored even after a use case is completed.
Learn how to edit text on this object.

Control object

Control object
A control object illustrates functionality that is not contained in any other object in the system.

Interface object

Interface object
Interface objects interact directly with the environment.
Learn how to connect objects.



Jacobson's Design Model
Jacobson's design model shows how the system behaves. There are two types of diagrams under this model: interaction diagrams and state transition diagrams. Interaction diagrams are similar to UML's sequence diagrams. State transition diagrams are like UML statechart diagrams, but Jacobson also employs a number of unique symbols listed below.

Send Message


Send Message

Receive Message


Receive Message

Return Message


Return Message

Send Signal


Send Signal

Receive Signal


Receive Signal

Perform Task


Perform Task

Decision


Decision

Label


Label