Information system writing assignment.

USE CASE #

<< An arbitrary use case number for reference purpose>>

USE CASE Name

<< “Use Verb + Noun” form as the use case name>>

Scenario

<<Specific scenarios of the use case>>

Trigger

<< Which event starts the use case?>>

ACTOR

<< The actor who will be using this use case. You may list more than one actor here>>

Goal (1 phrase)

<< Write a phrase for the goal of the use case in the form of “To + verb + ….”>>

Overview and scope

<< Write 2-4 sentences for the overview and main scope >>

Level

<< Primary or included or extended >>

Stakeholders

<<People who are concerned with the use case>>

Preconditions

<< Non-trivial pre-conditions to execute this use case>>

Postconditions in words (write in passive and past tense)

<< Successful end conditions in business terms. Write them in passive and past tense. Write 3 ideas: (1) What objects were created and deleted in this use case? (2) What attributes changed their values? (3) Which objects were connected/disconnected with which objects? >>

Included Use Cases

<< List of included use case names >>

Extending Use Cases

<< List of extending use case names >>

MAIN SUCCESSFUL SCENARIO in numbered sequence

Reference “included use cases” in this section using INCLUDE ius_name

Italicized terms are defined in Glossary

Actor Action

System Action

1. Actor does this

2. System does that

3. Actor does another

4. System does next thing

5 INCLUDE <<included use case name>> (Comment: This is how we call an included use case.)

6. Actor does

7. System replies

8. Customer pays by credit card

9. Process the credit card

10.

11.

<< Add more rows if you need>>

OTHER SUCCESSFUL SCENARIOS (Specify any successful variations of the normal execution path, including any extension points using

EXTEND eus_name)

Step

Branching Action

2a

<<Branching action of step 2 above>>

2b

<< Another branching action of step 2 above >>

8a Customer pays by cash

9a. System indicates cash and enter amount

8b Customer pays by check

9b. System indicates check and enter amount

<< Add more rows if you need>>

UNSUCCESSFUL SCENARIOS (erroneous situations)

Conditions

Actions

*a

Abort the transaction. <,Here * means this can be executed at any step>>

8c. Customer is short of money;

Abort the transaction

9c. Credit card validation fails

Ask to pay by another means or abort

<< Add more rows if you need>>

Priority in scheduling

<<Classify the use case into first, second, third, depending on the importance. Or Primary/Secondary/Optional>>

Frequency

<<How often will this use case be performed?>>

Business rules and data logic

<< Any integrity constraints on data and business rules related to this use case>>

Other non-functional requirements

<< Optional, non-functional requirements such as performance, reliability, usability, and other design considerations

etc.>>

Superordinates

<<If this is an included or extending use case, which primary use cases call this use case? If it is a primary use case, leave this row blank>>

Developer

<<Who developed this use case?>>

Creation date and last modified date

<< The version dates as stated >>

Glossary

<<Italicized terms are defined here or in the main Glossary>>

Other Comments

<<Any extra comments, time constraints, etc.>>