Download Software Requirements Specification for an Online Medicine Shop and more Summaries Software Development in PDF only on Docsity!
Practical :- 1
Software Requirement Specification
A Software Requirements Specification (SRS) is a document that describes the nature of a project, software or application. There are a set of guidelines to be followed while preparing the software requirement specification document. This includes the purpose, scope, functional and nonfunctional requirements, software and hardware requirements of the project. In addition to this, it also contains the information about environmental conditions required, safety and security requirements, software quality attributes of the project etc. In this document, our project is used as an example to explain few points.
- Introduction
- General description
- Functional Requirements
- Interface Requirements
- Performance Requirements
- Design Constraints
- Non-Functional Attributes
- Preliminary Schedule and Budget
- Appendices
Table content of SRS Document
- Introduction……………………………………………………………………………………………………………………………..
- 1.1 Purpose of this document………………………………………………………………………………………
- 1.2 Scope of document…………………………………………………………………………………………………
- 1.3 overview…………………………………………………………………………………………………………………
- General description………………………………………………………………………………………………………………….
- 2.1 Product Perspective………………………………………………………………………………………………..
- 2.2 Product features……………………………………………………………………………………………………..
- 2.3 Operating Environment…………………………………………………………………………………………..
- 2.4 Assumption Dependencies………………………………………………………………………………………
- Functional Requirements………………………………………………………………………………………………………….
- 3.1 Description and priority…………………………………………………………………………………………..
- 3.2 Stimulus/response sequence………………………………………………………………………………….
- 3.3 Functional requirement…………………………………………………………………………………………..
- Interface Requirements……………………………………………………………………………………………………………
- 4.1 User interface………………………………………………………………………………………………………...
- 4.2 Hardware interface…………………………………………………………………………………………………
- 4.3 Software interface…………………………………………………………………………………………………..
- 4.4 Communication interface………………………………………………………………………………………..
- Performance Requirements……………………………………………………………………………………………………..
- Design Constraints……………………………………………………………………………………………………………………
- 6.1 Standard Development Tools ………………………………………………………………………………….
- 6.2 Web Based Product…………………………………………………………………………………………………
- Non-Functional Attributes………………………………………………………………………………………………………
- Preliminary Schedule and Budget……………………………………………………………………………………………
- Appendices…………………………………………………………………………………………………………………………….
For the registration they have to upload some liigal proof of their medical. Once the admin approved their application they can add details about the medical and available medicine on our platform. By the user side, user can search for the medical according to their state and city. At the same time the user can get the medicine that he or she does not get from anywhere.
2) General description
PRODUCT PERSPECTIVE
An online medicine shop stores the following information.
Admins table contains basic information about admin.
Medicine table contains information about medicine.
User table contains information about user.
PRODUCT FEATURES
Admin
Admin login to system and register medical. Admin also manage the database.
Admin can remove the medical if any illegal activity done by them.
Medical
Medical login to system via email id and password and perfom different role like add , update and delete details about medicine.
Medical also maintain their profile.
User
User can order medicine from our plate-form but for the safety purpose they have to login first. User also update their information at their profile and see their payment history also.
Operating Environment
Operating environment for the Online Medicine Shop is as listed below.
- Database
- Client/Server system
- Operating system: windows
- Database: Mysql
- Platform: PHP
Assumption Dependencies
It is assumed that one hundred medicals will be register before the system is installed and tested.
FUNCTIONAL REQUIREMENTS
Other system features include:
CLIENT/SERVER SYSTEM
The term client/server refers primarily to an architecture or logical division
of responsibilities, the client is the web application (also known as the front- end), and the server is the DBMS (also known as the back-end).
A client/server system is a distributed system in which,
Some sites are client sites and others are server sites.
All the data resides at the server sites.
All web applications execute at the client sites.
4) INTERFACE REQUIREMENTS:
4.1 USER INTERFACES
Front-end software: PHP
Back-end software: PHPMYADMIN
4.2 HARDWARE INTERFACES
Windows.
A browser which supports CSS, HTML & JAVASCRIPT, JQUERY, AJAX.
4.3 SOFTWARE INTERFACES
Following are the software used for the online medical shop application.
- Operating system: We have chosen Windows operating system for its best support and user-friendliness.
- Database: To save the medicine data, medical information, we have chosen PHP MYADMIN database.
- Implementation: To implement the project we have chosen PHP for its more interactive support.
4.4 COMMUNICATION INTERFACES
This project supports all types of web browser
5) Performance Requirements
The product shall be 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.
The performance shall depend upon hardware components of the client/customers.
7) Non-Functional Attributes
Any familiar in using windows operation can operate the system since it have user friendly and easy to use user interface. Reliability The system is available based on the user needs, can work properly and do transactions efficiently including safe management of the pharmacy. The system is password protected to change things on the system. Here the pharmacist Manager control over the system by login to the system. Any user can not use the system without registered by the Administrator and all result data is protected and controlled by the Administrator Security
o User Identification : The system needs the Customer to recognize herself or himself.
o Logon ID: Any users who make use of the system need to hold a Logon ID and password.
o Modifications: Any modifications like insert, delete, update, etc. for the database can be synchronized quickly and executed only by the ward administrator(developer).
o Performance:
- Response Time: The system provides acknowledgment in just one second once the user's information is checked.
- Capacity: The system needs to support at least 1000 medical store at once.
- User-Interface: The user interface acknowledges within five seconds.
- Conformity: The system needs to ensure that the guidelines of the Microsoft accessibilities are followed. o Maintainability:
- Back-Up: The system offers the efficiency for data back up.
- Errors: The system will track every mistake as well as keep a log of it. o Reliability:
- Availability: The system is available all the time.
8) Preliminary Schedule and Budget
Particulars/details Ext.hrs. Rate hr. amount
1 Designing page layout, colour scheme, buttons etc. 15 1,000 15,
2 Home page content finalization with corrections 8 2,000 16,
3 About Us page and services page layout 12 2,000 24,
4 About us page and services page layout content 3 1,000 3,
5 About us page and services page finalization 15 1,000 15,
6 CSS coding for layout 12 2,000 24,
7 CSS coding for payment gateway 15 1,000 15,
8 Blog page design layout 5 1,200 6,
9 Domain registration 1 25,000 25,
10 Hosting 1 15,000 15,
11 CSS coding for payment gateway 1 25,000 25,
12 Logo creating/designing. 1 7,000 7,
13 Blog page design layout finalization 2 1,000 2,
14 Proof reading of the main pages 20 2,000 40,
15 Additional editing as per client’s requirement 5 1,500 7,
