Software Requirements Specification

for

Medical Shop Automated System

Version 1.0

Prepared by

Yash Oswal-59,

Ayush Kumath-50,

Viraj Modi-54

SAKEC

14 January, 2019
Software Requirements Specification for Medical Shop Automated System(MSAS)

Table of Contents

Table of Contents Error! Bookmark not defined.

1. Introduction Error! Bookmark not defined.
1.1 Purpose Error! Bookmark not defined.
1.2 Document Conventions Error! Bookmark not defined.
1.3 Product Scope Error! Bookmark not defined.
2. Overall Description Error! Bookmark not defined.
2.1 Product Perspective Error! Bookmark not defined.
2.2 Product Functions Error! Bookmark not defined.
2.3 User Classes and Characteristics Error! Bookmark not defined.
2.4 Operating Environment Error! Bookmark not defined.
2.5 Design and Implementation Constraints Error! Bookmark not defined.
3. External Interface Requirements Error! Bookmark not defined.
3.1 User Interfaces 4
3.2 Hardware Interfaces Error! Bookmark not defined.
3.3 Communications Interfaces Error! Bookmark not defined.
4. System Features Error! Bookmark not defined.
4.1 Stock Details Error! Bookmark not defined.
4.2 Receipt Generation Error! Bookmark not defined.
5. Other Nonfunctional Requirements 5
5.1 Performance Requirements 6
5.2 Security Requirements Error! Bookmark not defined.
5.3 Software Quality Attributes Error! Bookmark not defined.
5.4 Business Rules Error! Bookmark not defined.
6. Other Requirements 6
Software Requirements Specification for Medical Shop Automated System(MSAS)

1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of a Medical Shop Automated
System for the PCs/Desktop. It explains the purpose and features of the application itself, the
interface through which a user can access the inventory, the administrator that can change the
user’s account information and user accounts, and the constraints that must be satisfied for security
purposes. This document is intended for both the customer and the project development team.

1.2 Document Conventions

IEEE Document format was followed while creating this document. Standard font style used is
“Times New Roman”, font size is 12.

1.3 Product Scope

This software provides its users with the ease to handle its medical inventory. The records in the
application will contain manufacturing and expiry date of the medicines. With the help of this
software owner’s time will be saved and on a shop owner’s command the list of medicines to be
ordered will be generated. Minimum amount of stock will be specified.
Software Requirements Specification for Medical Shop Automated System(MSAS)

2. Overall Description

2.1 Product Perspective

The purpose of this section is to present a detailed description of the product’s perspective giving
information about the context and interface constraints. The product functions section outlines
major functionality this product will perform. The user characteristics section explains the
expectations MSAS has about the user. The constraints section contains detailed descriptions of
constraints and safety critical properties pertaining to MSAS.

2.2 Product Functions

● Login for authentic users

● Sales Report
● Inventory
● A form where a medicine’s details will be shown(e.g. Name, Price, Company,
Manufacturing date, Expiry date)
● A form to search for a specific medicine and obtain its details.

2.3 User Classes and Characteristics

USER: The user is expected to be familiar with the basic use of a PC/Desktop. To have a
basic knowledge about how to open the software. Must be able to navigate through forms of the
product.
OWNER: Owner must be able to understand about security privilege level when explained.

2.4 Operating Environment

This product(MSAS) will be supported only on PC/Desktop running Windows 7 and above. A
secure backup should be done everyday in case of a system failure. Java JDK(Java Development
Kit) SE 8 minimum must also be there installed on system.

2.5 Design and Implementation Constraints

If any alterations done to the product in any form by its users or unauthorized access the product
development team shall not be held responsible for any loss of data. If any issues in the product
then owner will contact the developer only. Calling a technician and then if loss of data occurs
then product development team shall not be held responsible for the same.

2.6 Assumptions and Dependencies

Software Requirements Specification for Medical Shop Automated System(MSAS)

The assumptions and dependencies section summarizes any assumptions or dependencies the
application has about the hardware, software, environment and user interactions associated with
it. The requirements section goes over the functionality customers want.

3. External Interface Requirements

3.1 User Interfaces

● An interface for user(owner/employee) to generate a receipt.

● An interface to show the inventory and search for a specific medicine.
● An interface for login of owner and employees.
● An interface which will show sales report.

3.2 Hardware Interfaces

Windows OS 7 and above will be required for proper functioning of product. Java JDK SE
8 or above to run this program.

3.3 Communications Interfaces

This product must be installed only on one system and if installed on more than one will
cause inconsistent data and redundancy.
Software Requirements Specification for Medical Shop Automated System(MSAS)

4.System Features

The following system will provide the shop owner and its employee to fasten the searching
of medicine at their respective shop .Moreover it will also provide facility to keep track about the
medicine records.The system will provide the shop employees the best approach to delete the sold
items and update the records accordingly. It will also enable the show owner to generate the list of
expired medicines.

4.1 STOCK DETAILS:

4.1.1 Description and Priority

The above mentioned feature comes under High priority.
Benefit of this feature will reduce paper work and will enable digitally managing of stock.

4.1.2 Stimulus/Response Sequences

Employee1:Will insert the medicine name in the search box.
Response: If medicine is available then its details will be shown or else the employee will
get a pop-up about the in-availability of medicine.

4.1.3 Functional Requirements

REQ-1: The medicine detailed description will be feeded previously.
REQ-2: The stock will be updated whenever new stock is bought or stock are sold.

4.2 RECEIPT GENERATION:

4.2.1 Description and Priority

The above mentioned feature comes under Medium priority.
Benefit of this feature will reduce paper work and will enable digitally managing of stock.

4.2.2 Stimulus/Response Sequences

Employee1:Will insert the medicine details in the stock details description box.
Response: Will generate the digital receipt about the medicine sold to the customer.
Software Requirements Specification for Medical Shop Automated System(MSAS)

5.Other Nonfunctional Requirements

5.1 Performance Requirements

The system GUI will be made simple and efficient to the owners and its employee.
The system will be updated whenever needed and regular system checkups will be performed at
regular intervals.

5.2 Security Requirements

The owner Log-in credentials will be required to access the system of respective shop.

5.3 Software Quality Attributes

The software will be flexible, interoperable, easily maintainable, portable, reliable,

reusable, robust, testable.

5.4 Business Rules:

OWNER: Will Log-in and turn the system on and can even monitor the system.

Employee: Will ADD,DELETE,UPDATE stock details and can even generate Bills,list of expired
medicine.
Software Requirements Specification for Medical Shop Automated System(MSAS)

6.Other Requirements

DATABASE REQUIREMENT: This system will require a huge database of the stock details.

LEGAL REQUIREMENT: The Software must be licensed to the licensed shop owner only.