Software Requirements

Specification

For
Style Sense (AI Based
Wardrobe System)
Version 1.0 approved

Prepared by: Aima Sajjad, Kiran Saba

Submitted to: Miss Iqra Qayyum

University Of Punjab

23-Oct-2025

Copyright © 2024
Software Requirements Specification Page ii

Table of Contents
List of Tables ...........................................................................................................................................iii
List of Figures ..........................................................................................................................................iii
1 Introduction .................................................................................................................................4
1.1 Purpose................................................................................................................................................ 4
1.2 Product scope ...................................................................................................................................... 4
1.3 Intended audience and document overview ........................................................................................ 4
1.4 References........................................................................................................................................... 4
2 Overall description......................................................................................................................4
2.1 Product perspective ............................................................................................................................. 4
2.2 Product function .................................................................................................................................. 4
2.3 User class and characteristics ............................................................................................................. 5
2.4 Operating environment ....................................................................................................................... 5
2.5 Design and implementation constraints .............................................................................................. 5
2.7 User documentation ............................................................................................................................ 5
2.8 Assumptions and Dependencies ......................................................................................................... 6
3 External interface requirements ................................................................................................6
3.1 User interfaces .................................................................................................................................... 6
3.2 Hardware interfaces ............................................................................................................................ 6
3.3 Software interfaces ............................................................................................................................. 6
3.4 Communication interfaces .................................................................................................................. 6
4 System Features ..........................................................................................................................6
4.1 Functional Requirements .................................................................................................................... 6
4.1.1 USECASE MODEL OF CAFÉ MANAGEMENT SYSTEM ...........................................6
4.1.2 Scenarios of Use Case ...........................................................................................................7
4.1.3 Sequence Diagrams .............................................................................................................15
4.1.4 Context Flow Diagram................................................................................................................... 24
4.2 Behavior requirements ...................................................................................................................... 24
4.2.1 Use case view: .............................................................................................................................24
5Other Nonfunctional Requirements .........................................................................................25
5.1 Performance Requirements ............................................................................................................... 25
5.2 Safety and Security Requirements .................................................................................................... 25
6 Other Requirements .................................................................................................................26
Software Requirements Specification Page iii

List of Tables

Table 1: Login System .................................................................................................................... 7

Table 2: Upload Wardrobe Image.................................................................................................. 8
Table 3: Virtual Try-On .................................................................................................................. 8
Table 4: Outfit Suggestion ............................................................................................................. 8
Table 5: Manage Wardrobe ............................................................................................................ 9
Table 6: Schedule Outfit ................................................................................................................. 9
Table 7: Budget and Purchase....................................................................................................... 10
Table 8: Wardrobe Analytics ........................................................................................................ 10
Table 9: Admin Login ................................................................................................................... 10
Table 10: Maintain System ........................................................................................................... 11
Table 11: Generate Reports .......................................................................................................... 11
Table 12: Privacy and Security Settings ....................................................................................... 12

List of Figures

Figure 1: Use case Model ............................................................................................................... 7

Figure 2: App Login Flow ............................................................................................................ 15
Figure 3: Add wardrobe Item Flow .............................................................................................. 15
Figure 4: Outfit Suggestion Flow ................................................................................................. 16
Figure 5: Virtal Try-On Sequence ............................................................................................16
Figure 6: Schedule Outfit Flow..................................................................................................... 17
Figure 7: Weather-Aware Styling Flow .................................................................................... 17
Figure 8: Payment Flow ................................................................................................................ 18
Figure 9: Budget Filter Flow......................................................................................................... 18
Figure 10: Wadrobe Analytics Flow ............................................................................................19
Figure 11: Purchase Recommendation Flow ................................................................................ 19
Figure 12: Data Backup or Expert Flow ....................................................................................... 20
Figure 13: Miantain System .......................................................................................................... 20
Figure 14: Take payment .............................................................................................................. 21
Figure 15: Generate report ............................................................................................................ 21
Figure 16: Check the report ......................................................................................................... 22
Figure 17: Subscription Management ........................................................................................... 22
Figure 18: Privacy Settings ........................................................................................................... 23
Figure 19: System logout .............................................................................................................. 23
Software Requirements Specification Page 4

1 Introduction
1.1 Purpose

The goal of this document is to specify requirements for Style Sense, an AI-based wardrobe
system. It is a product that allows users to digitize their wardrobes, receive outfit suggestions and
perms as well try on any virtual looks. It can also help people plan outfits by event and weather.
Its purpose is to cut down on the time spent by people choosing clothes for themselves and make
each outfit more useful.

1.2 Product scope

Once people have Style Sense, they will be able to build a digital wardrobe, get daily outfit
suggestions, use virtual try-on and be recommended purchases. The system uses computer
vision, machine learning to analyze clothing and user preferences for tags. Its main platform is
mobile; there might also be a web dashboard.

1.3 Intended audience and document overview

This document is written for developers, designers, as well QA and testers. It describes the
functional and nonfunctional requirements required to build STYLE Sense. It also describes the
interfaces that these requirements demand. It is aimed at stakeholders, developers, potential
visitors and their customers.

1.4 References

(Usecase diagrams of custom software, 2018)

1. Usecase diagrams of custom software. (2018). Retrieved from Institute of Electrical and
Electronics Engineers: [Link]

2 Overall description

2.1 Product perspective

STYLE (Sense) is an app with CV and ML modules that is mobile first. It can be coupled to
weather, calendar, and laundromat services. Architecture: Mobile client; Service gateway;
Machine learning services, Database, Admin console.

2.2 Product function

The Style Sense system includes following functionalities:

[Link] a variety of clothes and shoes

[Link] order information: wardrobe advice, etc. (including expenses guide)

[Link] test of looks two or more at once; self (participant)

Software Requirements Specification Page 5

[Link], Time-Aware Dressing changes people — schedule wear, organize events

[Link] recommendation that matches your budget

[Link] operations report

[Link], subscription, and privacy control

[Link] wardrope

2.3 User class and characteristics

Target User: Casual user, Fashion fan, Shopping enthusiast, Power user

2.4 Operating environment

Client: Android 10+ and iOS 14+; Server: Linux container, Restful API

ML model endpoint

2.5 Design and implementation constraints

Privacy as a design since privacy is important to the users. On-device processing wherever
feasible, and hence we do not need to wait on slow net. Fallback and incremental updates
to support model, simply to make things work well when there is no connection.

2.7 User documentation

[Link] app takes an individual through easy help and set-up steps when they first start up.
[Link] videos demonstrate the way to add clothes or to put them on.
[Link] most frequent questions are discussed in an easy web guide and FAQ.
[Link] management and applying updates are also made with the help of the admin
guide.

2.8 Assumptions and Dependencies

[Link] photos are clear the app works improves.

[Link] app needs internet for weather and other trends information.
[Link] internet can affect the working of the app.
[Link] should be enough for images and other data.
Software Requirements Specification Page 6

3 External interface requirements

3.1 User interfaces

Mobile UI: We will take pictures, filter things, open a feed of suggestions, and see a try-on
mirror.
Web UI: Analytics dashboard, bulk upload and an administrator console to control all of it.
Notifications: Push alerts and mail messages to ensure that no one is left behind.

3.2 Hardware interfaces

They shall be logical address of the system in IPv6 format.

3.3 Software interfaces

[Link]-sensitive weather styling (so it can determine whether to pull out a hoodie or a
pair of jeans when going to the campus by bus).

[Link] checkout (provides it with a hassle-free checkout with Spotify and the
campus streaming service).

[Link] partner APIs to look up products (so it does not have to spend users's money
burning budget).

[Link] model that acts as endpoints (to keep sentiment analysis project running on the
cloud).

3.4 Communication interfaces

HTTPS for server communication. OAuth 2.0 for third-party integrations. Webhooks for merchant
events.

4 System Features
System features contains different functional requirements of the system.

4.1 Functional Requirements

Write FR here

4.1.1 USECASE MODEL OF CAFÉ MANAGEMENT SYSTEM

Software Requirements Specification Page 7

system login

order food

chef
check customer's
order

customer
prepare food maintain system

request for
take food
raw material

students faculty payment

debit/credit cash
get discount membership
admin
order raw material

supply raw material

take payment

cashier generate report check the report

supplier
system logout

Figure 1: Use case Model

4.1.2 Scenarios of Use Case

Table 1: System Login

Use case: System Login

Actor: User

Pre-condition: User must be registered in the system.

Normal flow: User enters valid email and password, system verifies credentials
and grants access.

Post-condition: User successfully logs in to the Style Sense system.

Table 2: Upload Wardrobe Image

Use case: Upload Wardrobe Image

Software Requirements Specification Page 8

Actor: User

Pre-condition: User must be logged in.

User uploads clothing images from device or camera to add to

Normal flow:
wardrobe database.

Post-condition: Image successfully uploaded and saved in user wardrobe.

Table 3: Virtual Try-On

Use case: Virtual Try-On

Actor: User

Pre-condition: Wardrobe items must be available in the account.

User selects clothing items to virtually try on using AI-based

Normal flow:
image overlay.

Post-condition: System displays realistic try-on visualization.

Table 4: Outfit Suggestion

Use case: Outfit Suggestion

Actor: User

Pre-condition: User must have uploaded wardrobe items.

System analyzes wardrobe data, color matching, and weather to

Normal flow:
suggest outfit combinations.

Post-condition: Outfit suggestion displayed successfully.

Software Requirements Specification Page 9

Table 5: Manage Wardrobe

Use case: Manage Wardrobe

Actor: User

Pre-condition: User must be logged in.

Normal flow: User views, edits, or deletes wardrobe items.

Post-condition: Wardrobe updated successfully.

Table 6: Schedule Outfit

Use case: Schedule Outfit

Actor: User

Pre-condition: User must have created an outfit or suggestion.

Normal flow: User schedules outfits on calendar for future dates.

Post-condition: Outfit successfully scheduled.

Table 7: Budget and Purchase

Use case: Budget and Purchase

Actor: User

Pre-condition: User must be logged in and set preferences.

Software Requirements Specification Page 10

System shows matching clothing products within user’s budget using

Normal flow:
store APIs.

Post-condition: Purchase suggestions displayed successfully.

Table 8: Wardrobe Analytics

Use case: Wardrobe Analytics

Actor: User

Pre-condition: User must have wardrobe data in the system.

Normal flow: System calculates usage statistics and displays most/least worn outfits.

Post-condition: Analytics report generated successfully.

Table 9: Admin Login

Use case: Admin Login

Actor: Admin

Pre-condition: Admin must be authorized by the system.

Normal flow: Admin enters credentials to access management panel.

Post-condition: Admin successfully logged in.

Table 10: Maintain System

Use case: Maintain System

Actor: Admin
Software Requirements Specification Page 11

Pre-condition: Admin must have full access rights.

Admin updates records, fixes errors, and manages user and item
Normal flow:
data.

Post-condition: System updated and maintained successfully.

Table 11: Generate Reports

Use case: Generate Reports

Actor: Admin

Pre-condition: Admin must be logged in.

Admin generates reports about system usage, uploads, and user

Normal flow:
activity.

Post-condition: Reports successfully generated.

Table 12: Privacy and Security Settings

Use case: Privacy and Security Settings

Actor: User

Pre-condition: User must be logged in.

User updates privacy preferences and manages data-sharing

Normal flow:
permissions.

Post-condition: Privacy settings saved successfully.

Software Requirements Specification Page 12

4.1.3 Sequence Diagrams

Sequence diagrams of café management system are as follows:

Figure 2: cafe system login

forget authenticate
user login page verification database
password page

forget password

login to page check authenticity for access

check login detail

valid login detail provide authentication

check security queries

create session in and
store in database
send email to user to reset password

allow user to accss the page

login successfully

Figure 3: Information of order food

:Chef :Notification_Bar :Check_Stock :Confirmation

ched checks the incoming orders

check stock for current order

check ingredients

cancel order

confirm the order

chef is ready to start the dish

Figure 4: Information of checking the food order

Software Requirements Specification Page 13

:Chef :Notification_Bar :Check_Stock :Confirmation

ched checks the incoming orders

check stock for current order

check ingredients

cancel order

confirm the order

chef is ready to start the dish

Figure 5: Information of prepare the food

:Chef :Ingredients :Cook

grather ingredients

measure ingredients

start to cook

wrong cooked

get ingredient

cook again

Figure 6: Information about taking the food

Software Requirements Specification Page 14

:Customer :Confirmation :Counter :Table

message send to the customer

customer confirms

validate confirmation

check order number

go to counter for take its order

receive the food and receipt

take his seat

Figure 7: Information about the payment

:Cashier/Supplier :GetPayment :Database :ConfirmationMessage

receive payment from customer/admin

payment received

send notification on system successfully

store daily payment record

payment not received

no notification recevied

Figure 8: Debit/credit information

:Cashier/Supplier :ModesOfPayment :GetPayment :Database :ConfirmationMessage

receive payment from customer/admin

check the
payment received
Debit / Credit

send notification on system successfully

store daily payment record

payment not received

no notification recevied
Software Requirements Specification Page 15

Figure 9: Cash information

:Cashier/Supplier :CashPayment :Database :ConfirmationMessage

receive payment from customer/admin

payment received

send notification on system successfully

store daily payment record

payment not received

no notification recevied

Figure 10: Request for raw material

:Chef :Stock :Admin

check stock

missing ingredients

total quantity of ingredient

make a list for

required stock

send a list of required ingredients

Figure 11: Order the raw material

Software Requirements Specification Page 16

:Admin :RawMaterial :System :Supplier

checkout the list that sent by chef

send a order for raw material

received the order for material

give delivery time period to supply

received delievry time limit

Figure 12: Supply raw material

:Supplier :System :DeliveryService

received notification for deadline of delivery

collect all
requied item

send confirmation message to

admin that order is ready

successfully supplied material

deliver to administer
for cafe

Figure 13: Information of maintain the system

Software Requirements Specification Page 17

:Admin :Database :System

lookafter the system

added, edit and update

Figure 14: Take payment

:Cashier/Supplier :GetPayment :Database :ConfirmationMessage

receive payment from customer/admin

payment received

send notification on system successfully

store daily payment record

payment not received

no notification recevied

Figure 15: Generate report

Software Requirements Specification Page 18

cashier report page database

request report

generate report

provide daily sale report

display report

Figure 16: Check the report

:admin :report page :database :confirmation

open report page

cashier sent report

admin check the report

confrim the daily report by admin

Figure 17: Get discount

Software Requirements Specification Page 19

:Student :Discount :Items

student check for discount offer

offer on several items

Get discount

buy items on the base of discount

Figure 18: Information about Membership

:Faculty :MemberShip :Discount :Items

apply for membership

through membership faculty

get discount
offer on various items

get membership

Get discount

buy items on the base of membership & discount

Figure 19: System logout

Software Requirements Specification Page 20

:User database :LogoutPage

logout to page

check security for logout

logout successfully

4.1.4 Context Flow Diagram

Employee

Supplier

CAFÉ
MANAGGEMENT Management
SYSTEM

Café
Services

customer

Figure 20: CFD of Cafe Management System

4.1.5 Activity Diagram

Only one of entire system here

4.1.6 Class Diagram

Only one of entire system here

4.2 Behavior requirements

4.2.1 Use case view:

The use case for each of the actor is described below:
Software Requirements Specification Page 21

User Use Cases

• Use Case: Login/Logout
Description: The user can log in and log out of the system securely. The system authenticates the
user’s credentials before allowing access.

• Use Case: Add Wardrobe Item

Description: The user can upload or add new clothing items to their virtual wardrobe with details
such as type, color, and category.

• Use Case: Virtual Try-On

Description: The user can virtually try on selected outfits using augmented or simulated visuals to
preview combinations.

• Use Case: Request Outfit Suggestion

Description: The user can get personalized outfit recommendations based on their wardrobe, budget,
filters, and external factors like weather.

• Use Case: Schedule Outfit

Description: The user can schedule specific outfits for future dates. The system uses the Calendar API
to manage scheduled events.

• Use Case: Set Budget and Filters

Description: The user can define spending limits and filtering preferences (e.g., color, occasion,
season) to refine outfit suggestions.

• Use Case: Purchase Recommendation

Description: The user can receive recommendations for purchasing new clothing items through
integrated retail APIs.

• Use Case: Wardrobe Analytics

Description: The user can view analytics on clothing usage, trends, and preferences to better manage
their wardrobe.

• Use Case: Manage Subscription

Description: The user can manage their subscription plan, renew it, or upgrade/downgrade using a
secure payment API.

• Use Case: Privacy Settings

Description: The user can update privacy options, control data visibility, and manage sharing
preferences.

Admin Use Cases

• Use Case: Generate Reports
Description: The admin can generate various reports, such as usage statistics, subscription data, and
wardrobe analytics for system monitoring.

• Use Case: Maintain System

Description: The admin is responsible for maintaining system performance, fixing errors, and
ensuring smooth operations and data security.

Data Engineer Use Cases

• Use Case: Train and Update ML Models
Description: The data engineer can train, and update machine learning models used for outfit
recommendations, analytics, and personalization.
Software Requirements Specification Page 22

5 Non-functional Requirements

5.1 Performance Requirements

➢ The product can be deployed either on a local server or a cloud-based one.

➢ The initial load time for the system will be slight, and it will be determined by the size of the
data.

➢ Users' experience will vary according to the network speed and the hardware configuration.

➢ The Payment API will provide security for all the payment transactions.

➢ Two databases will be created for users and admins to facilitate uninterrupted access.

5.2 Safety and Security Requirements

➢ The source code developed for this system shall be maintained in configuration
management tool.
➢ The whole system is secured. Only admin can access all the data.
➢ The system will use HTTPS; because of this protocol this is more secure.
➢ The system will use secured POS system.

6 Other Requirements
Licensing Requirements

Not applicable.

Legal, Copyright and Other Notices

All rights reserved by our team.

Applicable Standards

It should be as per the industry standard