Use Cases Description

You might also like

Download as odt, pdf, or txt
Download as odt, pdf, or txt
You are on page 1of 4

Formal Description Of Use Cases 1.

Log-in/log-out Description :
Admin or Employee can log-in/log-out the system.

Actor :
Admin or Employee.

Pre Condition :
user have a valid user name or password.

Basic Flow :
1. user supplies valid user name or password. 2. After log-in there are various option which user see.

Post Condition :
user log-in and see various option to manipulate the system.

Exception :
1.The Password or user id is not valid. 2. System not responding.

2. Data Entry Description :


Admin or Employee enter data into the system.

Actor :
Admin or Employee.

Pre Condition :
The data must be valid.

Basic Flow :
1. The Admin and Employee have right to enter data. 2. But The only Admin have rights to do modification.

Post Condition :
After log-in the system both see various options to manipulate the system. And chose the option according to their requirements.

Exception :
1.System not working properly. 2. Data Redundancy.

3. Invoice/Receipt

Description :
Admin or Employee can make Invoice/Receipt.

Actor :
Admin or Employee.

Pre Condition :
The Form must be filled

Basic Flow :
1. The Admin And Employee can log-in the system. 2. And have rights to make invoice/Receipt.

Post Condition :
After log-in and filling form correctly . They click button to print Receipt.

Exception :
1.The Printer not working 2. Error in filling form.

4 . Modify/Update Description :
Admin have only rights to do modification.

Actor :
Admin

Pre Condition :
Before do modification the admin must log-in into the system.

Basic Flow :
After log-in into the system the admin can check data and do modification according to the requirements.

Post Condition :
After log-in the data must be saved correctly.

Exception :
1.Redundancy.

2. Id/Password not valid.

5. Test Library Description :


After log-in into the system the admin perform different test according to the patient requirements.

Actor :
Admin

Pre Condition :
In test library the mentioned test must be available.

Basic Flow :
1. in test library there are different options of available tests. 2. Admin have right to perform different test which patient demand.

Post Condition :
After log-in the test library option will be shown. The user (admin) go to the required test and then print the detail of the test.

Exception :
1. System not responding.

6. Doctor Description :
Admin or Employee both interact with doctor to get patient detail and requirements.

Actor :
Admin or Employee.

Pre Condition :
Either doctor recommend the patient or patient come itself.

Basic Flow :
1. The record of patient who referred by doctor must be store and saved in database. 2. Share of doctor according to the patient category must also be saved.

Post Condition :

The Doctor who refer patient must be in laboratory panel.

Exception :
1.Invalid Doctor Id. 2. System Error.

7. Print Report Description :


After log-in into the system the admin and doctor both have rights to print reports.

Actor :
Admin or Employee.

Pre Condition :
After log-in into the system the lab Id and doctor Id must be correct.

Basic Flow :
1.After log-in into the system and performing all other task such as patient name, lab id, doctor name who refer the patient.

Post Condition :
After log-in and printing reports the user must need to keep the record in their system.

Exception :
1.Printing Error. 2. System not working properly.

You might also like