Software Requirement

Specification [SRS]
For
Medicine Shop Software (MSS)
By
Apurv Anand & Karthik Rao &
Shreyas M. Jain
20-08-2016
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions & Abbreviations
1.4 Overview of the Document
1.5 References
2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 Operating Environment
2.4 User Characteristics
2.5 Design and Implementation Constraints
2.6 Assumptions and Dependencies
3. External Interfaces Requirements
3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces
4. Functional Requirements
5. Non-Functional Requirements
1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of the Medicine Shop
Software. It will explain the features and purpose of the system, the interfaces of the system,
what the system will do, the constraints under which it must operate and how the system is
supposed to work under various conditions. This document is intended for both the
stakeholders and the developers of the system.

1.2 Scope

This software system will be an Automation System for a Medicine Shop. This system
will be designed to maximize the Medical Shop’s efficiency by providing tools to assist in
automating the various processes performed frequently in a Medical Shop, which would
otherwise have to be performed manually.
More specifically, this system is designed to display the average number of medicines
sales for one week for each part. At the end of day, generate items to be ordered, print out
medicine description, quantity required and address of the vendor supplying the medicine.

1.3 Definitions and Abbreviations

1.3.2 Acronyms and Abbreviations Meaning

Acronym
MS SQL Microsoft Structured Query Language
ASP Active Server Pages
ISBN International Standard Book Number
IEEE Institute of Electrical and Electronics
Engineers
1.4 Overview of the Document

The next chapter, the Overall Description section, of this document gives an overview of the
functionality of the product. It describes the informal requirements and is used to establish a
context for the technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written primarily for
the developers and describes in technical terms the details of the functionality of the product.
Both sections of the document describe the same software product in its entirety, but are
intended for different audiences and this use different language.

1.5 References

NA
2. Overall Description

2.1 Product Perspective

Medicine Shop Software is a replacement for the ordinary medicine management

systems which depend on paper work for recording medicines and vendors information.

2.2 Product Functions

2.2.1 Administrators

 Admin should be able to insert, modify and delete medicine details.

 Can accept or reject a new user according to the medicine shop policy or payment
methods.
 Can get the information (status report) of any medicine that is sold.
 Add and edit medicine categories and arrange medicines by categories.
 Add and edit vendors information.
 Alert when a particular medicine has passed its expiry date.
2.2.2 Staff & Employees
 The employees should be provided with the updated information about the medicine
details.
 Employees are given a access to check their account’s information and change it.
 Members have the ability to search through medicine by name, vendors.

2.3 Operating Environment

The Medicine Shop Software is a system that should operate only through the
particular medicine shops and its divisions.

2.4 User Characteristics

Users of this Medicine Shop Software are owner, employees, staffs and the
administrators who maintain the system. Employees and staffs are assumed to have basic
knowledge of computers and Internet browsing. Administrators of the system should have more
knowledge of internal modules of the system and are able to rectify small problems that may
arise due to disk crashes, power failures and other catastrophes.

2.5 Design and Implementation Constraints

 The information of all employees, staffs, medicines and vendor information must be
stored in a database that is accessible by the website.
 MS SQL Server will be used as SQL engine and database.
 The Medicine Shop Software is running 24 hours a day.
 The authenticated employees and staff may access the system only through local intranet
available in the particular medicine shop and its extensions.
 Employees and staff must have their correct usernames and passwords to enter into their
accounts and do actions.

2.6 Assumptions and Dependencies

 The product needs the following third party products.

 Microsoft SQL server to store the database.
 ASP.net to develop the Product.
3. External Interfaces Requirements

3.1 User Interfaces

Login Interface:

In case the employees are not registered yet, they can enter the details and register.
Which asks the employees to type their username and password. If the employees entered either
his username or password incorrectly then an error message occurs. The owner has administrator
access to the system.

Search:

The employees & staff can enter the medicine he is looking for, then he can search for
the required medicines by entering the medicine name.

Categories view:

Categories view shows the medicine categories view with ability to employees to
add/edit or delete category from the list.

Admin’s Control Panel

This control panel will allow admin to add, confirm, or remove employees & staff; add,
edit, or remove a medicine and the vendors. And manage the database through higher admin
access.

3.2 Hardware Interfaces

Only the recommended configuration (basic requirements of a computer system) no other

specific hardware is required to run the software.

3.3 Software Interfaces

 The system to load on local intranet of the specific medical shop.

 Operating System
4. Functional Requirements

R1 Procure_Medicine
Inputs Med_Name, Quantity, Expiry_Date, Vender_Name, Vender_Address, Code_no
Process Show Details
Output Perform Inventory

R2 Order_Items (Threshold)
Inputs Med_Name, Quantity
Process Show Details
Output Update Information

R3 Order_Item (Expired)
Inputs Med_name, Quantity, Expiry_Date, Vender_Name, Vender_Address, Code_No
Process Show Details
Output Discard item

R4 Generate_cash_receipt
Inputs Med_Name, Quantity, Vender_Name, Vender_Address, Price, Code_No
Process Calculate Amount
Output Cash Receipt

R5 Generate_Total_Revenue
Inputs Med_Name, Quantity, Vender_Name, Vender_Address, Price, Code_No
Process Calculate Revenue
Output Generate_Total_Revenue
5. Other Nonfunctional Requirements

5.1 Performance Requirements

The Medical Shop automation software should be equipped to handle concurrent orders. The
availability data of the medicines and its vendors should be consistent over both the local and
web interface. The system must be interactive and the delays involved must be less .So in every
action-response of the system, there are no immediate delays.

5.2 Availability Requirements

The software should be accessible only to authorized personnel over the intranet.

5.3 Safety Requirements

The admin controls should be well hidden and inaccessible over the web interface. Information
transmission should be securely transmitted to server without any changes in information

5.4 Security Attributes

The main security concern is data in the database, any tampering could lead to improper data
in accord with the medicines present which could pose a serious problem hence proper login
mechanism should be used to avoid hacking.
 MSS

Med_Name, Inventory
Expiry_Date, Quantity

Owner
 Med_Inventory,
Med_Inventory Vendor_Inventory
DFD (Level 1)
Med_Name,
quantity, Order_Med
Procure_Med Expiry_Date (Threshold)
Med_Name,
0.1
quantity, 0.2
Expiry_date Code_No,
Vendor_Details

Inventory Vendor_Details

Med_Inventory,
Vendor_Inventory

Cash
Order_Med Reciept
Generate_CashRe
(Expired) ceipt

0.3 0.4

Med_Name, Quantity, Code_No, Quantity, Price

Expiry_Date

Graph, Revenue

Generate_Revenue

0.5
No of Orders,
Quantity
 DFD (Level 2) PROCURE_MED
Quantity, med_name

Med_Name

Med_name_De
tails Quantity_details

0.1.1 0.1.2

Med_Name_Inventory Quantity_inventory

Expiry_date

Expiry_date_details
Expiry_date
0.1.3

Expiry_inventory
 ORDER_MED (THRESHOLD)

Quantity, med_name
Med_name, code_no

Med_name_de Quantity_Details
tails
0.2.2
0.2.1

Med_name_quantity Quantity_inventory
Vendor_name,
vendor_address
Expiry_date

Expiry_details Expiry_date Vendor_details

0.2.3 0.2.4

Expiry_inventory Vendor_inventory
 ORDER_MED (EXPIRED)

Med_name, Quantity, med_name

code_no

Med_name_deta Quantity_details
ils
0.3.2
0.3.1

Med_inventory Quantity_inventory

Vendor_inventory

Expired_details Vendor_details

0.3.3 0.3.4

Vendor_name,
vendor_address
Expired_inventory
 GENERATE_CASH_RECEIPT

Quantity, med_name
Med_name, code_no

Med_name_det
Quantity_details
ails
0.4.2
0.4.1

Med_inventory Quantity_inventory

Expiry_inventory

Expiry_date Cost

Expiry_details Generate_cash
_receipt
0.4.3
0.4.4

Cash_receipt
Cash_receipt_inventory
 GENERATE_REVENUE

Med_name, code_no Quantity, med_name

Med_name_d
etails Quantity_details

0.5.1 0.5.2

Med_inventory Quantity_inventory

Expiry_date Vendor_name, vendor_address

Expiry_details Vendor_details
0.5.3 0.5.4

Expiry_inventory Vendor_inventory

cost

Cash_receipt Generate_reven
ue
0.5.5
0.5.6

Cash_receipt_inventory
Generate_revenue
DATA DICTIONARY
Med_Name = Name + Composition + Expiry_Date
Name: String
Composition: String
Expiry_Date = Date
Date = Day + Month + Year
Day: Integer
Month: Integer
Year: Integer

Code_No = Code_No
Code_No: Integer

Price = Price
Price: Integer

Vendor_Details = Vendor_Name + Vendor_Address

Vendor_Name: String
Vendor_Address: String

Inventory = Med_Name + Code_No + Expiry_Date + Vendor_Name + Vendor_Address + Price

ID: UC-01
TITLE: Procure_Medicine
DESCRIPTION: Management of Medicine shop contacts vendor for the bulk of medicines
requires, viewing it, process it.
PRIMARY ACTOR: Manager
PRECONDITIONS: Manager must contact the vendor
POSTCONDITIONS: The bulk of medicines are procured by Manager
MAIN: 1. Manager contacts Vendor
SUCCESS SCENARIO: 2. Vendor show the details of all the medicines available
3. Manager buys and transfers the medicines to the medical shop
4. Manager buys and transfers the medicine to medical shop
EXTENSION: 1a. Vendor not available
1a1. Manager has to contact another Vendor
2a. Not all medicines required by the medicine shop are available
2a1. Medicines above their expiry date, which have to be discarded
4a. Medicine cost too high
4a1. Problems in transferring of medicine
FREQUENCY OF USE: Once a week, if bulk of the medicines reach threshold
ID: UC-02
TITLE: Order_Medicine (threshold)
DESCRIPTION: Management of Medicine shop contacts Vendor for the bulk of medicines
required, viewing it, process it.
PRIMARY ACTOR: Manager
PRECONDITIONS: Manager must contact the vendor
POSTCONDITIONS: The bulk of medicines are ordered by Manager
MAIN: 1. Manager contacts Vendor
SUCCESS SCENARIO: 2. Vendor show the details of all the medicines available
3. Manager selects the medicines required for the medical shop
4. Vendor transfers the medicine to medical shop
EXTENSION: 1a. Vendor not available
1a1. Manager has to contact another Vendor
2a. Not all medicines required by the medicine shop are available
2a1. Medicines above their expiry date, which have to be discarded
4a. Medicine cost too high
4a1. Problems in transferring of medicine, accident issues, transportation
problems
FREQUENCY OF USE: Once a week, if bulk of the medicines reach threshold
ID: UC-03
TITLE: Order_Medicine (expired)
DESCRIPTION: Management of Medicine shop contacts vendor for the bulk of medicines
required, viewing it, process it.
PRIMARY ACTOR: Manager
PRECONDITIONS: Manager must contact the vendor
POSTCONDITIONS: The bulk of medicines are procured by Manager
MAIN: 1. Manager contacts Vendor
SUCCESS SCENARIO: 2. Vendor show the details of all the medicines available
3. Manager selects the medicines required for the medical shop
4. Vendor transfers the medicine to medical shop
5. Manager checks for the validity, expiry date of medicine
EXTENSION: 1a. Vendor not available
1a1. Manager has to contact another Vendor
2a. Not all medicines required by the medicine shop are available
2a1. Medicines above their expiry date, which have to be discarded
4a. Medicine cost too high
4a1. Problems in transferring of medicine
5a. Return the Medicine, which are par expiry date to the vendor
FREQUENCY OF USE: Whenever the bulk of medicines are bought from vendor
ID: UC-04
TITLE: Generate_cash_receipt
DESCRIPTION: Clerk of Medicine shop should generate the receipt for the medicines ordered by
the customer.
PRIMARY ACTOR: Clerk, Customer
PRECONDITIONS: Customer must buy medicine from the shop
POSTCONDITIONS: Customer should pay cash for medicine bought
MAIN: 1. Customer contacts Clerk
SUCCESS SCENARIO: 2. Clerk generates cash receipt
EXTENSION: 2a. Amount not printed properly
2a1. Amount more than actual price

FREQUENCY OF USE: everyday, whenever medicine purchased by customer

ID: UC-05
TITLE: Generate_revenue
DESCRIPTION: Management of Medicine shop contacts Owner for generating revenue to buy
bulk of medicine from vendors
PRIMARY ACTOR: Manager, Owner
PRECONDITIONS: Manager must contact the Owner
POSTCONDITIONS: The bulk of medicines required for the Medical shop
MAIN: 1. Manager contacts Owner
SUCCESS SCENARIO: 2. Owner generates revenue
3. Buy Medicine from the Vendor
EXTENSION: 1a. Owner not available
1a1. Manager has to contact Owner again
2a. Owner might generate revenue less than required
3a. Vendor not available
3a1. Contact another Vendor
FREQUENCY OF USE: Once in a month, if revenue of Medical shop reaches threshold
 ACTIVITY DIAGRAM
START VENDOR CONTACT MEDICINE (THRESHOLD) MEDICINE (EXPIRY)
CUSTOMER ORDER REVENUE
CONTACT
VENDOR

CHECK CHECK TAKE

ORDER MEDICINE MEDICINE CUSTOMER
BULK BULK EXPIRY ORDER
MEDICINE
QUANTITY EXPIRED
BELOW
EXPIRY GENERATE
NO REVENUE
CALCULATE COST
YES YES
WAIT
DISCARD FIXED
DISCARD END
TIME
GENERATE RECIEPT
NO
NO
PROCURE_MEDICINE
WAIT
FIXED
YES TIME
DECISION TREE

Input: Med_Name, Quantity, Expiry_Date, Vender_Na

Y (Proc_med)
Process: Show Details

Output: Perform Inventory

Input: Med_Name, Quantity

Y (Order_Med (Threshold))
Process: Show Details

Output: Update Information

Input: Med_name, Quantity, Expiry_Date, Vender_Na

Y (Order_Med (Expiry)) Process: Show Details
Valid Selection
Output: Discard item

Y (Generate_cash) Input: Med_Name, Quantity, Vender_Name, Vender_

Process: Calculate Amount

Output: Generate_Cash_Receipt

Y (Generate_revenue) Input: Med_Name, Quantity, Vender_Name, Vender_

Process: Calculate Revenue

Output: Generate_Total_Revenue

N (Display error message)

Display Error Messa
 DECISION TABLE
Valid Procure Order_Med(T) Order_Med(E) Generate_Cash_ Generate_Revenue
Selection _Med Receipt
Valid N Y Y Y Y Y
Selection
Procure_Med - Y N N N N
Order_Med(T - N Y N N N
)
Order_Med(E - N N Y N N
)
Generate_Cas - N N N Y N
h_Receipt
Generate_Rev - N N N N Y
enue
ACTION
Display Error X
Message
Med_Name X X X X X
Expiry_Date X X
Quantity X X X X X
Price X X
Code No X X X X
Vendor_Nam X X X X
e
Vendor_Addr X X X X
ess
Sequence Collaboration Diagram
1. Procure Medicine
2. Order medicine
3. Generate Cash Receipt
4. Generate Cash Revenue
COMPLETE CLASS DIAGRAM