Design DocumentBS110201522
Design DocumentBS110201522
Version 1.0
Revision History
Table of Contents
Sr No Topics Page No
3 Sequence Diagrams 6
5 Class Diagram 12
6 Database Design 13
7 Interface Design 14
8 Test Cases 16
The software design document tells us that how the requirements of the software should be implemented
as well as provides an overall guidance of the project architecture. It provides the detail description of
each and every part of the design that how they will work.
The Software design document benefits in the proper evaluation and maintenance of the software.
Design document helps in the speedy development of the software. It supports in the integration and unit
testing of the software’s structure and interface.
The design document contains following things:
1. Entity relationship diagrams a graphical representation of a system between that which
will show relationship between entities and their attributes.
2. Sequence diagrams which shows how processes operate with one another and in what
order.
3. Architecture Design Diagrams are used to represent data in the form of layers. It
describes the major functionality and performance requirements of the system as well as
the non-functional requirements.
4. Class diagrams which shows the system classes, their attributes, methods and
relationship. It is the static view of the system. It helps in developing executable code of
the software application.-
5. Database diagram which shows a detailed data model of a database.
6. Interface diagram shows the user interface of the application.
7. Test cases are used to test the application.
3. Sequence Diagrams :
6|Page
7|Page
8|Page
9|Page
10 | P a g e
4.
5.
6.
7.
8.
9.
10.
11.
11 | P a g e
12.
13.
14.
15.
16.
17.
18.
19.
12 | P a g e
5. Class Diagram:
13 | P a g e
6. Database Design:
14 | P a g e
7. Interface Design
Snapshot 1
Snapshot 2
15 | P a g e
Snapshot 3:
16 | P a g e
8. Test Cases
Use Case Id 01
Result Pass
Use Case Id 02
Pre Condition All types of users can view FAQs. The website much be active.
Result Pass
17 | P a g e
Use Case Id 03
Admin should be login then add different categories of auto
Actions parts.
Result Pass
Use Case Id 04
Pre Condition Admin and buyers must be login to access this field.
Result Pass
18 | P a g e
Use Case Id 05
Result Pass
Use Case Id 06
Result Pass
19 | P a g e
Use Case Id 07
Result Pass
Use Case Id 08
Result Pass
20 | P a g e
Use Case Id 09
Buyer open the webpage and write product name in search bar.
Actions Click on search.
Result Pass
Use Case Id 10
Result Pass
21 | P a g e
Use Case Id 11
Result Pass
Use Case Id 12
First Login
View notifications
Actions View his orders list.
Check the status of order, shipping etc.
Result Pass
22 | P a g e
Use Case Id 13
First Login
Actions View notifications
View his orders history
Result Pass
Use Case Id 14
Pre Condition User must be registered and account should be open/ login
Result Pass
23 | P a g e
Use Case Id 15
Result Pass
Use Case Id 16
Result Pass
24 | P a g e
Use Case Id 17
Result Pass
Use Case Id 18
Result Pass
25 | P a g e
Use Case Id 19
Actions User give email id password and then fill personal information
Result Pass
Use Case Id 20
Result Pass