Vous êtes sur la page 1sur 3

Use Case Specification

1: Login
1.1 Brief Description:
This use case describes how a user logs into the Library Management System .
1.2 Flow of events:
1.2.1 Basic flow:
This use case starts when the actor wishes to log into the System.
The system requests that the actor enter his/her name and password.
The actor enters his/her name and password.
The system validates the entered name and password and logs the actor into the
system.
1.2.2Alternative Flow:
Invalid Name & Password:If in the basic flow; the actor entered an invalid name or password
the system displays an error message. The actor can choose to either return to the beginning of
basic flow or cancel the login; at which point the use case ends.
1.3 Special requirement: None
1.4Pre-condition: None
1.5 Post-condition:
If the use case was successful; the actor is now logged into the system. If not; the system
state is unchanged.
1.6 Extension point : None

2: Maintain User Record


2.1 Brief description:
This use case allows the admin to manage the user information. This includes modify and
deleting user form or to the system.
2.2 Flow of event:
2.2.1 Basic flow:
This use case starts when the admin wishes to add change or delete user information in the
system.
The system request that the admin specify the function he/she would like to
perform(either Update a user or Delete a user)
Once the admin provides the requested information one of the sub flow is executed.
If the admin selected update a user the Update a user sub flow is executed.
It the admin selected delete a user the Delete a user sub flow is executed.

2.2.1.1 Update a user:


The system request that the admin entered the user-id.
The admin enter the user id; the system retrieves and displays the user
information.
The admin makes the desired changes to the user information.
Once the admin updates the necessary information; the system updates the user
record.
2.2.1.2 Delete a user
The system request that the admin entered the user-id.
The admin enter the user id; the system retrieves and displays the user
information.
The system prompts the admin to confirm the deletion of the user.
The admin verifies the deletion.
The system deletes the user from the system.
2.2.2 Alternative Flow:
2.2.2.1 User not found
If in the update or delete users sub flow, a user with the specified ID no does not exist;
the system displays an error message. The admin can then enter a different id no. of cancel the
operation at which point the use case ends.
2.2.2.2 Delete Cancelled
If in the delete a user sub flow the admin decides not to delete the user the delete is
cancelled and the basic flow will be restarted from the beginning.
2.3 Special Requirement:
None

2.4 Pre Condition:


The admin must be logged onto the system before this use case design.
2.5 Post Condition:
If the use case was successful the users information is updated or deleted from the system
otherwise the system state has been unchanged.
2.6 Extension point
None