0% found this document useful (0 votes)
133 views6 pages

Pharmacy Management System

The document outlines test criteria, functional and non-functional requirements, and test objectives for a pharmacy management system. It includes entry and exit criteria for system verification tests, as well as functional requirements like drug information, financial reports, and customer records. Non-functional requirements specify the system must have a user-friendly interface and reliable data protection. Test cases are provided to test functions like user login, adding patient and doctor records, and generating bills. The testing will verify key system functions and ensure compliance with requirements.

Uploaded by

Rupesh Patil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
133 views6 pages

Pharmacy Management System

The document outlines test criteria, functional and non-functional requirements, and test objectives for a pharmacy management system. It includes entry and exit criteria for system verification tests, as well as functional requirements like drug information, financial reports, and customer records. Non-functional requirements specify the system must have a user-friendly interface and reliable data protection. Test cases are provided to test functions like user login, adding patient and doctor records, and generating bills. The testing will verify key system functions and ensure compliance with requirements.

Uploaded by

Rupesh Patil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Test criteria

Entry criteria:-
System Verification Test want to require that all functional verification tests have been
attempted and that 95% have been completed;
a Functional Verification Test team might want to require that the user interface is
frozen.
Exit Criteria:-
a System Verification Test want to require that all System Verification Tests have
been attempted and that 95% have been completed.
Functional Requirements
There are functions done by the system such as: the necessary information of drugs,
prepare profit and loss statement, customer records, debtors records, preparing of
invoices, Calendar, sales records, stock management, gives daily reports, easily
searching of medicine, Update, delete and printing all reports within the system.
Non-Functional Requirements

Pharmacy Management system is able to operate in the following characteristics. 


Any familiar in using windows operation can operate the system since it have user
friendly and easy to use user interface.  Reliability: The pharmacy system is
available based on the user needs, can work properly and do transactions efficiently
including safe management of the pharmacy. The pharmacy system is password
protected to change things on the system. Here the pharmacist Manager control over
the system by login to the pharmacy system. Any user can not use the system without
registered by the Administrator and all result data is protected and controlled by the
Administrator.
SRS Specification :-
A Software requirements specification (SRS), a requirements specification for a
software system, is a complete description of the behavior of a system to be
developed and may include a set of use cases that describe interactions the users will
have with the software. In addition it also contains non-functional requirements. Non-
functional requirements impose constraints on the design or implementation (such as
performance engineering requirements, quality standards, or design constraints)
Product Analysis :-
The system will allow access only to authorized users with specific roles
(Administrator, Operator). Depending upon the user’s role, he/she will be able to
access only specific modules of the system.
A summary of the major functions that the software will perform:
i. A login facility for enabling only authorized access to the system.
ii. When a patient is admitted, the front-desk staff checks to see if the patient is
already registered with the hospital. If he is, his/her Name is entered into the
computer. Otherwise a new Patient ID is given to this patient.
iii. If a patient checks out, the administrative staff shall delete his patient ID from the
system.
iv. The system generates reports on the following information:
v.List of detailed information regarding the patient who has admitted in the hospital.
Test Objectives:-
1. To computerize all details regarding patient details & hospital details.
2. Scheduling the appointment of patient with doctors to make it convenient for both.
3. Scheduling the services of specialized doctors and emergency properly so that
facilities provided by hospital are fully utilized in effective and efficient manner.
4. If the medical store issues medicines to patients, it should reduce the stock status
of the medical store and vice-versa.
5. It should be able to handle the test reports of patients conducted in the pathology
lab of the hospital.
6. The inventory should be updated automatically whenever a transaction is made.
7. The information of the patients should be kept up to date and there record should
be kept in the system for historical purposes.
Test Deliverables:-
The application will have a user friendly and menu based interface. Following screens
will be provided.
i. A Login Screen for entering username, password and role (Administrator, operator)
will be provided. Access to different screens will be based upon the role of the user.
ii. A Form for Search the details of a patient.
iii. The Form for creating a new patient record will contain text fields where the Patient
ID will be machine generated and the rest of the details will have to be filled up.
iv. A Form for generating the tests reports.
v. The Form to produce a bill will create fields such as Patient ID, Appointment No.,
Doctor’s charges, Hospital charges etc. which will need to be filled up.
Testing Cases :-

Test Test Expected Expected Actual Input Actual Output

Case ID Input Output

1. Login Form Username, Homepage admin, Login


Successfully
Eg:-ABC

Password

Eg:-13sbc

2. ID Integer Doctor Form ID of the Doctor Msgbox “Record


Eg:-12345 page
Added

Successfully!”

3. Name Character Doctor Form Name of the Msgbox “Record


Eg:-Raju page Doctor
Added

Successfully!”

4. Address Character Doctor Form Address of the Msgbox “Record


Eg:-Nashik page Doctor
Added

Successfully!”

5. Phone Number Integer Doctor Form Contact number Msgbox “Record


Eg:-1234567894 page of the doctor
Added

Successfully!”
6. Qualification Character Doctor Form Qualification of Msgbox “Record
Eg:-M.B.B.S page the Doctor
Added

Successfully!”

7. Gender Character Doctor Form Gender of the Msgbox “Record


Eg:-Male, page doctor
Added
Female
Successfully!”

8. Patient_no Integer Patient Form ID of the Patient Msgbox “Record


Eg:-P_01 Page
Added

Successfully!”

9. Name of Character Patient Form Name of the Msgbox “Record


Patient Eg:-M.B.B.S Page patient
Added

Successfully!”

10. Age Integer Patient Form Age of the Msgbox “Record


Eg:-19 Page Patient
Added

Successfully!”

11. Gender Character Patient Form Gender of the Msgbox “Record


Eg:-Male, Page Patient
Added
Female
Successfully!”

12. Address Character Patient Form Address of the Msgbox “Record


Eg:-Nashik Page Patient
Added

Successfully!”

13. Date Datetime Patient Form Date of Msgbox “Record


Eg:-1/1/2021 Page admission
Added

Successfully!”

14. Contact Number Integer Patient Form Contact number Msgbox “Record
Eg:-1234567894 Page of the patient
Added

Successfully!”
15. Room No Character Patient Form Admitted patient Msgbox “Record
Eg:-P_01 Page room no.(in case
Added
of IP)
Successfully!”

16. Bill_no Integer Billing Form Number of the Msgbox “Record


Eg:-B_01 Page Bill
Added

Successfully!”

17. Date Datetime Billing Form Date at which bill Msgbox “Record
Eg:- 21/1/2021 Page is generated
Added

Successfully!”

18. Patient Id Character Billing Form Id of the patient Msgbox “Record


Eg:-Pid_01 Page
Added

Successfully!”

19. Name Character Billing Form Name of the Msgbox “Record


Eg:-Ramesh Page Patient
Added

Successfully!”

20. Age Integer Billing Form Age of the Msgbox “Record


Eg:-19 Page patient
Added

Successfully!”

21. Gender Character Billing Form Gender of the Msgbox “Record


Eg:- Male, Page Patient
Added
Female
Successfully!”

22. Date of Admission Datetime Billing Form Date on which Msgbox “Record
Eg:-2/1/2020 Page patient is
Added
admitted into
Successfully!”
Hospital
23. Date of Discharge Datetime Billing Form Date on which Msgbox “Record
Eg:-2/2/2021 Page patient is
Added
Discharged from
Successfully!”
the Hospital
24. Room Charges Integer Billing Form Charges of the Msgbox “Record
Eg:-100 Page room
Added

Successfully!”

25. Pathology fees Integer Billing Form Laboratory Msgbox “Record


Eg:-150 Page report Charges
Added

Successfully!”

26 Doctor Fees Integer Billing Form Doctor Checkup Msgbox “Record


Eg:-200 Page Fees
Added

Successfully!”

.27. Miscellaneous Integer Billing Form Other Charges Msgbox “Record


Eg:-100 Page
Added

Successfully!”

28. Total Amount Integer Billing Form Total amount of Msgbox “Record
Eg:-19000 Page the bill
Added

Successfully!”

You might also like