Use Cases

In OO design, use case models and diagrams are the

equivalent to the DFD and process diagrams in structured
design. The use case model is a higher level view of the
process. In use case, modeling a business function is
defined and contains an actor, which is a role that
performs the function. A single function is called a use
case. Continuing to use the time reporting object design
from above, an actor would be Supervisor, and a use case
would be PROCESS TIME ENTRY. The use case is
documented and the steps are written out with pre and
post step conditions, successful outcomes, and alternate
outcomes.

Use case diagrams are more levels of process

interactions. Therefore, the use case diagram would have
both the Employee and Supervisor objects diagrammed
into a single business process. The difference between the
use case diagram and the use case model is that the use
case model is a single defined use case.

Additional diagram methods are available in OO design for

deeper technical diagramming. In most systems analyst
designs, diagram methods that are more involved and
technical are not used unless specifically required. The
modeling output using the objects, classes, attributes,
methods, instances, inheritance, actors, and use cases,
are more than enough to properly generate the logical
design of the system. For reference, other diagram options
noted in the text reading are class diagrams, sequence
diagrams, state transition diagrams, activity diagrams, and
the larger system view, using business process modeling.

In Module Six, the class will use the outputs from the prior
modules to complete the system analysis process and
begin the transition into system design.