Ieee-Srs Format

Software Requirements
Specification
for
Medical Store management system

Version <1.0>
Prepared by
Group Name
Jainab Khan
Zeba F Shaikh
Gulam Sadik pailwal
Azhar Shaikh
MCA III(241)
MCA III(288)
MCA III(26)
MCA III(106)
Project Guide :
Company Name :
Course:
Teaching guide :
Date:
Jainab2792@gmail.com
zebafashaikh@gmail.com
sadik.pailwal@gmail.com
skazhar7276@gmail.com
<place your industrial guides name here>

CapturaPro Technology pvt ltd
MCA
Prof. Jawed Khan
9/2/2015
SoftwareRequirementsSpecificationforMSMS
Pageii
Contents
REVISIONS................................................................................................................................................ III
1
INTRODUCTION................................................................................................................................ 1
1.1
1.2
1.3
1.4
1.5
1.6
OVERALL DESCRIPTION................................................................................................................. 3
2.1
2.2
2.3
2.4
2.5
2.6
2.7
EXTERNAL INTERFACE REQUIREMENTS.......................................................................................5

FUNCTIONAL REQUIREMENTS..................................................................................................... 6
BEHAVIOUR REQUIREMENTS...................................................................................................... 6
OTHER NON-FUNCTIONAL REQUIREMENTS................................................................................7

4.1
4.2
4.3
PRODUCT PERSPECTIVE........................................................................................................... 3
PRODUCT FUNCTIONALITY......................................................................................................... 3
USERS AND CHARACTERISTICS.................................................................................................. 3
OPERATING ENVIRONMENT........................................................................................................ 3
DESIGN AND IMPLEMENTATION CONSTRAINTS..............................................................................4
USER DOCUMENTATION............................................................................................................. 4
ASSUMPTIONS AND DEPENDENCIES............................................................................................4
SPECIFIC REQUIREMENTS............................................................................................................. 5
3.1
3.2
3.3
DOCUMENT PURPOSE............................................................................................................... 1
PRODUCT SCOPE..................................................................................................................... 1
INTENDED AUDIENCE AND DOCUMENT OVERVIEW ........................................................................1
DEFINITIONS, ACRONYMS AND ABBREVIATIONS............................................................................1
DOCUMENT CONVENTIONS........................................................................................................ 1
REFERENCES AND ACKNOWLEDGMENTS.....................................................................................2
PERFORMANCE REQUIREMENTS................................................................................................. 7
SAFETY AND SECURITY REQUIREMENTS.....................................................................................7
SOFTWARE QUALITY ATTRIBUTES..............................................................................................7
OTHER REQUIREMENTS................................................................................................................. 8
APPENDIX A DATA DICTIONARY........................................................................................................... 9

APPENDIX B - GROUP LOG................................................................................................................... 10
Pageiii
Revisions
Version
Primary Author(s)
Description of Version
1.0
Jainab Khan,
Medical store management system
Date Completed
3 months
Zeba F Shaikh
Azhar Shaikh
Sadik Pailwal
Date
Version
Description
1.0
First Draft.
People
Project Owner and
Client:
Faculty Advisor: Prof
Jawed Kh an
Project Group:
Jainab Khan
Zeba F Shaikh
Azhar Shaikh
Sadik Pailwal
Page4
1 Introduction
1.1 Purpose
The purpose of this document is to describe the Medical Store Management System(MSMS)
product .This document contains the functional and non-functional requirements of the project. It
will explain the purpose and features of the system, the interfaces of the system, what the system
will do, the constraints under which it must operate and how the system will react to external
stimuli.
The main goal of the application is to maintain the record of Purchase, Sales and Stocks details
with cash transaction maintenance. It is the complete medical store management software
designed as to ease the work load of medical shop professionals. The main feature includes
invoicing, inventory and stock control, accounting, client and vendor management.
This software helps you to track all the profits, loss, profitable clients and products of medical
store. Flexible and adaptive software suited to medical stores of any size
1.2 Product Scope

Medical store management system is software that manages all the records of the
medicines and other concerned entities like debtors and creditors
The main aim of the project is to create automated software which is purely used to serve
complete Medical Inventory Management, Control Stocks, Expiry & Claims,and Effective
Purchase Management.
Developing a medical store management system would benefit the chemist shop
management.
It is Software driven following well-organized approach the quality of services can be
enhanced considerably.
Each employees sales information is store in database.
Medical Store Software for Individual Shop or Retail Chain is designed to handle all the
needs in most efficient, effective & accurate way.
Medical Billing Software is committed to provide the best supporting system for the Retail &
Distribution Business upgrading itself from time to time according to the market needs
1.3 Intended Audience and Document Overview

The intended readers of this document are the
Developers of the site

Testers
admin
Any suggested changes on the requirements listed on this document should be included in the last
version of it so it can be a reference to developing and validating teams.
Page5
1.4 Definitions, Acronyms and Abbreviations

Acronym
Meaning
MSMS
Medical Store Management System
Admin
System administrator who is given specific permission for

managing and controlling the system
MS SQL
ASP
JSP
J2EE
IEEE
XML
HTTP
ISO 8601
Microsoft Structured Query Language

Active Server Pages
Java Server page
Java 2 Enterprise Edition
Institute of Electrical and Electronics Engineers
Extensible Mark-up Language is a text based format that
let developers describe, deliver And exchange structured
data between a range of applications to client for display
and manipulation.
Hypertext Transfer Protocol. Its a service protocol.
A standard format for representing date and time
recommended by the International Organization for
Standardization
Style sheets specify the presentation of a document written in another computer language (such
as JSP or Java An HTML ) which, in this specification, is referred to as the document language .
Throughout this documentation, the following conventions have been used :
Fonts: Times New Roman
Size 16 For Main Headings
Size 14 For Sub Headings
Size 12 For the Rest of the Document
Words in Bold are important terms, and have been formatted to grab the attention of the
reader
1.5 References and Acknowledgments
IEEE standard for writing SRS document.

I. Sommerville, Software Engineering, 8th Addison-Wesley, 2007.
Related software for reference eg mediplus etc
Page6
2 Overall Description
2.1 Product Perspective
MSMS is a replacement for the ordinary medical store management systems which depend
on excel for recording medicine and customers information. This totally self contained and works
efficiently. It provides simple database rather then complex ones for high requirements and it
provides good and easy graphical user interface new, nave as well as experienced users of the
computers .MSMS will provide an advanced medicine search mechanism and will make it easy to
maintain stock and all the inventory related task.
2.2 Product Functionality

2.2.1 Administrators
Admin should be able to insert, modify and delete products ie medicine.
can manage different branches of the store. Also manage employees of all branches.
can manage accounts. That includes balance sheet, profit & loss account and delay-inpayment modules.
can add, delete and update employees of all branches.
manage distributors for the store. Admin receives quotation from different distributors, then
places purchase order, receives invoice and manages payment to distributors.
Add and edit medicine and can get the information where it is store.
Add and edit employees and distributors information.
Can send lateness warnings to customers who have exceeded deadline date for payment.
Admin should be able to insert, modify and delete medicine
Can accept or reject a employee according to the need and salary is managed. Can get
the information (status report) of any employee who has sold how much product from
which shop.
Add and edit customer information
Can see the report according to brands,product,doctor wise to check the availability.
Page7
2.2.2 Normal Users (employees of the store)
Employees can manage customers of the store. Can add, update and delete customers.
Employees can generate bill and manage payment for the customers.
Employees can manage retailor-customers. Can give quotation to them. Receive purchase
order, generate invoice and manage payment and delivery of stock to retailor-customer.
The employees should be provided with the updated information about the products
catalog.
Employees can manage stock for the store.
Employees have the ability to search through products by brand and range related to the
product.
Employees should be able to insert, modify products
2.3 Users and Characteristics

Users of the website are the administrators and employees who maintain the website.
Employee should are have basic knowledge of computers. 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. Friendly user interface, help
and user guide must be sufficient to educate the users on how to use this product without any
problems or difficulties.
We have identified five potential classifications of users of our system:
Software Designers: These are the most obvious users. They will use the system as a
means of laying out the design of an as yet unimplemented system.
Software Developers: These are the people that take the model generated by the
designers and implement it in code. They may also use the system to identify the
design of an existing system in order to maintain it.
Quality Engineers: These users are usually responsible for ensuring that a design is
feasible and/or reliable. They will therefore also need to be looking at the output from
our system.
System Administrator: Due to the client/server/concurrent nature of the system,
someone needs to be responsible for security and maintenance of the system. This is
the System Administrators role.The Administrator of the system, project or model need
not be a member of the any of the other roles identified here.
The Client: More often than not, software is designed for a client. The client may wish
to see the design as layed out by the system and be able to see what exactly they are
buying.
2.4 Operating Environment
The MSMS is an application and shall operate in all centralized store of same branch
where application is installed.
Page8
This product is web -based and will be hosted by a web server
2.5 Design and Implementation Constraints
The information of all employees, medicine and stock must be stored in a

database that is accessible by the applications.
MS SQL Server will be used as SQL engine and database.
The medical store management system is running 24 hours a day as when ever is required.
Users may access MSML from computer that has installed application in it and as it is a
centralized software and it cannot be from any web browser..
Employees must have their correct usernames and passwords to enter into system and
do actions
2.6 User Documentation

The user guide provides the information and instructions needed to set up and use a
product. A user guide includes written and visual information (such as diagrams or screen shots) to
assist the user in completing tasks associated with the product (or service), organized along
functional or workflow lines.
2.7 Assumptions and Dependencies

The product needs the following third party products.
Microsoft SQL server to store the database.
Java to develop the Product
The success of this system depends on
Existence of an Internet service is needed.
Are administor and employees comfortable with computers and have enough conation to
work with the product?
Application interface must be friendly and easy-to-use.
The search mechanism should be simple and fast.
Calculation of stock should be appropriate and expiry information sholdould also be correct
and with proper calculations.
TIME DEPENDENCIES
Page9
The implementation of application is entirely dependent upon the time spent designing and
implementing the core features.
HARDWARE DEPENDENCIES
Some of the additional features relay on hardware components present in PCS.
EXTERNAL DEPENDENCIES
Several of the features presented in this system relay on the existence and maintained
operation of several APIs. A non-exhaustive list follows.
1. EMAIL NOTIFICATIONS:
The central server will be responsible for this feature of the application.Email will be send to
customer and distributors.
2. SMS NOTIFICATIONS:
The central server will be responsible for this feature of the application.Email will be send to
customer and distributors.
Page10
3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
The user interface for the software shall be compatible to any browser such as Internet E
xplorer, Mozilla or Netscape Navigator by which user can access to the system.
The software provides good graphical interface for the front end of the database so that
nave users can make use of the system with ease.
3.1.2 Hardware Interfaces

Since the application must run over the internet, all the hardware shall require to connect
internet will be hardware interface for the system. As for e.g. Modem, WAN LAN, Ethernet CrossCable.
Hardware requirements:
SERVER:
Web Server
Apache Tomcat Web Server
Processor
Intel Pentium IV or AMD -800 MHz
Speed
1.7 GHz
Memory Capacity
325 MB
Hard Disk Capacity
500 MB
Processor
Intel Pentium IV or AMD -800 MHz
Speed
1.7 GHz
Memory Capacity
256 MB
Hard Disk Capacity
2 GB
Monitor
15 CRT or LCD monitor
Keyboard
Normal or Multimedia
Mouse
Compatible mouse
Client:
Page11
Software Requirements
Operating System
Windows
Database
SQL
Enterprise Application
J2EE
Implementation Architecture
MVC, 3 Tier using Servlets, JSP
Scripting Languages
Java Script
Programming Language
Java
3.1.3 Communications Interfaces

The software requires the support of the following software for the database and other
requirements.
JSP(java)for the front end.

SQL server 2008 for the database.
3.2 Functional Requirements

The following list offers a brief outline and description of the main features and functionalities of
the Medical store system. The features are split into two major categories: core features and
additional features. Core features are essential to the applications operation, whereas additional
features simply add new functionalities. The latter features will only be implemented as time
permits.
CORE FUNCTIONS
1. USER REGISTRATION & WELCOME
Only appears once (the first time the application is run)
Allows the user to register with the Medical store server
Enables the user to customize his/her account settings and preferences
2. GROUP CREATION & MANAGEMENT
Streamlines the process of creating and organizing groups
Provides support for multiple groups
Allows the Admin to add group
Page12
3. INVENTORY
Stores and monitors the bill amount, the individuals involved, etc.
Includes support for multiple simultaneous bills
Efficiently distributes debt amongst the individuals responsible for the bill
4. FINANCE
Enables group members to simulate transfers of debt, payments made, etc.
Adjusts member balances accordingly
Records relevant information (amount paid, employees involved, etc.)
5. SALES & PURCHASE
Calculates the most efficient method of sorting out sales & purchase
Notifies group of sales order, sales returns, purchase order, purchase return, stocks available,
etc.
6.
GROUP HISTORY
Automatically records all transactions and bills posted to each group
Provides users with access to a detailed history of transactions
Supports sorting transactions by date, amount, distributor, etc.
7. MASTER MENU
Allows the Admin to customize his/her preferences
Enables the user to modify certain features and functionalities
Admin assign employees the access to its perspective work and according its designation.
8. HELP MENU
Displays a list of topics covering the different components of Medical Store System
Offers detailed information on each feature, menu, etc.
Can be accessed at any time via the help menu
9 . E-MAIL/SMS NOTIFICATIONS (CRM)
Extends the standard notifications service built into medical store system
Automatically delivers notifications via e-mail and/or text message
10 . REPORTS
Generates reports for customers available, sales, purchase ,stocks and so on
ADDITIONAL FUNCTIONS
Page13
11. CUSTOMERVISUALIZATION
present a visual representation of current customer balances
Allows users to navigate through financial information in a more intuitive fashion
Maintains medicine of particular brand used by specific doctors
12. PAYPAL INTEGRATION
Incorporates a mechanism for initiating real transactions
Facilitates secure, hassle-free transactions between members
Automatically updates member balances as transactions occur
13. VOUCHERS
Records and stores receipts associated with different expenses
Provides a method of checking/verifying expenses posted to a Group , Customers &
Employees
14. MEDICAL STORE SYSTEM TUTORIAL
Provides an abridged version of the Help menu for first-time users
Offers a step-by-step run through of each feature, menu, etc.
Enables any user to quickly take advantage of all Medical store system functionalities
Functionalities :
3.1.2 Admin
Prerequisite (admin signed in) for all requirements below
Requirement ID: R1.01.01
Title:insert employee
Description: This action is done to add new employee of the store.
Priority:2
Title: delete / modify employee
Description: This event is to delete an existing employee or modify its information.
Priority:2
Requirement ID:R1.01.03
Title:Validate employee account
Description:when a new employee sign up then he should wait for acceptance by Administrator
according to store policies.
Priority:1
Title:delete employee
Description:Admin can delete an employee due to some specific rules.
Priority: 2
Title: maintain balance sheet
Description:Admin can manage balance sheet.
Priority:1
Title: insert distributor
Description: This action is done to add new distributor for the store.
Priority: 2
Title: delete / modify distributor
Description: This event is to delete an existing distributor or modify its information.
Priority:2
Title: delete distributor
Description:Admin can delete an distributor due to some specific rules.
Priority: 2
Title: place a purchase order to distributor
Description:Admin can place a purchase order to distributor.
Priority:1
3.1.2 Normal User(Employee of the store)
Title: register
Description:when new user enters WLMS for the first time then he has to register
Priority:3
Title: add new stock
Description:employee can add new stock i.e product
Priority:1
Page14
Page15
Title: update or modify the stock information
Description:an employee can update or modify stock information
Priority:1
Title: edit personal information
Description:if some customer changes for example his mobile number, an employee can modify
it.
Priority: 2
Title: reset password
Description:when a member forgets his password he can claim it back via e-mail.
Priority:1
3.1.3 Common Functions
Title: login
Description: both Admin and employee must be logged in before they modify any information
Priority:1
Title: search for product i.e medicines
Description:when an employee or admin wants to search on some product by name,brand , etc.
Priority:1
3.3 Behaviour Requirements

3.3.1 Use Case View
Page16
4 Other Non-functional Requirements

4.1 Performance Requirements
The system shall accommodate high number of medicine and employees without any fault.
Responses to view information shall take no longer than 5 seconds to appear on the
screen.
4.2 Safety and Security Requirements
System use shall not cause any harm to human users.
System will use secured database.
Employees can just perform task for which permission is given but they cannot edit or
modify anything except selling of medicine.
System will have different types of users and every user has access constraints
4.3 Software Quality Attributes

The graphical user interface of Medical store system is to be designed with usability as the
first priority. The system will be presented and organized in a manner that is both visually
appealing and easy for the user to navigate. There will be feedbacks and visual cues such
as notifications to inform users of updates and pop-ups to provide users with instructions .
4.3.1 Portability
The system must have ability to transport the software on different systems. System must
run under different computing environments.
4.3.2 Reusability
The system application can be reused in new application. Codesorpartsofthisprogram
maybeusedinothersoftware
4.3.3 Availability
System indicating the extends to which a system can continue to work when a significant
component or set of components goes down.
Page17
4.3.4 Maintainability
Medical store management system maintains its data safe and secure.The entire software
will be maintain.
4..3.5 Reliability & Correctness

To ensure reliability and correctness, there will be zero tolerance for errors in the algorithm
that computes and splits expenses between group members.
4.3.6. Robustness
The System should have capacity to restart after failure.
4.3.7. Usability
The Software should be easy to use and user friendly.

Ieee-Srs Format

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ieee-Srs Format

Uploaded by

Copyright:

Available Formats

Software Requirements

Medical Store management system

<place your industrial guides name here>

EXTERNAL INTERFACE REQUIREMENTS.......................................................................................5

OTHER NON-FUNCTIONAL REQUIREMENTS................................................................................7

APPENDIX A DATA DICTIONARY........................................................................................................... 9

Medical store management system

1.2 Product Scope

1.3 Intended Audience and Document Overview

Developers of the site

1.4 Definitions, Acronyms and Abbreviations

Medical Store Management System

System administrator who is given specific permission for

Microsoft Structured Query Language

Fonts: Times New Roman

Size 16 For Main Headings

Size 14 For Sub Headings

Size 12 For the Rest of the Document

1.5 References and Acknowledgments

IEEE standard for writing SRS document.

2.2 Product Functionality

Admin should be able to insert, modify and delete products ie medicine.

can add, delete and update employees of all branches.

Add and edit employees and distributors information.

Admin should be able to insert, modify and delete medicine

Add and edit customer information

2.2.2 Normal Users (employees of the store)

Employees can manage stock for the store.

2.3 Users and Characteristics

2.4 Operating Environment

This product is web -based and will be hosted by a web server

2.5 Design and Implementation Constraints

The information of all employees, medicine and stock must be stored in a

MS SQL Server will be used as SQL engine and database.

2.6 User Documentation

2.7 Assumptions and Dependencies

Microsoft SQL server to store the database.

Java to develop the Product

The success of this system depends on

Existence of an Internet service is needed.

Application interface must be friendly and easy-to-use.

The search mechanism should be simple and fast.

3.1.2 Hardware Interfaces

Apache Tomcat Web Server

Intel Pentium IV or AMD -800 MHz

Hard Disk Capacity

Intel Pentium IV or AMD -800 MHz

Hard Disk Capacity

15 CRT or LCD monitor

MVC, 3 Tier using Servlets, JSP

3.1.3 Communications Interfaces

JSP(java)for the front end.

3.2 Functional Requirements

3.3 Behaviour Requirements

4 Other Non-functional Requirements

4.2 Safety and Security Requirements

System use shall not cause any harm to human users.

System will use secured database.

4.3 Software Quality Attributes

4..3.5 Reliability & Correctness

You might also like