Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

Brief Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or Low

Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.

Use Case Number
The author-

assigned number to refer to each specific use case. The format of this number is

<SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>

, for example

Init1dbw1.1,

Init1dbw1.2,

Init2dbw2.1, 2.2, etc.

Brief Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

Actor(s)

for this particular use case

Pre-condition

The state of the system before the user interacts with it

Post condition

The state of the system after the user interacts with it

Steps to take

The step-by-step description of how users will interact with the system to achieve a specific business goal or function

Alternate Flow

Things which would prevent the normal flow of the use case

Priority

The priority of implementing the use case

: High, Medium or Low

Associated Links

The brief user stories

, each

describing the user interacts with the system for

the one function only of the use case. There would potentially be a number of user stories that make up the use case.

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

Brief Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

Alternate Flow

Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or Low

Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.

Use Case Number
The author-assigned number to refer to each specific use case. The format of this number is <SemCon Ops Initiative><analyst's initiatls><requirement number>.< <use case number>, for example Init1dbw1.1, Init1dbw1.2, Init2dbw2.1, 2.2, etc.

Brief Narrative/Description (a description of the actor, the business objective or goal, and the main success scenario)

Actor(s) for this particular use case

Pre-condition
The state of the system before the user interacts with it

Post condition
The state of the system after the user interacts with it

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

Alternate Flow
Things which would prevent the normal flow of the use case

Priority
The priority of implementing the use case: High, Medium or Low

Associated Links

The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.