12 Steps to Use Case Specification (UC)

1. Purpose: Stated purpose of UC
2. Agent, general description: If the agent of UC, describes the process of implementing UC
3. Flow of key events: Outlined the main event, processes, manipulation of UC
4. Flow replacement: Mentioned sub-flows encountered
5. The specific requirements: Required to implement UC
6. Conditions ago: Conditions Required to start as UC
7. Following conditions: Condition or results after implementing UC
8. The extension point:
9. Graphed context
10. Chart activities
11. Statecharts
12. The scenario

For example, implementation specifications UC

We perform such specification login UC library management system

Purpose: Ensure authentication user information safe and secure system

Agent, general description:
Agent: Readers, Library staff, System Administrator
General Description: Users (Readers, Library staff, System Administrator) when you want to manipulate the system as loan payment, change information, Information Management,… must log on to the system.

Flow of key events:

Actions of agents

1. Select the log function

–

3. Enter your login information

4. Send the information entered to the system

The reaction of the system

–

2. Show login form

–

–

5. Check credentials, If true, allows access, wrong message asking to re-enter

Flow replacement: If the user enters the wrong information required to re-enter, but only within the limits allowed

The specific requirements: Username and password match those registered.

Conditions ago: Users have to register in the system

Following conditions: Notice successful login / failure

The extension point: Without.

Graphed context

Chart activities

Statecharts

The scenario

• B1, B2, B3, B4, B5, B6
• B1, B2, B3, B4, B5, A1, B2, B3, B4, B5, B6
• B1, B2, B3, B4, B5, A1, B2, B3, B4, B5, A1, B2, B3, B4, B5, B6