08/11/1019

Project Title:
Online Pharmaceutical Store
Group Members:
Usama Akbar BSEM-F17-079
Izhar Ahmad BSEM-F17-113
Sana Shaheen BSEM-F17-125
Section:
BSSE-5B
Subject:
Software Requirement Engineering
Submitted to:
Sir Saleem Zubair
 Software Requirements
Specification
for

<Online Pharmaceutical Store >

Version 1.0 approved

Prepared by <author>

<organization>

<date created>

Copyright © 1999 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for <Project> Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii
Revision History ...............................................................................................................................
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions .................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 2
1.4 Product Scope .................................................................................................................................. 2
2. Overall Description ..................................................................................................................2
2.1 Product Perspective.......................................................................................................................... 2
2.2 Product Functions ............................................................................................................................ 3
2.3 User Classes and Characteristics ..................................................................................................... 3
2.4 Operating Environment .................................................................................................................... 4
2.5 Design and Implementation Constraints .......................................................................................... 4
2.6 User Documentation ........................................................................................................................ 4
3. External Interface Requirements ...........................................................................................4
3.1 User Interfaces ................................................................................................................................. 4
3.2 Hardware Interfaces ......................................................................................................................... 4
3.3 Software Interfaces .......................................................................................................................... 5
3.4 Communications Interfaces ............................................................................................................. 5
4. System Features .......................................................................................................................6
4.1 System Feature 1 .............................................................................................................................. 6
4.2 System Feature 2 (and so on) ........................................................................................................... 6
5. Other Nonfunctional Requirements .......................................................................................6
5.1 Performance Requirements .............................................................................................................. 7
5.2 Safety Requirements ........................................................................................................................ 7
5.3 Security Requirements ..................................................................................................................... 7
5.4 Software Quality Attributes ............................................................................................................. 8
5.5 Business Rules ................................................................................................................................. 8
Software Requirements Specification for <Project> Page 1

1. Introduction
1.1 Purpose
The purpose of online medical store is to provide online services to our customers with
the best prices for their prescription medications. Our convenience and services will
exceed the expectations of our customers.

1.2 Document Conventions

The following are the list of conventions that’s used in this document and project
• Administrator
A login Id representing the user with user administrator privileges to
software.
• Client
Intend user of software
• Sql
SQL used to perform CRUD operations on database.
• Oracle
A server used to store data in organized form
• Java
Coding Language
• DFD
Show data flow between entities.
• User interface
Something through which user communicate with system.
Software Requirements Specification for <Project> Page 2

1.3 Intended Audience and Reading Suggestions

The intended audience of this document is all major stakeholders which include the
development team, the project owner, the project customer, the senior project advisor,
project financer and anyone evaluating the project

1.4 Product Scope

Our convenient online portal helps save you time. We offer one-stop shopping for
brand, generic, plasma and biologic, and specialty medications. Plus, we provide
targeted news and updates about products, programs and services that matter most to
your pharmacy.
All your pharmaceutical needs are met at your doorstep by our trained riders, in safe
and hygienic conditions. We maintain recommended temperature level and packaging
material to prevent any damage while in storage or transit.
Your order will be delivered to you in a sealed package, which you may accept only if
the seal is intact. Before accepting your medicines, you have full authority to return the
order if the seal is tampered. To ensure authenticity of medicines provided by our
company, we will not be able to return/exchange medicines once sold and accepted by
you. This is for your safety and to maintain quality standards.

2. Overall Description
2.1 Product Perspective

The product is supposed to be an open source, under the GNU general Public License.
It is an app based system. It provides simple mechanism for users.

Cross-platform system:
When the users select any type of medicine or any need thing. Our operating
support gives interaction and gives more powerful operating system.
User account:
The system allows the user to create their accounts in our app and provide features of
updating and viewing profiles. And they use our app for own benefit.
Number of users being supported by the system:
Software Requirements Specification for <Project> Page 3

Though the number is precisely not mentioned but the system is able to support a
large number of online users at a time.
Search:
search is simply local search engine based on key words.
Discussion Forum:
Provides users with a platform to discuss and help each other with their problems.
FAQs section:
Frequently asked section contain answer of problem which tablet user frequently
faced.

2.2 Product Functions

• Up-to-date pharmaceutical product and pricing information

• Simplified and intuitive drug ordering and return functionality
• Pharmacy inventory management
• Drug purchase history reporting
• Payment solutions
• Interoperability with other pharmacy or hospital IS systems
• All you need to do is to log on to website
• search for the medicine, click on buy now
• If it requires prescription - you can upload a copy of your prescription from your
mobile, tablet or desktop and then check out. You can also send your prescription
on WhatsApp or email us.

User Classes and Characteristics

• User of include customers and staff

• Customers can be member or visitor who are accessing this system.
• Staff who act as administrator and controlling overall system.
• User should id literate and should know the computer.
• Cashier show know the data entry and typing.
• Admin should have knowledge of internet and browsing.
Software Requirements Specification for <Project> Page 4

Operating Environment

• This system will be run on all operating systems and also compatible for
internet explorer and google chrome.
• The only requirement for using of this system is you should have a machine.

2.3 Design and Implementation Constraints

This project is developed using java. On the backhand for database we are using SQL
server. The product is Accomplished with the login facility for user.

2.4 User Documentation

This project will include a user manual. The user manual includes complete overview
of the product, configuration of the tool used (SQL server or other), technical details
backup procedures and contact information which will include email address and
phone no

3. External Interface Requirements

3.1 User Interfaces
• Product Details
• Search and Filter
• Customer Reviews
• New Promotions
• Simple Checkout
• Visible Contact Info
• Return/Exchange Info
• Security Symbols

3.2 Hardware Interfaces

• Database System:
Software Requirements Specification for <Project> Page 5

It is necessary to program the website to connect securely to

the database so that all the orders are processed correctly and your business runs
smoothly. Technologies like PHP and MySQL are the communication route
between the website and the DBMS (database management system)
• Networking:
TCP (transfer control protocol) and IP (internet protocol) defines
as how computers should connect with each other through the internet and how
they share information. Common TCP/IP protocols are HTTPS, HTTP, and FTP.
We use these protocols to access the website without even realizing it. FTP (file
transfer protocol) used to download files from a browser.
• Browser Compatibility:
A web browser is a software application that is used to
locate, receive and display content received from the web servers. Popular web
browsers include Mozilla Firefox, Google Chrome, Internet Explorer and Safari.
Web developers and Web development agencies test the website see how it
displays on multiple browsers across multiple devices and screen sizes before
launching the website.
• Server Software:
Apache and Windows IIS

3.3 Software Interfaces

• Front End: HTML, CSS, JavaScript, Ajax, JQuery

• Server: Side Scripting: PHP, ASP
• CMS: WordPress + Woo commerce, Magento, OpenCart, PrestaShop
• Database: MySQL, MSSQL

3.4 Communications Interfaces

• Browser Compatibility:
Mozilla Firefox, Google Chrome, Internet Explorer and
Safari
• SSL (secure sockets layer) and TLS (transport layer security) are the protocols
associated with trust and security for our website.
• Server Software:
Software Requirements Specification for <Project> Page 6

Apache and Windows IIS

• Web Server:
Linux operating system

4. System Features
Silent Features
• Menu driven, Key board and mouse navigation
• Paperless practice
• Improve efficiency, productivity
• Cost effective solutions
• Graphical User Interface with Context Sensitive Help
• No special training needed for using the system
• Anyone who don’t have accounting knowledge can use without
any difficulty
General Features
• Automatic importing of drug list
• Inbuilt account group and account ledgers
• Option for setting default company
• Keep address book / telephone directory for easy access
• Maintain customer relationship
• Incorporates Calculator with system
• Option for sending mail from Pharma itself
• Provides multi user environment

5. functional Requirements
There are function done by the system such as: store the necessary information of
drugs, prepare bill for the medicine , give week reports, easily searching of medicine,
working in two languages, update, save, and delete data of medicine.

The function what the system do is

➢ Store medicine data’s
➢ Search medicine data effectively
➢ Update, delete, and edit medicine information
Software Requirements Specification for <Project> Page 7

➢ Generate report on medicine

➢ Prepare bill for the medicine
➢ Gives navigation or information for the pharmacy organization
➢ Give alert for the user when medicine item is low
➢ Changing in login password
➢ Have the system document how to use the system

5.1 Performance Requirements

• Any page of the application should not take more than 6 seconds to load on a
DSL broadband connection.
• The system may be throttled or slowed down on heavy loads to ensure service
for everybody. By throttling is meant that certain functionality may be
unavailable during heavy server load.
• The application should be able to support 100 concurrent users without any
performance degradation.
• Although striving to have a 100% uptime, unless during a scheduled
maintenance period, which will be relayed to the users of the site well in
advance, problems may occur. No hesitation will be present when the need arises
to move over to another server, should the current server be insufficient to
provide a decent level of service consistently.

5.2 Safety Requirements

• Use SSL and ensure that your website is PCI compliant

• Insist on customers using strong passwords
• Use a web application firewall for network level security

5.3 Security Requirements

• Public has read-only access via website

• API provides read-only data access
• Profile editing requires password-protected user account with manually-
assigned rights
• Change log records details on data modification (date, username)
Software Requirements Specification for <Project> Page 8

• Consideration will be given to potentially hiding of email address from public

view to avoid collection by
• spam senders

5.4 Software Quality Attributes

• Security (and reliability): As a user, I want the system to be secure so that I am

confident using it. But security is not visible as-is, and need to be reflected in the
usability. If there is an outage, the best to regain confidence of the customer is
IMO to be transparent with what happened.
• Usability: As a user, I want the feel at ease with the system. I don't need
something fancy, but something usable, which provide the feature that make me
feel comfortable with it. Usability also relate to the overall impression of
security, e.g. the email that I receive to confirm a registration can give me a better
or worse impression of the system, or the the way my credit card is shown
(usually only the last digit), etc. all these usability details can increase my trust
in the system.
• Availability: As a user, if the site is down or there are instability I get a really
bad impression. Make sure you can degrade the quality of service and at least
have a nice page indicating scheduled maintenance or service saturation.
• Performance (and response time): Performance would come only then. I don't
want to have to wait excessively, but as long as I get a feedback about what's
going on, I can wait a bit.

5.5 Business Rules

• Starting from national level
• Expansion of business all over the world
• Providing high quality service
• Fit into the mind of the customer
• Image building of Pakistan that lead to increase in the market
• Reducing cost of business
• Use of more advanced technology
Software Requirements Specification for <Project> Page 9

6. Non-Functional Requirements
• Java and allied web technologies should be used for development of the website.
• Apache’s Tomcat Web-Server should be used to deploy the application.
• MySQL should be used as the database.
• All the images used on the site must be procured through legal channels and
there should be no copyright violations
• The system should be developed in such a way that it can be easily reused,
deployed and tested.
• The system should be able to protect and preserve transactions.
• The system should be portable to various operating environments.