Professional Documents
Culture Documents
Specification
For
Version 1.0
<2016-AG-7916>
<2016-AG-7942>
<2016-AG-7962>
<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
FUNCTIONAL REQUIREMENTS
7. The scope of the work
8. The scope of the Product
9. Functional and data requirement
2
1.Purpose Of Project
As We all know that technology is Progressing at very High Pace. Every Thing Is being Digital.
People are bringing their shops online so that they may gain some customer and increase their services. In
the Same way we were assigned this Project By Metro Shoes Faisalabad to Bring their System on the
Internet so that they can meet the need of the current era.
3
1.1.1 Data Flow Diagrams:
Context Level Diagram
4
Level 1 Diagram
5
9. Functional and Data
Requirements
Requirement # MIS001
Requirement type: Functional Requirements
Event / Use Case 1.1
Description:
Source:
Rationale (justification):
Dependencies:
Conflicts:
History:
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 number of products available in the stake.
Source:
6
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:
History:
Requirement # 4
Requirement type: Functional Requirements
Event / Use Case 1.1
Description:
The system should enable the user to search the product in Particular categories and in his prize
range. .
Source:
Admin
Rationale (justification):
Dependencies:
Conflicts:
History:
Requirement # 5
Requirement type: Functional Requirements
Event / Use Case 1.1
7
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):
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:
8
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 # 9
Requirement type: Functional Requirements
Event / Use Case 1.1
Description:
There should record all the details of User. Like previously used address, Provided phone number,
and the products user has bought in Past.
Source:
Admin
Rationale (justification):
Dependencies:
Conflicts:
History:
Requirement # 10
Requirement type: Functional Requirements
Event / Use Case 1.1
Description:
The system should provide shopping cart during online purchase. So that customer can order more
than one products at the same time.
Source:
Admin
9
Rationale (justification):
Dependencies:
Conflicts:
History:
Requirement # 11
Requirement type: Functional Requirements
Event / Use Case 1.1
Description:
The system should display the recommended Products to the user.
Source:
Admin
Rationale (justification):
Dependencies:
Conflicts:
History:
Requirement # 12
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 # 13
Requirement type: Functional Requirements
Event / Use Case 1.1
10
Description:
The system should display all the charges including shipping charges.
Source:
Admin
Rationale (justification):
Dependencies:
Conflicts:
History:
11
12
13
14
15
16
17
18
19
20