Srs Online Retail Management System

230
srs
srs (software requirments specifications)

SRS Online Retail Management System

It is a web-based Retail Management System for XYZ Shop. Details regarding the different users involved in the system and the functions which they can perform are given below:

 


 

Scope of Project Online Retail Management System:

Project scope is the part of project planning that involves determining and documenting a list of specific project  goals, deliverables, tasks, costs and deadlines. Defining the project scope involves adopting a clear vision and an agreement on the outcomes of the project. This allows each milestone of the project to stay on target

Functional and Non Functional Requirements of Online Retail Management System:

Functional Requirements :

A functional requirement shows that what the system must do what services the system present to users. It describes a software system or its component. A function is nothing but inputs to the software system, its behavior, and outputs

Functional Requirements of Online Retail Management System:

Following are the users of this system. Each user has to login first, to use the system.  Purchaser
 Seller
 Auditor
 Admin
Responsibilities and functions of each user are given below:
Purchaser:
1. There is only one purchaser in the system which can purchase different product items from
any wholesaler within the area. The purchaser can buy one or more product items from
one wholesaler. 2. Purchaser can access and browse the system and buy product items from the list (shows in
the system). 3. The information which a purchaser can access include 3 non-editable and 6 editable
contents:
a. Non-Editable
 Product ID
 Product Name
 Shelf No (Where it will be placed)
b. Editable
 Purchase Product Quantity  Purchase Product Price
 Purchase Total Price(Calculated automatically)  Wholesaler name
 Wholesaler Phone no
 Wholesaler Address
Seller:
1. Seller is responsible to manage the records of sold products. There may be many sellers in
the systems. The seller can sell one or more products to one buyer. 2. The information a seller can access include 3 editable and 4 non-editable contents:
c. Editable
 Product ID
 Product Name
 Shelf No (Where it was placed)
d. Non-Editable
 Seller ID
 Sale Product Quantity  Sale Product Price
 Sale Product Total (Calculated automatically)
Auditor:
1. There is only one auditor. 2. The system which an auditor can access include 13 non-editable contents:  Product ID
 Product Name
 Shelf No (Where it will be placed)  Purchase Product Quantity  Purchase Product Price
 Purchase Total Price(Calculated automatically)  Wholesaler name
 Wholesaler Phone no
 Wholesaler Address  Seller ID
 Sale Product Quantity  Sale Product Price
 Sale Product Total (Calculated automatically)
Admin:
1. Admin is the power user and has the rights of each user. He can add/remove the
Purchaser, Seller and Audito

NON-FUNCTIONAL REQUIREMENTS Online Retail Management System:

  • Application is user friendly.
  • Application Perform fast manipulation and calculations.
  • Application is adaptable.
  • Application will be able to work on all types of operating systems.
  • Application will be capable to handle multi user activities simultaneously.
  • There will be back up system to face any problem in system
  • All the options should be learning friendly I.e. member could easily understand what that option will do if he clicked on it.
  • Response Time is very awesome.
Some others are:
  • Accessibility
  • Maintainability
  •  Fault Tolerance.
  • Security
  • Robustnes



 

Use Case Diagram of Diagnosis of Online Retail Management System

a use case diagram can summarize the details of your system’s users   and their interactions with the system. Scenarios in which your system or application interacts with organizations, people, or external systems. Goals that your system or application helps those entities achieve



 

 

Usage Scenarios Diagnosis of Online Retail Management System:

A brief user story explaining who is using the system and what they are trying to accomplish. A Scenario is made up of a number of simple, discrete steps that are designated as being performed by either the System or a  User.

 

ADOPTED METHODOLOGY for Online Retail Management System:

The adopted methodology for this project is vu process model. Vu process model is a combination of water-fall model and spiral model. This combination has many advantages. This model has high risk analysis so avoidance of risk would be achieved. This model is easy to understand and use. Now first we will discuss the Water-fall model.



 

Work Plan of Diagnosis of Online Retail Management System:

Work plan



for complete srs contact us

watsapp: 03469806607