Skip to content
This repository has been archived by the owner on Aug 11, 2019. It is now read-only.

To Do Use Case ( Template )

dcy2011 edited this page Jun 1, 2011 · 1 revision

USECASENAME

Brief Description

The description should briefly convey the role and purpose of the use case.

Flow of Events

Basic Flow

This use case starts when the actor does something. An actor always initiates use Cases. The use case should describe what the actor does and what the system does in response. It should be phrased in the form of a dialog between the actor and the system.

Basic Flow 1 Basic Flow 2

Alternative Flows

More complex alternatives should be described in a separate section, which is referred to in the basic flow-of-events section. Think of the alternative flow sections like "alternative behavior"

Alternative Flow 1 Alternative Flow 2

Special Requirement(s)

Pre-Conditions

Pre-condition (of a use case) is the state of the system that must be present prior to a use case being performed.

Post-condition

Post-condition (of a use case) is the state of the system that must be present after the use case has been performed.

User Interface

This section captures all the screen shots involved in this use case

Fields, structure and validation rules for the above page.

Name Required Length Display Type Data Type Validations

Clone this wiki locally