Update SRS - xeeshad/E-commerce GitHub Wiki

E-Medicine Project Software Requirements Specification

                Tanvir  Hossain Jishad- 16 

              Md.Mozahidul Islam -1620755642
             Md.Abdul Aziz - 1711757042

Date Version Description Author <28/10/19> <1.0> SRS 1.0 Group-1

Table of Contents

  1. Introduction 4 1.1 Purpose 4 1.2 Scope 4 1.3 Overview 4
  2. Overall Description 5
  3. Specific Requirements 5 3.1 Functionality 5

3.1.1 Ordered Products 5. 3.1.2 View categories 6 3.1.3 Show News & perspective. 6
3.1.4 Provide Search facility. 7 3.1.5 View Doctor Schedule 8.
3.1.6 Allow online change or cancellation of order. 9 3.2 Usability 10 3.2.1 Graphical User Interface 10 3.2.2 Accessibility 10 3.3 Reliability & Availability 10 3.3.1 Back-end Internal Computers 10 3.3.2 Internet Service Provider 11 3.4 Performance 11 3.5 Security 11 3.5.1 Data Transfer 11 3.5.2 Data Storage 11 3.6 Supportability 11 3.6.1 Configuration Management Tool 11

Software Requirements Specification

  1. Introduction

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 E-Medicine Website by defining the problem statement in detail. Nevertheless, it also concentrates on the capabilities required by stakeholders and their needs while defining all kind medicine features. The detailed requirements of the E- Medicine are provided in this document.

1.1 Purpose

The purpose of the document is shopping online medicine and all other pharmacy product without any suffer. Also it will reduce the suffering of old age people also young. Now a days everyone is busy so that we provide a service for saving their valuable time.

In short, the purpose of this SRS document is to provide a detailed overview of our software product, 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 product and its functionality. Nonetheless, it helps any designer and developer to assist in software delivery lifecycle (SDLC) processes.

1.2 Scope

Primarily, the scope pertains to the E-Medicine product features for making E-MEDICINE live. It focuses on the company, the stakeholders and applications, which allow for online sales, distribution and marketing of products.

This SRS is also aimed at specifying requirements of software to be developed but it can also be applied to assist in the selection of commercial software products. The standard can be used to create software 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.3 Overview

The remaining sections of this document provide a general description, including characteristics of the users of this project, the product's hardware, and the functional and data requirements of the product. General description of the project is discussed in section 2 of this document. Section 3 gives the functional requirements, data requirements and constraints and assumptions made while designing the E-Medicine. It also gives the user viewpoint of product. Section 3 also gives the specific requirements of the product. Section 3 also discusses the external interface requirements and gives detailed description of functional requirements.

  1. 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 product perspective from different stakeholders. It provides the detail product functions of E-Medicine with user characteristics permitted constraints, assumptions and dependencies and requirements subsets.

  1. Specific Requirements

The specific requirements are –

3.1 Functionality

Introduction –

This subsection contains the requirements for the E-medicine. These requirements are organized by the features discussed in the vision document. Features from vision 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.1 Ordered Products. CARD:

  1. AS a user I want to order some medicine.

CONFIRMATION:

3.1.1.1 The system shall display all the medicine that is available. 3.1.1.2 The system shall allow new user to 5% discount on their first ordered. 3.1.1.3 AS a user I can add one or more component to the order. 3.1.1.4 The system shall enable free home delivery for new user. 3.1.1.5 The system shall allow a golden user to 10% discount. 3.1.1.6 The system shall allow a premium user to 12% discount on their every order. 3.1.1.7 As a user ,I Can see all my old order

CONFIRMATION:

1 .If the user does not log in, then the system will give a message to log in first. 2. After successful log in the user can add any product which are available. 3. The system will show the payment process after ordering the product.

3.1.2 View Categories CARD: 1.As a user I want to see the categories of medicine 2. AS a user I want to see the list of medicine

Conversation:

3.1.2.1 AS a user I want to see the liver disease medicine. 3.1.2.2 As a user I want to see the heart disease medicine. 3.1.2.3 As a user I want to see the kidney disease medicine 3.1.2.4 As a user I want to see the Skin disease medicine 3.1.2.5 As a user I want to see the eye disease medicine 3.1.2.6 As a user I want to see the cough medicine 3.1.2.7 As a user I want to see the Pain killer medicine

CONFIRMATION:

  1. The system will provide the confirm medicine for the disease which will search the user.
  2. The system will give the proper description of the medicine
  3. The system will also give the information about the side effect of the medicine
  4. The system will give the advice to visit a specialist doctor
  5. The system also give a doctor suggestion about the disease

3.1.3 Show News & perspective

CARD:

  1. As a user I want to see the latest news & views about diseases. CONVERSATION: 3.1.3.1 As a user I want to see the latest news around world 3.1.3.2 As a user I want to see the trending news around the world. 3.13.3 As a user I want to know the solution of perspective diseases.

CONFIRMATION:

1.The system will provide the current news about disease 2.The system will give 100% true news 3. The system will provide some doctor comment about that disease 4.the System will provide some symptoms about that disease 5.the system will give some pre solution and medicine tips about that disease.

3.1.4 Provide Search facility.

CARD: 1.As a user I want to search the medicine by name 2.As a user I want to search the medicine by genetic name 3.As a user I want to search a medicine by disease name

Conversation:

3.1.4.1 The system shall enable user to enter the search text on the screen.

3.1.4.2The system shall enable user to select multiple options on the screen to search.

3.1.4.3The system shall display all the matching products based on the search

3.1.4.4The system shall display only 5 matching result on the current screen.

Confirmation:

1.If the medicine is out of stock then show the another medicine suggestion.

2.The system shall enable user to navigate between the search results.

3 The system shall notify the user when no matching product is found on the search.

3.1.5 View doctor schedule

CARD:

  1. As a user I want to see the doctor schedule

CONVERSATION:

  1. As a user I want to see liver doctor schedule
  2. As a user I want to see brain doctor schedule
  3. As a user I want to see kidney doctor schedule
  4. As a user I want to see skin doctor schedule
  5. As a user I want to see eye doctor schedule
  6. As a user I want to see heart doctor schedule
  7. As a user I want to see cancer doctor schedule
  8. As a user I want to see broken leg doctor schedule

CONFIRMATION:

  1. The system will provide the proper schedule of that doctor.
  2. If the doctor is not available than the system will try to give doctor contact information
  3. The system will provide the proper information of that doctor
  4. The system also provide the doctor fees
  5. If the doctor is not available in Bangladesh than the system will give aa suggestion of another doctor.

3.1.6 Allow online change or cancellation of order.

CARD:

1.AS a user I want to cancel an order 2.As a user I want to change a medicine 3.As a user I want to change all the medicine 4.as a user I can change my shipping address 5.As a user I can change my payment method

CONVERSATION:

1.AS a new user I have to confirm a cancel order after 1 day order.

  1. As a golden user I want to confirm a change in order before 10 hour of delivery hour.

  2. As a premium user I can cancel or change an order before 3 hour.

Confirmation:

  1.The system will charge some money for late information of cancel an order.

2.After changing the shipping address the charges will be high or low . 3.After cancel an order the system show the medicine available in the website.

3.2 Usability 3.2.1 Graphical User Interface

The system shall provide a uniform look and feel between all the web pages.

The system shall provide a digital image for each product in the product catalog.

The system shall provide use of icons and toolbar.

3.3 Reliability & Availability 3.3.1 Back-end Internal Computers

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 RAID V Disk Stripping on all database storage disks.

3.3.2 Internet Service Provider

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.4 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.

The performance shall depend upon hardware components of the client/customer.

3.5 Security 3.5.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.

3.5.2 Data Storage

The customer’s web browser shall never display a customer’s password. It shall always be echoed with special characters representing typed characters.

The customer’s web browser shall never display a customer’s credit card number after retrieving from the database. It shall always be shown with just the last 4 digits of the credit card number.

The system’s back-end servers shall never display a customer’s password. The customer’s password may be reset but never shown.

The system’s back-end servers shall only be accessible to authenticated administrators.

The system’s back-end databases shall be encrypted.

3.6 Supportability 3.6.1 Configuration Management Tool

The source code developed for this system shall be maintained in configuration management tool.

⚠️ **GitHub.com Fallback** ⚠️