Page 69 -

36 Part 1 • SyStemS analySiS FundamentalS

Figure 2.16
A use case scenario is divided
into three sections: identification Use case name:
and initiation; steps performed; Area: Register for Conference
and conditions, assumptions, and Actor(s): Conference Planning UniqueID: Conf RG 003
questions. Participant
Stakeholder:
Level: Conference Sponsor, Conference Speakers
Blue
Description:
Triggering Event: Allow conference participant to register online for the conference using a secure Web site.
Trigger type: Participant uses Conference Registration Web site, enters userID and password, and clicks the logon button.
External
Temporal
Steps Performed (Main Path)
Information for Steps
1. Participant logs in using the secure Web server.
userID, Password
2. Participant record is read and password is verified.
Participant Record, userID, Password
3. Participant and session information is displayed on the
Registration Web page.
Participant Record, Session Record
4. Participant enters information on the Registration Web form
and clicks Submit button.
Registration Web Form
5. Registration information is validated on the Web server.
Registration Web Form
6. Registration Confirmation page is displayed to confirm
registration information.
Confirmation Web Page
7. Credit card is charged for registration fees.
Secure Credit Card Web Page
8. Add Registration Journal record is written.
Confirmation Web Page
9. Registration record is updated on the Registration Master.
Confirmation Web Page, Registration Record
10. Session record is updated for each selected session on
the Session Master. Confirmation Web Page, Session Record
11. Participant record is updated for the participant on
the Participant Master. Confirmation Web Page, Participant Record
12. Successful Registration Confirmation Web page is sent to
the participant.
Preconditions: Registration Record Confirmation Number
Postconditions: Participant has already registered and has created a user account.
Assumptions: Participant has successfully registered for the conference.
Success Guarantee: Participant has a browser and a valid userID and password.
Minimum Guarantee: Participant has registered for the conference and is enrolled in all selected sessions.
Participant was able to logon.
Requirements Met:
Outstanding Issues: Allow conference participants to be able to register for the conference using a secure Web site.
Priority: How should a rejected credit card be handled?
High
Risk:
Medium

The first area, use case identifiers and initiators, orients the reader and contains the use case
name and a unique ID; the application area or system that this use case belongs to; the actors
involved in the use case; and the stakeholders that have a high level of interest in the use case.
Some stakeholders never interact directly with the system, such as the stockholders, the board
of directors, or the sales manager. Each primary actor is a stakeholder but not listed in the stake-
holder area. The first area should therefore include the level (blue, kite, and so on) and a brief
description of what the use case accomplishes.
The header concludes with the initiating (triggering) event—that is, what caused the use case
to start—and the type of trigger, either external or temporal. External events are those started by
an actor, either a person or another system requesting information, such as an airline reserva-
tion system requesting flight information from an airline system. Temporal events are those that
are triggered or started by time. Events occur at a specific time, such as sending an email about
special offers once a week on a Sunday evening, sending bills on a specific day, or generating
government statistics on a specified date every quarter.