SDD Mes3043

MES3043
SOFTWARE DESIGN
GROUP PROJECT
Software Design Document
Laundry Delivery System (Rabbit Laundry Service)
PREPARED FOR
Dr. Azniah Binti Ismail
GROUP: B3
MATRIC
NO. STUDENT NAME
NUMBER
1 Mohamad Imran Bin Mohamad Yusri D20211097801
2 Abdul Qayyum Bin Zakaria D20211101136
3 Muhammad Hazeeq Bin Mohd Khairi D20211097790
4 Amar Al Hakim Bin Md Shah D20211097794
5 Muhammad Faris Izzuan Bin Khairol Azani D20211097795
6 Muhamad Aliuddin Bin Mohd Khairunnizam D20211097805

SOFTWARE DESIGN DOCUMENT (SRS)
Version 4.0
Rabbit Laundry Delivery System
Leader Name: Abdul Qayyum Bin Zakaria
Team Member Names
Mohamad Imran Bin Mohamad Yusri
Muhammad Hazeeq Bin Mohd Khairi
Amar Al-Hakim Bin Md Shah
Muhammad Faris Izzuan Bin Khairol Azani
Muhamad Aliuddin Bin Mohd Khairunnizam
This document is based on the IEEE Std 1016-1998,

IEEE Standard for Standard Design Description
REVISION HISTORY & DOCUMENT APPROVAL
Revision History
Date Version Author Revision Details
19/10/2022 Version 1.0 Muhammad Hazeeq First version created
13/11/2022 Version 2.0 Muhammad Hazeeq Major changes in design

Amar Al-Hakim screen flow and design
Mohamad Imran description
Abdul Qayyum Major changes in section 1
Muhamad Aliuddin
Muhammad Faris Izzuan
27/12/2022 Version 2.1 Muhammad Hazeeq Major changes in Software

Amar Al-Hakim Requirement Specification
Mohamad Imran for section 2
Abdul Qayyum
Muhamad Aliuddin
18/1/2022 Version 3.0 Muhammad Hazeeq Major changes in Software

Amar Al-Hakim Requirement Specification
Mohamad Imran for section 3
Abdul Qayyum
Muhamad Aliuddin
9/7/2023 Version 4.0 Muhammad Hazeeq Added changes for section 4

Amar Al-Hakim
Mohamad Imran
Abdul Qayyum
Muhamad Aliuddin
Document Approval
The following Software Requirement and Specification has been accepted and approved by
the following:
Signature Name Date
Abdul Qayyum Bin Zakaria 23/11/2022
- Dr. Azniah Binti Ismail -

TABLE OF CONTENT
NO. CONTENT PAGE
1.0 Introduction
1.1 Purpose 1
1.2 Scope
1
1.3 Definitions
2
1.4 Reference
2
1.5 Overview
2
2.0 Proposed Architecture
2.1 View 1 (ADV 1) 3

2.2 View 2 (ADV 2)
4
2.3 View 3 (ADV 3)
5
3.0 Subsystem Decomposition and Design Goals
3.1 System Decomposition 7

3.2 Design Goals
23
3.3 Addressing Design Goals
26
4.0 Detailed Design
4.1 Navigation Design 39

4.2 Content Design
46
1.0 INTRODUCTION
This section gives a scope of description and an overview of everything included in this
Software Design Document (SDD) document. The purpose of this document is
described, and a list of abbreviations and definitions is provided.
1.1 Purpose
The purpose of this document is to provide detailed information on the designs of all
functions and specifications for the Rabbit Laundry Delivery Service System. This
document will give detailed explanations of the overall architectural design, the
diagram design of the interface, and design details with descriptions. The diagram in
this document uses the Unified Modeling Language (UML) standard. This document
was prepared for the sole purpose of acceptance by a client and as a guide for the
development team to implement the first testing version of the product.
1.2 Scope
The Rabbit Laundry Delivery Service System is an application that allows users to
easily send and receive clean laundry during their packed schedule. The app will also
notify the user if the laundry is finished cleaning and give them the option to either pick
it up themselves or have it delivered to their doorstep.
DOCUMENT IDENTIFICATION
SYSTEM NAME VERSION PAGE
Rabbit Laundry Delivery Service 4.0 1

Classified Version 4.0/SDD
1.3 Definitions
Table 1.3 Definitions, acronyms and abbreviations
Term Definition
GPS Global Positioning System
iOS iPhone Operating System
HarmonyOS Harmony Operating System
1.4 Reference
- https://organizing.tv/best-laundry-delivery-services/
- https://www.sapphiresolutions.net/blog/top-10-trending-laundry-service-apps-
easy-to-use-apps
1.5 Overview
The remaining section of this document will include a general description of the system
that will soon be built, as mentioned in Section 2 of this document, that also provides
several informational items on the system perspective and its functions, user
characteristics, general constraints, assumptions, and dependencies. Section 3 will give
more specific requirements about the external interfaces for building user, hardware,
software, and communication interfaces. Explanations about the details of the system
to be built will be present within Section 3, including overall functional requirements,
use cases, an activity diagram, a class diagram, and quality requirements. Section 4 will
explicitly provide the various interfaces that are related to the Rabbit Laundry Delivery
Service System as well as many different analytical diagrams and models. This will be
shown and explained to give stakeholders and clients a grasp on the project.

2.0 PROPOSED SOFTWARE ARCHITECTURE
2.1 View 1 (ADV 1)
Diagram 1: Architectural Design View (ADV 1)
This is the architectural design view for the Rabbit Laundry Delivery Service
Application. The Rabbit Laundry Delivery Service Application is installed on the
smartphone via the Play Store, App Store, and Huawei App Gallery. There are a few
functions in the application, which include the Face ID function, the Quick Response
(QR) function, the Live Location function and the Premium User function. The Face
ID function needs to use a Face ID Scanner and built-in camera in the smartphone to
scan the user's face for a login alternative. The Quick Response (QR) function also
needs to use the built-in camera on the smartphone and the QR Code Scanner to scan
the QR code for payment purposes. The QR code will be generated when the user

chooses to do the transaction using the QR code. In this application, a cloud database
is used to store the user's data. The Rabbit Laundry Delivery Service Application uses
Application Programming Interface (API) to communicate with Banking Service for
payment purposes and the Google Maps Service for tracking purposes. API also used
to communicate with company servers.
2.2 View 2 (ADV 2)
The Rabbit Laundry Delivery Service Application uses the layered architecture pattern
in its architecture diagram. The layered architecture pattern has each layer handling
different types of roles. The presentation layer is responsible for user interaction with
the application. The business layer handles application function sets that are available
to the end users. The data service layer is responsible for encapsulating the logic for
retrieving, storing, updating, and deleting data, shielding the rest of the application from
the complexities of the underlying data storage technology. Layered architecture
supports scalability by allowing individual layers to be scaled independently. For

instance, if the application experiences increased user demand, the presentation layer
can be scaled horizontally to handle more user requests, while the underlying business
logic and data access layers can remain unchanged. In some cases, the layered
architecture can lead to duplication of code or data transformations across layers. For
example, if the data access layer and the business logic layer perform similar
transformations on data, it can result in redundant code and increased maintenance
effort. Ensuring consistency and avoiding duplication across layers can be challenging.
2.3 View 3 (ADV 3)

Rabbit Laundry Delivery Service application ADV3 describes all the subsystems in the
application. There are 6 subsystems in this application, which are the Account
Subsystem, View Status Subsystem, Menu Subsystem, Order Service Subsystem,
Payment Subsystem, and Tracking Subsystem. Users have to register or sign in as a
member in order to login before they can access the other subsystems. All subsystems
in Rabbit Laundry Delivery Service Application send and receive request data / service
through Application Programming interface (API) that connects to the Cloud Database.
There are three layer in these Architecture Design View 3 which are presentation layers
that contain User interface (UI) and the components that process the UI components
where the functions are presented to the end user. In the presentation layer, Rabbit
Laundry Delivery Service users can view the service that are been requested through
the user interface. Business layer contains application functions that are available to the
end users. It will provide and get data from Rabbit laundry Delivery Service user by
using API for the services. Data service layer allows Rabbit laundry Delivery Service
users to access the data or service requested. For instance, view service provided, scan
QR code, use real-time tracking

3.0 SUBSYSTEM DECOMPOSITION AND DESIGN GOALS
3.1 Subsystem Decomposition
Subsystem Function Presentation Business Data Layer
Account Subsystem To View Account Account Details Package Account Details Validation Account Details DataAccess
Details Package Package
Component P1.1
UIAccountHomepage Component B1.1 Component D1.1
GetAccountDetails() GetAccountDetails_sendData()
Component P1.2
UIAccountMenu Component B1.2 Component D1.2
SenttoValidateDataEntries() GetAccountDetails_DataEntry()
Component P1.3
UIViewAccountDetails Component B1.3
ValidateUsingDatabase()

Component B1.4
SaveValidateResults()
Component B1.5
GetUIViewAccountDetails()

Author’s Name: Abdul Qayyum Bin Zakaria
Diagram 4: Subsystem Decomposition (Account Details)

View Status To View The Status Of Laundry View Laundry Status UI View Laundry View Laundry
Subsystem Order Package Validation Package DataAccess Package
Component P2.1 Component B2.1 Component D2.1

UIViewStatus GetLaundryStatusDetail() GetLaundryStatusDetail_s
endData()
Component B2.2
ValidateUsingDatabase()
Component D2.2
Component B2.3 GetLaundryStatusDetail_
receiveValidationResult() DataEntry()

Author’s Name: Muhamad Aliuddin Bin Mohd Khairunnizam
Diagram 5: Subsystem Decomposition (View Status Subsystem)

Menu Subsystem To display options of Menu UI Package Menu Validation Package Menu DataAccess Package
the subsystem
UIHomepage getViewStatus() ViewStatusDataAccess_SendRequest()

UIMenu getOrderService() ViewStatusDataAccess_ReceiveData()

UIViewStatus getTracking() OrderServiceDataAccess_SendRequest()

UIOrderService getUIViewStatus() OrderServiceDataAccess_ReceiveData()


UITracking getUIOrderService() TrackingDataAccess_SendRequest()
Component B3.6 Component D3.6

getUITracking() TrackingDataAccess_ReceiveData()

Author’s Name: Muhammad Faris Izzuan Bin Khairol Azani
Diagram 6: Subsystem Decomposition (Menu Subsystem)

Order Service Display Order Service Display Order Service UI Display Order Service Display Order Service
Subsystem Provided Package Validation Package Data Access Package

UIHomepage getUIOrderService() OrderServiceDataAccess
Agent_sendRequest()
Component P4.2 Component B4.2
UIMenu getUIViewOrderService Component D4.2
Detail() OrderServiceDataAccess
Component P4.3 Component B4.3 Agent_receiveData()
UIOrderService receiveValidationResult()


UIViewOrderServiceDetail decideScreenDisplay()
Component P4.5
UIViewOrderServiceDetail
Error

Author’s Name: Muhammad Hazeeq Bin Mohd Khairi
Diagram 7 : Subsystem Decomposition (Order Service)

Payment Make Payment Using Payment Option UI Payment Option Validation Payment Option
Subsystem Online Banking And E- Package Package DataAccess Package
Wallet
UIOrderService getUserBankAcc() payment_SendRequest()

UIChoosePayment sendValidationPayment() payment_ReceiveRequest()

UIMakePayment decidePayment()

Component P5.4
UIPaymentSuccessful
Component P5.5
UIPaymentUnsuccessful

Author’s Name: Mohamad Imran Bin Mohamad Yusri
Diagram 8: System Decomposition (Payment Subsystem)

Tracking Subsystem Tracking Tracking Location Tracking Location Option Tracking Location Option
Location Option UI Package Validation Package DataAccess Package
Maps
UIHomepage sendValidationLocationAccess DataLocationAccess_sendRequest()
()
Component P6.2 Component D5.2
UICamera Component B6.2 DataLocationAccess_ReceiveRequest()
receiveValidationLocationAcce
Component P6.3 ss ()
UIScanLocation

Author’s Name: Amar Al-Hakim Bin Md Shah
Diagram 9: System Decomposition (Tracking Subsystem)

3.2 Design Goals
Design Goals QR_ID Quality Requirements Design Criterion Group Design Criterion Subsystem Involved
DESIGN GOAL QR001 Rabbit Laundry Delivery Service RELIABILITY AVAILABILITY Login Subsystem
1 App should work all the time, Homepage Subsystem
24/7 View Status
Subsystem
Menu Subsystem
Order Service
Subsystem
Payment Subsystem
Tracking Subsystem
DESIGN GOAL QR002 Rabbit Laundry Delivery Service USABILITY EASE OF USE Payment Subsystem
2 App QR code reader and face ID Login Subsystem
detection should be user-friendly

DESIGN GOAL QR003 Rabbit Laundry Delivery Service PERFORMANCE RESPONSIVENESS Payment Subsystem
3 App QR code reader should be Login Subsystem
able to detect QR codes, and Face
ID should be able to detect the
user's face
DESIGN GOAL QR004 Rabbit Laundry Delivery Service PERFORMANCE SPEED Login Subsystem
4 App should be able to launch Homepage Subsystem
quickly and work as responsive View Status
Subsystem
Menu Subsystem
Order Service
Subsystem
Payment Subsystem
Tracking Subsystem

DESIGN GOAL QR005 Rabbit Laundry Delivery Service PERFORMANCE EASY TO Login Subsystem
5 App should be able to finish DOWNLOAD Homepage Subsystem
downloading under 1 minutes on View Status
the user’s mobile device Subsystem
Menu Subsystem
Order Service
Subsystem
Payment Subsystem
Tracking Subsystem
DESIGN GOAL QR006 Rabbit Laundry Delivery Service PERFORMANCE STORAGE Login Subsystem
6 App should be able to store many
user account information in the
database

3.3 Addressing Design Goals
Design Goals QR_ID Quality Requirements Design Criterion Group Design Criterion Subsystem Involved
DESIGN GOAL 1 QR001 Rabbit Laundry Delivery RELIABILITY AVAILABILITY Login Subsystem
Service App should work all Homepage
the time, 24/7 Subsystem
View Status
Subsystem
Menu Subsystem
Order Service
Subsystem
Payment Subsystem
Tracking Subsystem

Issues:
1. Mapping Subsystem to Processors and Components

Rabbit Laundry Delivery Service App has been designed to work 24 hours a day to ensure that the services
provided can run smoothly at any time. Furthermore, the internet connection in this application is very important
because it is the main connection between the user's device and the services provided in this app. Also, this
application should be regularly updated and maintained to continue its functions smoothly and provide users
with the best possible experience, including fixing bugs, adding new features, and improving performance, as
well as regularly checking and updating the app's security measures to protect users' data and privacy.
2. Identifying and Storing Persistent Data

The data in the Rabbit Laundry Delivery Service App is stored in the system cloud database, and the users are
able to use all components and functions of our service in these apps. Therefore, users can access all available
functions in this application, with the main condition that they have an internet connection.

3. Providing Access Control

Users can access the application with the main condition that apps require an internet connection to make the
operation system of this application work without any issues. Furthermore, all service functions in the Rabbit
Laundry Delivery Service App are highly dependent on the internet. Therefore, the user should be alert when
using this application because, naturally, this app will not process all the functions if there is no connection to
the internet.
4. Designing The Global Control Flow

Not applicable
5. Identifying Boundary Condition

Not applicable

DESIGN GOAL 2 QR002 Rabbit Laundry Delivery USABILITY EASE OF USE Payment Subsystem
Service App QR code reader Login Subsystem
and face ID detection should
be user-friendly
Issues:

Rabbit Laundry Delivery Service App is a user-friendly application and at the same time, it emphasizes security
features for users. This can be seen when this application is specially designed by placing the function QR code
reader that allows users to make payments via QR Pay. In addition, the use of face ID detection, which utilizes
facial recognition technology to identify and authenticate users, will increase user confidence to continue using
this application safely without hesitation.


Not applicable
Rabbit Laundry Delivery Service App involves implementing security measures to ensure that only authorized
users can access the app and its features. This can be achieved through various means such as requiring users
to set up a secure account, utilizing secure login methods such as password protection, or using face ID
detection. Additionally, this application can also guarantee safer user security when making any payment online.

Not applicable

Not applicable

DESIGN GOAL 3 QR003 Rabbit Laundry Delivery PERFORMANCE RESPONSIVENESS Payment Subsystem
Service App QR code reader Login Subsystem
should be able to detect QR
codes, and Face ID should be
able to detect the user's face
Issues:

Rabbit Laundry Delivery Service App provides some features that can improve the performance for the users
experience especially in security aspects and payment process. This app has been specially designed by placing
the function QR code reader that allows users to make payments via QR Pay. And then, the use of face ID
detection, which utilizes facial recognition technology to identify and authenticate users will increase user
security safety and improve the confidence users to continue using this application safely without hesitation.


Not applicable

Rabbit Laundry Delivery Service App ensures that only authorized users only that can access this application
and its features. This can be achieved through various means such as requiring users to set up a secure account,
utilizing secure login methods such as password protection, or using face ID detection. Additionally, this
application can also guarantee safer user security when making any payment online.

Not applicable

Not applicable

DESIGN GOAL 4 QR004 Rabbit Laundry Delivery PERFORMANCE SPEED Login Subsystem
Service App should be able Homepage
to launch quickly and work Subsystem
responsively. View Status
Subsystem
Menu Subsystem
Order Service
Subsystem
Payment Subsystem
Tracking Subsystem
Issues:

Rabbit Laundry Delivery Service Application stores all information in the cloud database. The application will
be connected to the server all the time, 24/7 in order to be used. Therefore, a server that can hold a large amount

of users and information at the same time is needed for the user to access the data at any time and have a faster
response time.

Not applicable

Rabbit Laundry Delivery Service Application allows users to access all the data that has been stored in the
cloud database at any time, with no delay on the data that has been requested and received.
Not applicable

Not applicable

DESIGN GOAL 5 QR005 Rabbit Laundry Delivery PERFORMANCE EASY TO Login Subsystem
Service App should be able DOWNLOAD Homepage
to finished download under 1 Subsystem
minutes on the user’s mobile View Status
device Subsystem
Menu Subsystem
Order Service
Subsystem
Payment Subsystem
Tracking Subsystem
Issues:

Rabbit Laundry Delivery Service App just needs 1 minute or less to download on the user's mobile device.
Importantly, the users need the internet connection to ensure this app can be downloaded smoothly.


Rabbit Laundry Delivery Service App requires users to allow the application to be downloaded and be accessed
on their device. Therefore, the users must allow the application to be accessed so all application files that are
required could be saved in the user device. Therefore, the application can be run and the user can experience this
application.

The users must allow all permission that has been requested by Rabbit Laundry Delivery Service App. So, the
users can experience the functions that have been provided by this application.

Not applicable

Not applicable

DESIGN GOAL 6 QR006 Rabbit Laundry Delivery PERFORMANCE STORAGE Login Subsystem
Service App should be able
to store many user account
information in the database
Issues:

Rabbit Laundry Delivery Service App uses a database to keep any private data and run the process of the
application. The database used will store and process all user account data for company reference purposes.
Therefore, the data obtained will use a larger space and integrate each account to the center database. Thus, these
apps are able to store many user account information in the database.

All data and account user information will be stored in the cloud database to avoid the problem of data loss or
data damage. As such, all data will be stored preferably in the cloud database in case the account user faces

internet connection problems while using this app.

Only users of the Rabbit Laundry Delivery Service App with a stable internet connection can access their data
files in this application that contains a large amount of user account data.
Not applicable

Not applicable

4.0 DETAILED DESIGN
4.1 Navigation Design
4.1.1 Rabbit Laundry Delivery Service for User Navigation Design







4.2 Content Design
4.2.1 Content Table
Subsystem Importance Level Content Name Content To Be Written In The Screen
Account Subsystem High View and Manage Account 1. User Details

Details 2. User phone number
3. User username
4. User default address
View Status Subsystem High View Laundry Status Progress 1. Order Details
2. Laundry Status
Menu Subsystem High View Main Menu 1. Account Details Menu

2. View Laundry Status Menu

3. Order Service Menu

4. Payment Options
5. Tracking Menu
Order Service High Display Order Service Provided 1. View Order Options
Subsystem 2. Order Service Details
Payment Subsystem High Make Payment And Receive 1. Choose payment options
Payment Receipt 2. Make payments using online
banking
3. Get payment receipt
Tracking Subsystem High Tracking Location Maps 1. Track Laundry Location

SDD Mes3043

Uploaded by

Copyright:

Available Formats

SDD Mes3043

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SDD Mes3043

Uploaded by

Copyright:

Available Formats

MES3043

Software Design Document

Laundry Delivery System (Rabbit Laundry Service)

Dr. Azniah Binti Ismail

1 Mohamad Imran Bin Mohamad Yusri D20211097801

2 Abdul Qayyum Bin Zakaria D20211101136

3 Muhammad Hazeeq Bin Mohd Khairi D20211097790

4 Amar Al Hakim Bin Md Shah D20211097794

5 Muhammad Faris Izzuan Bin Khairol Azani D20211097795

6 Muhamad Aliuddin Bin Mohd Khairunnizam D20211097805

Rabbit Laundry Delivery System

Leader Name: Abdul Qayyum Bin Zakaria

Team Member Names

Mohamad Imran Bin Mohamad Yusri

Muhammad Hazeeq Bin Mohd Khairi

Amar Al-Hakim Bin Md Shah

Muhammad Faris Izzuan Bin Khairol Azani

Muhamad Aliuddin Bin Mohd Khairunnizam

This document is based on the IEEE Std 1016-1998,

Date Version Author Revision Details

19/10/2022 Version 1.0 Muhammad Hazeeq First version created

13/11/2022 Version 2.0 Muhammad Hazeeq Major changes in design

27/12/2022 Version 2.1 Muhammad Hazeeq Major changes in Software

18/1/2022 Version 3.0 Muhammad Hazeeq Major changes in Software

9/7/2023 Version 4.0 Muhammad Hazeeq Added changes for section 4

Signature Name Date

Abdul Qayyum Bin Zakaria 23/11/2022

- Dr. Azniah Binti Ismail -

NO. CONTENT PAGE

2.0 Proposed Architecture

2.1 View 1 (ADV 1) 3

3.0 Subsystem Decomposition and Design Goals

3.1 System Decomposition 7

4.0 Detailed Design

4.1 Navigation Design 39

SYSTEM NAME VERSION PAGE

Rabbit Laundry Delivery Service 4.0 1

Table 1.3 Definitions, acronyms and abbreviations

GPS Global Positioning System

iOS iPhone Operating System

HarmonyOS Harmony Operating System

SYSTEM NAME VERSION PAGE

Rabbit Laundry Delivery Service 4.0 2

2.0 PROPOSED SOFTWARE ARCHITECTURE

2.1 View 1 (ADV 1)

Diagram 1: Architectural Design View (ADV 1)

SYSTEM NAME VERSION PAGE

Rabbit Laundry Delivery Service 4.0 3

2.2 View 2 (ADV 2)

Diagram 2: Architectural Design View (ADV 2)

SYSTEM NAME VERSION PAGE

Rabbit Laundry Delivery Service 4.0 4

2.3 View 3 (ADV 3)

Diagram 3: Architectural Design View (ADV 3)

SYSTEM NAME VERSION PAGE

Rabbit Laundry Delivery Service 4.0 5

SYSTEM NAME VERSION PAGE

Rabbit Laundry Delivery Service 4.0 6

3.0 SUBSYSTEM DECOMPOSITION AND DESIGN GOALS