0% found this document useful (0 votes)
14 views

Software Design Document, Testing, and Deployment and Configuration Management

Uploaded by

tivip.003
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views

Software Design Document, Testing, and Deployment and Configuration Management

Uploaded by

tivip.003
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 49

Software Design Document,

Testing, and Deployment and

Configuration Management

Online Shop Platform A24 (OSPA24)

Prepared for : University of Economic and


Finances
Version 1.0

Submitted to: Mr. Phan Trong Nghia

Page i
Page ii
Software Design Document, UUIS

Members :

Name Student ID

Do Anh Duy 215050916

Nguyen Tran Quoc Tinh 215050518

Tran Tien Dung 215051376

Thi Ngoc Thuan 215050675

Ha Thi Thanh Thao 215051772

Page iii
Software Design Document, UUIS

TABLE OF CONTENTS

Contents
TABLE OF CONTENTS...................................................................................................................................3

LIST OF FIGURES..........................................................................................Error! Bookmark not defined.

1. Introduction....................................................................................................................................................1

1.1. Purpose....................................................................................................................................................1

1.2. Scope.......................................................................................................................................................1

1.3. References...............................................................................................................................................1

1.4. Overview.................................................................................................................................................2

2. Design considerations.....................................................................................................................................2

2.1. Assumptions............................................................................................................................................2

2.2. Constraints...............................................................................................................................................2

2.3. System environment................................................................................................................................2

2.4. Design methodology...............................................................................................................................2

3. Component design..........................................................................................................................................2

3.1. Manager Login........................................................................................................................................3

3.2. Customer Login......................................................................................................................................4

3.3. Register...................................................................................................................................................7

3.4. Select Item..............................................................................................................................................9

3.5. Add product to cart...............................................................................................................................11

3.6. Manage customer..................................................................................................................................13

3.7. Add new product...................................................................................................................................15

3.8. Delete product.......................................................................................................................................17

Page iv
Software Design Document, UUIS

3.9. Update product......................................................................................................................................19

3.10. View product....................................................................................................................................21

3.11. Buying..............................................................................................................................................23

3.12. View order history............................................................................................................................25

3.13. Subscribing To Newsletter...............................................................................................................27

4. Software interface design.............................................................................................................................30

4.1. User interface design.............................................................................................................................30

4.1.1. User interface...............................................................................................................................45

4.1.1.1. Screen image................................................................................................................................45

Page v
Software Design Document, UUIS

Page vi
Software Design Document, UUIS

1. Introduction
The A24 Fashion Store project aims to create an online platform for selling clothing,
accessories, and jewelry. This document outlines the design considerations and architectural
decisions for the development of the A24 Fashion Store.

1.1. Purpose
The purpose of this Software Design Document (SDD) is to outline the architectural design and technical
specifications for the development of the A24 Fashion Store. It provides a comprehensive guide for the
development team to understand the system requirements, design considerations, and implementation
details necessary to build the online platform successfully.

1.2. Scope
The scope of this SDD encompasses the design and architecture of the A24 Fashion Store,
including both frontend and backend components. It covers aspects such as the client-server
architecture, frontend design considerations, backend implementation details, database
design, security measures, testing strategy, deployment plan, and maintenance procedures.

1.3. References
The user of this SDD may need the following documents for reference:

Requirements Document for the A24 Fashion Store

User Interface (UI) Design Document for the A24 Fashion Store

Entity Relationship Diagrams (ERDs) for the A24 Fashion Store Database

Technical Specifications for Third-party Services (e.g., Payment Gateway).

Page 1
Software Design Document, UUIS

1.4. Overview
The A24 Fashion Store is an online platform for selling clothing, accessories, and jewelry.
The system will follow a client-server architecture, with the frontend built using modern
web technologies such as HTML, CSS, and JavaScript, and the backend developed using
ASP.NET Core . The database will be implemented using Microsoft SQL Server to store
user data, product information, and transaction records.

The frontend design will focus on delivering a user-friendly interface with features such as
product listings, user authentication, shopping cart management, and checkout
functionality.

Post-launch, ongoing maintenance and support will be provided to address issues,


implement new features, and optimize system performance based on user feedback and
business requirements.

2. Design considerations
2.1. Assumptions
Users have basic computer and web browsing skills.
Users are familiar with common terms used in online shopping.

2.2. Constraints
The website is accessible only through web browsers.
The website is developed using modern web technologies such as HTML, CSS, and
JavaScript.

2.3. System environment


The website is designed to be compatible with all major web browsers.
Accessible from any device with internet connectivity.
Available 24/7 for uninterrupted shopping experience.

2.4. Design methodology


The website is designed to be scalable for future expansion and enhancements.
Modular design approach with reusable components for maintainability and flexibility.

3. Component design
“Users with appropriate permission” in the diagram refers to the users who are given
exemptions or/and users of a particular level. Precise permissions are listed in Section 2.3
of SRS.
Page 2
Software Design Document, UUIS

For diagrams with multiple functions, the design is the same for those functions, except for
parameters/methods/classes.

3.1. Manager Login

Figure 1. Sequence diagram for Manager Login

Page 3
Software Design Document, UUIS

Figure 2. Activity diagram for Manager Login

3.2. Customer Login

Page 4
Software Design Document, UUIS

Figure 3. Sequence diagram for Customer Login

Page 5
Software Design Document, UUIS

Figure 4. Activity diagram for Customer Login

Page 6
Software Design Document, UUIS

3.3. Register

Figure 5. Sequence diagram for Register

Page 7
Software Design Document, UUIS

Figure 6. Activity diagram for Register

Page 8
Software Design Document, UUIS

3.4. Select Item

Figure 7. Sequence diagram for Select Item

Page 9
Software Design Document, UUIS

Figure 8. Activity diagram for Select Item

Page 10
Software Design Document, UUIS

3.5. Add product to cart

Figure 9. Sequence diagram for Add product to cart

Page 11
Software Design Document, UUIS

Figure 10. Activity diagram for Add product to cart

Page 12
Software Design Document, UUIS

3.6. Manage customer

Figure 11. Sequence diagram for Manage customer

Page 13
Software Design Document, UUIS

Figure 12. Activity diagram for Manage Customer

Page 14
Software Design Document, UUIS

3.7. Add new product

Figure 13. Sequence diagram for Add new product

Page 15
Software Design Document, UUIS

Figure 14. Activity diagram for Add new product

Page 16
Software Design Document, UUIS

3.8. Delete product

Figure 15. Sequence diagram for Delete product

Page 17
Software Design Document, UUIS

Figure 16. Activity diagram for Delete product

Page 18
Software Design Document, UUIS

3.9. Update product

Figure 17. Sequence diagram for Update product

Page 19
Software Design Document, UUIS

Figure 18. Activity diagram for Update Product

Page 20
Software Design Document, UUIS

3.10. View product

Figure 19. Sequence diagram for View product

Page 21
Software Design Document, UUIS

Figure 20. Activity diagram for View product

Page 22
Software Design Document, UUIS

3.11. Buying

Figure 21. Sequence diagram for Buying

Page 23
Software Design Document, UUIS

Figure 22. Activity diagram for Buying

Page 24
Software Design Document, UUIS

3.12. View order history

Figure 23. Sequence diagram for View order history

Page 25
Software Design Document, UUIS

Figure 24. Activity diagram for View order history

Page 26
Software Design Document, UUIS

3.13. Subscribing To Newsletter

Figure 25. Sequence diagram for Subscribing To Newsletter

Page 27
Software Design Document, UUIS

Figure 26. Activity diagram for Subscribing To Newsletter

Page 28
Software Design Document, UUIS

Page 29
4. Software interface design
4.1. User interface design
UI is designed according to UI design principles.
The structure principle: UI is organized in such a way that related things are combined together and unrelated
things are separated.
The simplicity principle: It is easy to follow the provided interface. In the case of mistake, system displays
error message.
The visibility principle: All system‟s functions are available through UI. It does not overwhelm users with too
many alternatives.
The feedback principle: Through the system of messages, the design keeps users informed of actions,
errors, or exceptions.
The reuse principle: In design, same names were used to perform the same operations with different objects in
order to reduce ambiguity.

Page 44
Software Design Document, UUIS

4.1.1. User interface


Used GUI components are menus, submenus, buttons, text boxes, check boxes, down drop
lists, links, and tables. The only means of access to the entire database, by all users, is
through this UI.

4.1.1.1. Screen image


Some examples of UI are presented below:

Figure 34. “Login” page

Page 45
Software Design Document, UUIS

Figure 35. “Sign up” page.

Page 46
Software Design Document, UUIS

Figure 36. Home page.

Page 47
Software Design Document, UUIS

Figure 37. Section “New Arrivals – Men’s”

Page 48
Software Design Document, UUIS

Figure 38. Section "New Arrivals – Woman.”

Page 49
Software Design Document, UUIS

Figure 39. Section "New Arrivals – Kid’s”

Page 50
Software Design Document, UUIS

Figure 40: Footer.

Page 51
Software Design Document, UUIS

Figure 41. Product page.

Page 52
Software Design Document, UUIS

Figure 42. “Single product” page.

Page 53
Software Design Document, UUIS

Figure 43. “Contact” page

Page 54
Software Design Document, UUIS

Page 55
Software Design Document, UUIS

Page 56
Software Design Document, UUIS

Page 57

You might also like