1. INTRODUCTION 1.1.
Purpose of the SRS
To provide an outline of the software product required to develop an Online Retail System and to specify its associated: Functional, Non-functional Requirements and Constraints
Intended Audience
Following are the intended audience who may refer to this document in present or future times: Organization (for which Software is being developed): Managers of following departments: o Procurement o Shipping o Website Maintenance o Finance/Accounts o Security/Authorization Developer Organization (One developing the product): Designers, who shall design the system for the requirements specified in this document. Developers, who shall develop the product by coding for the specified requirements. Testers, who ensure the product successfully completes the specified requirements. Users: Registered User as a buyer, Registered User as a window shopper, Unregistered User as a buyer, Unregistered User as a window shopper.
1.2. Scope
The software product being proposed by this SRS is Online Retail System. The proposed product shall fill the existing gap, like the geographical distances, lack of availability in a particular region between the end consumers and retailers, with the help of internet benefitting both consumers and retailers in the process.
Section 1.3, 1.4 ans 1.5 I have not written as it seems they will be written in the end after writing everything else.
2. General Description 2.1. Product Perspective
The software product shall provide following benefits to the consumers and retailers: Interfaces The software product shall be self-contained and independent, with following interfaces for users, system and soft wares: User interface: Buyers Employee of the Organization (for which website is developed) System interface: Payment Portal Courier Service (Optional) SMS connectivity Hardware Interface: Clients (PCs) used by users and employees.
2.2. Product Functions
Quick browsing through a variety of products. Buying products at a low price. Ordering products from homes. Increase in the consumer base of the retailers. Managing inventory of the items. Keeping track of the customers and their buying patterns. Protects the personal information and credit card transactions done by the consumer. Protects the system against failures/crash.
2.3. User Characteristics:
The user of the product is expected to have the basic knowledge of computer and internet surfing.
2.4. Constraints: 2.5. Assumptions & Dependencies:
3. Specific Requirements:
This section provides the specific functional and non-functional requirements which the software product shall do for the users of the product.
3.1. Functions (by External Interfaces e.g. Users):
Customers:
3.1.1.
Customers
Preconditions:
Customer browses through variety of products:
External Interface:
No precondition required.
Data Entries (to be done):
Product Category
Data Format:
No particular format is required for this particular input.
3.1.2.
Customers
Preconditions:
Customer selects product/many products to buy:
External Interface:
The system has identified the customer.
Data Entries (to be done):
Selection of the product to be added to the customers basket.
Data Format:
The data of the single user enters into a single basket.
3.1.3.
Customers
Preconditions:
Customer buy(s) product/many products:
External Interface:
The system has identified the customer.
Data Entries (to be done): Mode of payment, Shipping Address, Working Mobile Number
Data Format: 1. Multiple Modes of payment are required to be shown to the customer on a single screen, giving him/her the option of selecting one of them. 2. Correct Shipping Address is required to be specified for shipping the purchased product. 3. Correct Mobile number is required to be specified for contacting the customer.
End Message: An order receipt is generated with a unique Order number on the final order of the bought product(s). The order receipt is sent to the customer through an email and order number through a SMS.
