Table of Contents

Overview 3.3.1 Usability 3.3.2 Reliability 3.4 Performance Requirements 3.4.1 Response Time 3.4.2 Manager Response 3.4.3 Throughput 4. Logical Database Requirements 2 2 5 5 5 5 6 6 6

1. Introduction
Purpose The purpose of this document is to describe the requirements of an automated Medical store management system. This document will be the base for system design phase of the software development lifecycle and is also used for acceptance testing and designing test cases by the testers. It will also form the basis of contract between the user and developing organization and will be used during maintenance. Scope The intended product automates the working of a Medical store of the hospital thereby providing efficient services to the customers, doctors and the store manager. After installation of the system the customer would be able to get the prescribed medicines form the store and doctors will be able to check the medicines available and can even order if required any. Definitions Store Manager: the person who is in charge of overall working of Medical store. Customer: Customer is the person who requires the medicines or any other instrument or product. Employee: He is the person who deals directly with the customer and satisfies all his queries. D.B.A: The database administrator who will look after the database of the store References

K.K. Aggarwal Sangeeta Sabharwal Roger S.Pressmann Website: www.scribd.com www.ieee.com www.hitech-on-web.com

Overview The SRS will provide a detailed description of the medical store management System. This document will provide the outline of the requirements, overview of the characteristics and constraints of the system. The SRS will provide the general factors that affect the product and its requirements. It provides the background for those requirements. The items such as product perspective, product function, user characteristics, constraints, assumptions and dependencies and requirements subsets are described in this section. The SRS contains all the software requirements mentioned in detail sufficient enough to enable designers to design the system to satisfy the requirements and testers to test if the system satisfies those requirements.

2. Overall Description Product Perspective The system is designed for overall managing the Medical store working including accounts. The system will be realized using configuration supporting 12 terminals with full screen support connected through local network in the Hospital. The terminals would be available at the various Departments as well as at the desk of in charges of all the major departments of the hotel. Additionally status would also be made available on the local network for almost all types of medicines. So users would be able to experience a more enhanced and simpler interface. Product Functions The Medical store management system supports following functions: a. Login facility for authorized access to the system. b. Functions by which doctors can check status of the concerned medicines. c. Functions by which D.B.A can update the database. d. User(with role of employee) will be able generate Printable bills e. User (Manager) will be able to add more users. . User Characteristics Users of the system are the Medical store staff and the doctors. Assuming that they have very less knowledge of using such type of systems, the system has well designed user interfaces. In house training will be provided to the staff for using the system. Yet the staff should at least be able to use general purpose applications of the computers and should have basic knowledge about computer Assumptions and dependencies
The users have sufficient knowledge of computers. The medical store computer should have Internet connection and Internet server capabilities.

 The users know the English language, as the user interface will be provided in English. 3. 3.1 Specific Requirements External interface requirements The following screens will be provided: Login Screen: This will be the first screen that will be displayed. It will allow user to access different screens based upon the user's role. Various fields available on this screen will be User ID: Alphanumeric of length up to 10 characters Password: Alphanumeric of length up to 8 characters Role: Will have the following values: Manager, doctor, Data Entry Operator Inventory Info Parameters Screen: This screen will be accessible only to user with role Manager. It will allow the user to enter the medicine name for which the user wants inventory information. Inventory Information Screen: This screen will be accessible only to user role Manager. It will allow the user to add modify/delete inventory information about new/existing medicines. Various fields available on these screens will be: a) Name of manufacturer a. Quantity purchased Quantity sold c. Expiry date d. Stock e. Manufacturing date Alerts Parameters Screen: This screen with alerts will be shown to user when a particular medicine falls in following categories: (i) Alarm about expiring medicines (ii) Alarm about medicines out of stock (iii)Alarm about medicines in less demand It will allow the user to edit the inventory for the medicine indicated by alarm.

3.1.1 User Interlaces

b.

Bill Parameters Screen: It will allow the user to enter the Batch Number and the medicine name for which the user wants to/print the bill. Medicines List Parameters Screen: It will allow the user to enter the Batch Number and the medicine name which are out of stock /expired/need to be changed.

3.1.2 Hardware Interfaces Screen resolution of at least 800x600-required for proper and complete viewing Of the screens. Higher resolution would not be a problem. Supports for printer-that is, approximate drivers are installed and printer is connected. It will be required for printing bills and reports 3.1.3 Software Interfaces Any window based operating system (Windows 95/98/2000/XP/NT/VISTA/7). MS Access 2000 as the DBMS-for database. Crystal Reports 8- for generating and viewing reports. 3.2 Functions Manager functions Administrator can add new medicines, syrups, equipments, syringes He can add new users for the more functionality like new employee, new department, and new store manager. He can change the prices of the medicines, their batch no, barcode. He can add/delete/modify the details of the all the products available in the store. Doctors functions He can check the various medicines with their details available in various departments. He can generate the report printable for the recommendation of any medicine required.

Employees functions He cans add/delete/modify the details of medicines available in the store. He can generate the report for the bill.

 He can give medicine information to the customer.

3.3 Software System Attributes 3.3.1 Usability The system shall allow the users to access the system from the computers that are installed with application in hospital and medical store using a user common interface. The system is user friendly and self-explanatory.

3.3.2 Reliability The system has to be very reliable due to the importance of data and the damages incorrect or incomplete data can do. The system will be developed in such a way that it may fail once in a year. Even if the system fails, the system will be recovered back up within an hour or less the system shall provide 100% access reliability. 3.3.3 Availability The system is available 100% for the user and is used 24 hrs a day and 365 days a year. The system shall be operational 24 hours a day and 7 days a week.

3.3.4 Security The application will be password protected. Users will have to enter correct username, password and role in order to access the application. 3.3.5 Maintainability The application will be designed in a maintainable manner. It will be easy to incorporate requirements in the individual modules (i.e. updation, billing, and medicines report generation and user account info).

3.3.6 Portability The application will be easily portable on any window-based system that has MSAccess 2000 or extend version installed. 3.4
3.4.1

Performance Requirements Response Time The medicine or inventory Information page should be able to be display within a minute. The information is refreshed every two minutes.

3.4.2

Manager Response The system shall take as less time as possible to provide service to the manager of the medical store. Throughput The number of transactions is directly dependent on the number of users, the users may be the administrator, employees of the store and also the doctors who use the it for checking-out medicine report and recommending new medicines Logical Database Requirements The following information will be places in a database: Medicine info : Batch number, Medicine name, category, expiry date, manufacturing date Inventory info : Quantity Purchased, quantity sold,stock,balance Billing info : Customer datails, details of medicine sold. User account info : User name, User id,Password,Role.

3.4.3

4.