SRS_v1.0
SRS_v1.0
SRS_v1.0
Chemists World
Software Requirements Specification
Version <1.0>
Chemists World Version: 1.0
Software Requirements Specification Date: 11/25//15
<document identifier>
Revision History
Date Version Description Author
11/25/15 1.0 SRS 1.0 Danish
Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 Definitions, Acronyms, and Abbreviations 5
1.4 References 5
1.5 Overview 5
2. Overall Description 5
3. Specific Requirements 5
3.1 Functionality 6
3.1.1 Types of User 6
3.1.2 Provide Login/Sign Up Facility to Customer 6
3.1.3 Homepage 6
3.1.4 Chemist Catalog Page (Search Result Page) 7
3.1.5 Chemist portfolio Page 7
3.1.6 Order Page 7
3.1.7 Blog Page 8
3.1.8 My Account Page 8
3.1.9 Chemist Dashboard Page 8
3.1.10 Admin Dashboard Page 9
3.2 Reliability & Availability 9
3.2.1 Back-end Internal Computers 9
3.2.2 Internet Service Provider 9
3.3 Performance 9
3.4 Security 9
3.4.1 Data Transfer 10
3.4.2 Data Storage 10
3.5 Supportability 10
3.5.1 Configuration Management Tool 10
3.6 Design Constraints 10
3.6.1 Standard Development Tools 10
3.6.2 Web Based Product 10
3.7 On-line User Documentation and Help System Requirements 11
3.8 Purchased Components 11
3.9 Interfaces 11
3.9.1 User Interfaces 11
3.9.2 Hardware Interfaces 11
3.9.3 Communications Interfaces 11
3.10 Licensing Requirements 12
3.11 Legal, Copyright, and Other Notices 12
3.12 Applicable Standards 12
4. Supporting Information 12
The introduction of the Software Requirements Specification (SRS) provides an overview of the
entire SRS with purpose, scope, definitions, acronyms, abbreviations, references and overview
of the SRS. The aim of this document is to gather and analyze and give an in-depth insight of the
complete Chemist World Listing Site by defining the problem statement in detail. Nevertheless,
it also concentrates on the capabilities required by stakeholders and their needs while defining
high-level product features. The detailed requirements of the Chemist World Listing Site are
provided in this document.
1.1 Purpose
The purpose of the document is to collect and analyze all assorted ideas that have come up to
define the system, its requirements with respect to consumers. Also, we shall predict and sort
out how we hope this product will be used in order to gain a better understanding of the
project, outline concepts that may be developed later, and document ideas that are being
considered, but may be discarded as the product develops.
In short, the purpose of this SRS document is to provide a detailed overview of our application,
its parameters and goals. This document describes the project's target audience and its user
interface, hardware and software requirements. It defines how our client, team and audience
see the application and its functionality. Nonetheless, it helps any designer and developer to
assist in software development lifecycle (SDLC) processes.
1.2 Scope
Primarily, the scope pertains to the Chemist listing application features for making Chemist
world application live. It focuses on the company, the stakeholders and applications, which
allow for online listings and marketing of local chemists.
This SRS is also aimed at specifying requirements of application to be developed but it can also
be applied to assist in the selection of in-house and commercial application products. The
standard can be used to create application requirements specifications directly or can be used
as a model for defining an organization or project specific standard. It does not identify any
specific method, nomenclature or tool for preparing an SRS.
1.4 References
The references are:
ü netmeds.com
ü apollopharmacy.in
1.5 Overview
The remaining sections of this document provide a general description, including characteristics
of the users of this application, the application's hardware, and the functional and data
requirements of the application. General description of the application is discussed in section 2
of this document. Section 3 gives the functional requirements, data requirements and
constraints and assumptions made while designing the Chemist Listing Site. It also gives the
user view point of application. Section 3 also gives the specific requirements of the
application. Section 3 also discusses the external interface requirements and gives detailed
description of functional requirements. Section 4 is for supporting information.
2. Overall Description
This document contains the problem statement that the current system is facing which is
hampering the growth opportunities of the company. It further contains a list of the
stakeholders and users of the proposed solution. It also illustrates the needs and wants of the
stakeholders that were identified in the brainstorming exercise as part of the requirements
workshop. It further lists and briefly describes the major features and a brief description of
each of the proposed system.
The following SRS contains the detail application perspective from different stakeholders. It
provides the detail application functions of chemists listings with user characteristics permitted
constraints, assumptions and dependencies and requirements subsets.
3. Specific Requirements
3.1 Functionality
Introduction – This subsection contains the requirements for the Listing Site. These
requirements are organized by the features discussed in the PFL document. Features from PFL
documents are then refined into use case diagrams and to sequence diagram to best capture
the functional requirements of the system. All these functional requirements can be traced
using tractability matrix.
3.1.3 Homepage
3.1.3.1 Client Logo will be displayed on the top left header on the main page.
3.1.3.2 Main Menu will be displayed.
3.1.3.3 Image Banner will be displayed on full screen
3.1.3.4 Searching parameters will be displayed to user where user may enter city or choose
location to get chemist listing on click find chemist.
3.1.3.5 User may also view mobile app links which will redirect user to application store.
3.1.3.6 User may view copyright details, social network icons to follow and static links like
Terms & Conditions and Privacy Policy.
The system shall provide storage of all databases on redundant computers with automatic
switchover.
The system shall provide for replication of databases to off-site storage locations.
The system shall provide a contractual agreement with an internet service provider for T3
access with 99.9999% availability.
The system shall provide a contractual agreement with an internet service provider who can
provide 99.999% availability through their network facilities onto the internet.
3.3 Performance
The product shall be based on web and has to be run from a web server.
The product shall take initial load time depending on internet connection strength which also
depends on the media from which the product is run.
3.4 Security
3.4.1 Data Transfer
The system shall use secure sockets in all transactions that include any confidential customer
information.
The system shall automatically log out all customers after a period of inactivity.
The system shall confirm all transactions with the customer’s web browser.
The system shall not leave any cookies on the customer’s computer containing the user’s
password.
The system shall not leave any cookies on the customer’s computer containing any of the user’s
confidential information.
The customer’s web browser shall never display a customer’s password. It shall always be
echoed with special characters representing typed characters.
The system’s back-end servers shall never display a customer’s password. The customer’s
password may be reset but never shown.
3.5 Supportability
3.5.1 Configuration Management Tool
The source code developed for this system shall be maintained in configuration management
tool.
The system shall be built using a standard web page development tool that conforms to either
IBM’s CUA standards or Microsoft’s GUI standards.
There are no memory requirements. The computers must be equipped with web browsers such
as Internet explorer. The product must be stored in such a way that allows the client easy
access to it. Response time for loading the website should take no longer than five minutes. A
general knowledge of basic computer skills is required to use the website
3.9 Interfaces
There are many types of interfaces. User Interface, Software Interface and Hardware Interface.
The protocol used shall be HTTP. The Port number used will be 80. There shall be logical
address of the system in IPv4 format.
The user interface shall be implemented using any tool or software package like PHP.
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
Cross-Cable.
Chemist World shall use the HTTP protocol for communication over the internet and for the
intranet communication will be through TCP/IP protocol suite.
Chemist World should display the disclaimers, copyright, word mark, trademark and product
warranties.
4. Supporting Information