0% found this document useful (0 votes)
42 views

Report Format For BE-CS, IT Students

The document provides requirements for a pharmacy management system desktop application. It describes the purpose as ensuring effective data saving and manipulation to minimize time and resources for searching medicine data. It also allows generating reports on dispensed drugs. The system has functions for administrators to provide access and for employees to enter medicine details. It stores login details, customer information, and medicine reserve stock details.

Uploaded by

mahesh kale
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views

Report Format For BE-CS, IT Students

The document provides requirements for a pharmacy management system desktop application. It describes the purpose as ensuring effective data saving and manipulation to minimize time and resources for searching medicine data. It also allows generating reports on dispensed drugs. The system has functions for administrators to provide access and for employees to enter medicine details. It stores login details, customer information, and medicine reserve stock details.

Uploaded by

mahesh kale
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

1

Software Requirements
Specification
for

Pharmacy
Management
System
(Desktop Application)
Version 1.0

Prepared By:
1.Mahesh Kale [24]
2.Shyam Patel [37]
3.Sourabh Patil[38]
Submitted to :- Prof. R. M. Samant.

[- 1 -]
2

Table of Contents
Table of Contents ...........................................................................................................................1
1. Introduction ..............................................................................................................................3
1.1 Purpose............................................................................................................................................. 3
1.2 Document Conventions.................................................................................................................... 3
1.3 Intended Audience and Reading Suggestions .................................................................................. 4
1.4 Product Scope .................................................................................................................................. 4
1.5 References........................................................................................................................................ 4
2. Overall Description .............................................................................................................................. 4
2.1 Product Perspective.......................................................................................................................... 4
2.2 Product Functions ............................................................................................................................ 5
2.3 Operating Environment.................................................................................................................... 6
2.4 Design and Implementation Constraints .......................................................................................... 6
2.5 User Documentation ........................................................................................................................ 6
2.6 Assumptions and Dependencies ...................................................................................................... 6
3. External Interface Requirements ...........................................................................................7
3.1 User Interfaces ................................................................................................................................. 7
3.2 Hardware Interfaces ......................................................................................................................... 8
3.3 Software Interfaces .......................................................................................................................... 8
3.4 Communications Interfaces ............................................................................................................. 8
4. System Features .......................................................................................................................8
4.1 Safety and security requirements ..................................................................................................... 8

[- 2 -]
3

1.Introduction

Pharmacy management system is robust, integrated technology. Pharmacy


management system deals with the maintenance of drugs and consumables in the
pharmacy unit. The set-up of this pharmacy management system will ensure
availability of sufficient quantity of drugs and consumable materials in pharmacy.
This will enhance the efficiency of clinical work and ease patient’s convenience.

The Pharmacy management system is based on computer technology that gives


service for users, managed by the pharmacist who give implementation of function
relatively in effective times as well as will design for removing time wasting, saving
resources, easy data access of the medicine, security on data input and data access by
removing almost manual based system.

1.1 Purpose :
The pharmacy management system is built for the sake of ensuring effective and
clear data saving and manipulating as well as neat work on the pharmacy medical
products. This refers the pharmacy management system project highly minimize time
and resource by which, searching the medicine data you can get the data in quickest
time. Some of the resources minimized include paper, manpower and related things.
The other thing is for storing data’s in secure way.
A summarized list of drugs dispensed to patient can be viewed for monitoring
purposes. Also PMS will be able to generate report on the list of drugs dispensed in
the polyclinic for a given time period. And there is a message alert for the user if the
stock holding quantity reaches a low level. Thus, the pharmacist will need to
replenish the drugs.

1.2 Document Conventions :


This document is prepared using the IEEE recommended practice for Software
Requirement Specification.

[- 3 -]
4

1.3 Intended Audience and Reading


Suggestions :
The different types of reader that this document is intended for are developers,
project managers, marketing staff, users, testers, and documentation writers. The rest
of this SRS contains Overall Description, External Interface Requirements, System
Features, Non Functional Requirements and Other Requirements. Suggested
sequence for reading the document -begin with the overview sections and proceed
through the sections that are most pertinent to each reader type.

1.4 ProductScope :
The purpose of the Pharmacy management system is to ease drugs management and to
create a convenient and easy-to-use application for employees and staff.. We will have a
database server supporting hundreds of major medicines around the world as well as
thousands of drugs by various companies. Above all, we hope to provide a comfortable
user experience along with the best pricing available.

1.5 References :
This web application has been prepared on the basis of discussion with Team members and
also
taken information from following website – www.google.com , www.ics.com and the
IEEE
.website.

2.Overall Description
2.1 Product Perspective :
A pharmacy management system stores the following information.

Login details:
It includes the admistrative login such as user name and passwords.
Customer description:

It includes customer code, name, address and phone number. This information may
be used for keeping the records of the customer for any emergency or for any other
kind of information.
[- 4 -]
5

Reserve stock:
It includes medicine details, code number, batch number, date of expiry.

2.2 Product Functions :


The functions are divided according to the user types such as:-
Administrator:-
The function of the administrator is give access to employees .
Employee:-
The function of the employee is to provide medicine details .
This app will only allow the registered employee to enter into the stock details. The
various stages in the app are as follows:-

 Login

 Check Availability

 Modify

 Result

1. Login:
This window offers the user two choices for logging into the system according to the preset
privileges - employee login and Administrator login.
The employee login will take the user to the user profile.
The Administrator Login will take the user to the administrator profile.
2. Check Availability:
In this window authorized person check or find the details of medicines as well
as check stock availability.
3. Modify:
This window can only be accessed by the administrator or authorized person . It allows the
administrator to add and edit drugs .
[- 5 -]
6

4. Result:
This window displays the result. This data will be saved and displayed in the window . If
the data is found then it shows on window.

2.3 Operating Environment :


Operating environment for the airline management system is as listed below.
 client/server system
 Operating system: Windows.
 database: sql + database
 platform: vb.net/Java/PHP

2.4 Design and ImplementationConstraints :


1. SQL commands for above queries/applications
2. Assuming these are global queries. Explain how various functions will be
combined to do so.
3.Implement the database at least using a centralized database management
system.

2.5 User Documentation :


With this project,There will be a project report. So then by using that report user will get
understand the system then they can easily access.

2.6 Assumptions and Dependencies :


1. A request for purchasing/cancellation of a medicine from an store , giving related
medicine details in case required medicine is not available .
2. Calculation of strong medicines (voveran ) and without doctors permission
medicines will not be provided.

[- 6 -]
7

3.External Interface Requirements :

3.1 User Interfaces :

• Registration Screen:
Various fields available on this screen will be:
-Login Name
-Email Id
-Password

• Login Screen:
Fields available on this screen are:
-Login Name
-Password

• Medicine Details Screen:


Various Fields are:
medicineName
-No. Of medicines
-stock

. Result Displaying Screen:


Various Fields are:
-medicine name
[- 7 -]
8

-medicine expiry date

3.2 Hardware Interfaces :


1. Windows.
2. A browser which supports CGI, HTML &Javascript.

3.3 Software Interfaces :


Any windows based operating system.
-MySql Server Database
-Apache tomcat server

4.System Features
Some Performance requirements identified is listed below:
The database shall be able to accommodate a minimum of 1,000 records of
Users.
The software shall support use of multiple users at a time.
There are no other specific performance requirements that will affect
development

4.1 Safety and Security Requirements :


The database may get crashed at any certain time due to virus or operating
system failure. Therefore, it is required to take the database backup.

[- 8 -]

You might also like