Page 293 -

260 Part 3 • the analysis Process

Figure 10.5 Use Case Diagram
An overall view of UML
diagrams, showing how each may create one
Each use case
diagram leads to the activity diagram.
development of other UML
diagrams.
Activity Diagram

Use case
scenarios may
be generated from
the use case
diagram.

Use Case Scenario

Identifiers
Use cases and
Steps create one
Each use case
sequence
scenario may
diagrams
Conditions sequence
help determine
classes. diagram.
Class Diagram Sequence Diagram Communication Diagram

1 1..

1 1

Statechart Diagram diagram to help interchangeable.

Sequence and
communication
diagrams are

Each class may
have a statechart
determine
operations.

or the method of implementation. Students could be added in person, using the Web, using a touch-
tone telephone, or any combination of these methods. The Add Student use case includes the Verify
Identity use case to verify the identity of the student. The Purchase Textbook use case extends the
Enroll in Class use case, and may be part of a system to enroll students in an online course.
It may seem as if the Change Student Information use case is a minor system feature and
should not be included on the use case diagram, but because this information changes frequently,
administration has a keen interest in allowing students to change their own personal information.
The fact that the administrators deem this to be important not only justifies, but calls for, the use
case to be written up.
Students would not be allowed to change grade point average, outstanding fees, and other
information. This use case also includes the Verify Identity use case, and in this situation, it means
having the student enter a user ID and password before gaining access to the system. View Student
Information allows students to view their personal information, as well as courses and grades.