Software Requirements

Specification
For

< Online shopping Metro shoe Faisalabad >

Version 1.0

Prepared by <2016-AG-7931 >

<2016-AG-7916>

<2016-AG-7942>

<2016-AG-7962>

< Name of Client >

<10-Nov-2017>
 Table of Contents

PROJECT DRIVERS
1. Purpose of project
1.1 Existing Manual System
1.1.1 Data Flow Diagram
1.1.2 Data Dictionary
1.2 Flaws in Existing Manual Complaint System
1.3 Purpose of the Developing System
2. Client of the System
3. Users of the Product

PROJECT CONSTRAINTS
4. Mandated constraints
4.1 Solution design Constraints
4.2 Implementation environment of the current system
4.3 How long do the developers have for the project.
5. Naming convention and definition
6. Relevant facts and assumptions

FUNCTIONAL REQUIREMENTS
7. The scope of the work
8. The scope of the Product
9. Functional and data requirement

9. Functional and Data Requirements

Requirement # MIS001
Requirement type: Functional Requirements
Event / Use Case 1.1
Description:
Source:
Rationale (justification):
Dependencies:
Conflicts:
History:

Monday 14 Dec 10:00 Am

(Functional requirements with detail and use case model)

2
Requirement # 1
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should allow the user to Login.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 2
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should display all the products that can be configured.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 3
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should allow the user to select the product to configure
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

3
History:

Requirement # 4
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should enable the user to enter the search text on screen.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 5
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should enable the user to add one or more item to the configuration.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 6
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should display detailed information of the selected product.
Source:
Admin
Rationale (justification):

4
Dependencies:

Conflicts:

History:

Requirement # 7
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should display the reviews and rating of each product, when it is selected.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 8
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should display available payment methods for order.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 8
Requirement type: Functional Requirements
Event / Use Case 1.1

5
Description:
There should be some mechanism to record all detail of purchasing.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 9
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should provide shopping cart during online purchase.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 10
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should display all the available promotions to the user.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

6
Requirement # 11
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should display different shipping option provided by shipping department.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

Requirement # 12
Requirement type: Functional Requirements
Event / Use Case 1.1

Description:
The system should display shipping charges.
Source:
Admin
Rationale (justification):

Dependencies:

Conflicts:

History:

7
8
9
10
11
12
13
14
15
16