Documentation Property of Use Case

To fully specify a use case its documentation must contain:

1.

Purpose: goal being achieved, functionality provided by it

2.

User: actor initiating it

3.

Messages exchanged with actors: events, updates, retrievals, decision making

4.

Generalisations

5.

Extension stereotypes: <include>> & <<extend>>

6.

Scenarios as use case instances to complement use case description

7.

Alternative scenarios and Exceptions

8.

Succinct but informal for communicating with user

9.

Termination conditions, results returned to actors

10.

Activity diagrams to supplement the use case, if needed

11.

Example: Register for Course use case:

(a)

Use case started by Student

(b)

Provides facility to create, delete, modify, and/or review a student schedule for a specified term