Use Cases

Use cases document during the analysis phase the intended procedures out of the
view of actors for isolated cases.

Actors are active participants from which processes start (by generating an
external event) or who keep processes continually running.

Actors may be
humans, who work interactively with the system,

other systems, that use network communications, and

internal components, that keep continually running (like the system's

clock).

Use cases are documented informally by a sequence of steps (with possibly

exceptions) and may be summarized in a graphical form by presenting actors and
single cases.

Copyright © 2001, 2002 Andreas Borchert, converted to HTML on February 21, 2002

Class Diagrams
 Class diagrams consist of classes and their relationships.

Class boxes consist of a class name, a set of public fields, and public methods.

Most relationships within class diagrams express a structural reference that is later
to be reflected in the data structure. In this example, a department object is able to
provide a list of the employees that are associated with it.

The numerical ranges (e.g. ``*'', ``1..*'' or ``0..1'') specify the multiplicity of a
structural relationship. A department, for example, has no or one department head
but an employee may be head of any number of departments.

Copyright © 2001, 2002 Andreas Borchert, converted to HTML on February 21, 2002

Sequence Diagrams
 Sequence diagrams model the control flow for small scenarios.

The scenarios may (but do not have to) come from the use cases.

They demonstrate how actors and classes interact with each other in a sequential
form.

Copyright © 2001, 2002 Andreas Borchert, converted to HTML on February 21, 2002