Software Design Document, Testing, and Deployment and Configuration Management
Software Design Document, Testing, and Deployment and Configuration Management
Configuration Management
Page i
Page ii
Software Design Document, UUIS
Members :
Name Student ID
Page iii
Software Design Document, UUIS
TABLE OF CONTENTS
Contents
TABLE OF CONTENTS...................................................................................................................................3
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
3. Component design..........................................................................................................................................2
3.3. Register...................................................................................................................................................7
Page iv
Software Design Document, UUIS
3.11. Buying..............................................................................................................................................23
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:
User Interface (UI) Design Document for the A24 Fashion Store
Entity Relationship Diagrams (ERDs) for the A24 Fashion Store Database
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.
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.
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.
Page 3
Software Design Document, UUIS
Page 4
Software Design Document, UUIS
Page 5
Software Design Document, UUIS
Page 6
Software Design Document, UUIS
3.3. Register
Page 7
Software Design Document, UUIS
Page 8
Software Design Document, UUIS
Page 9
Software Design Document, UUIS
Page 10
Software Design Document, UUIS
Page 11
Software Design Document, UUIS
Page 12
Software Design Document, UUIS
Page 13
Software Design Document, UUIS
Page 14
Software Design Document, UUIS
Page 15
Software Design Document, UUIS
Page 16
Software Design Document, UUIS
Page 17
Software Design Document, UUIS
Page 18
Software Design Document, UUIS
Page 19
Software Design Document, UUIS
Page 20
Software Design Document, UUIS
Page 21
Software Design Document, UUIS
Page 22
Software Design Document, UUIS
3.11. Buying
Page 23
Software Design Document, UUIS
Page 24
Software Design Document, UUIS
Page 25
Software Design Document, UUIS
Page 26
Software Design Document, UUIS
Page 27
Software Design Document, UUIS
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
Page 45
Software Design Document, UUIS
Page 46
Software Design Document, UUIS
Page 47
Software Design Document, UUIS
Page 48
Software Design Document, UUIS
Page 49
Software Design Document, UUIS
Page 50
Software Design Document, UUIS
Page 51
Software Design Document, UUIS
Page 52
Software Design Document, UUIS
Page 53
Software Design Document, UUIS
Page 54
Software Design Document, UUIS
Page 55
Software Design Document, UUIS
Page 56
Software Design Document, UUIS
Page 57