Stichit SRS

COMSATS University Islamabad,
Park Road, Chak Shahzad, Islamabad Pakistan

Department of Computer Science
Software Requirements Specification

For
Stitchit
(An android application)
Version 1.0
By
Abdul Rehman Sohail CU/FA16-BCS-104/ISB
Linta Anmol CU/FA16-BCS-109/ISB
Maida Shaheen CU/FA16-BCS-122/ISB
Supervisor
Mr. Tehseen Riaz Abbasi
Submission Date: 3rd October, 2019
Original Version 1.0
Bachelor of Science in Computer Science (2016-2020)
1
Table of Content
Department of Computer Science 1

1. INTRODUCTION 4
1.1. DOCUMENT PURPOSE 4
1.2. PRODUCT SCOPE 4
1.3. INTENDED AUDIENCE 4
1.4. DEFINITIONS, ACRONYMS AND ABBREVIATIONS 5
2. OVERALL DESCRIPTION 5
2.1. PRODUCT PERSPECTIVE 5
2.2. PRODUCT FUNCTIONS 5
2.3. USER CHARACTERISTICS 5
2.4. OPERATING ENVIRONMENT 6
2.5. GENERAL CONSTRAINTS 6
3. REQUIREMENT ELICITATION TECHNIQUES. 6
4. USE CASES. 6
4.1. USE CASE(S) DIAGRAM: 9
4.2. USE CASE(S): 13
4.1. 3D DRESS PLACEMENT (SURFACE) 45
4.2. 360 DRESS ROTATE 46
4.3. DRESS ZOOM IN 47
4.4. DRESS ZOOM OUT 48
4.5. VIEW AR GUIDE 49
4.6. ADD AR GUIDE 50
4.7. DELETE AR GUIDE 51
6.2. SEND DRESS IMAGES-------------------------------------------------------------------------------------------------- 61
6.3. SEND DRESS MODELS------------------------------------------------------------------------------------------------------- 62
6.4. PLACE A PHONE CALL------------------------------------------------------------------------------------------------------- 63
6.5. RECEIVE TEXT MESSAGE---------------------------------------------------------------------------------------------- 64
6.6. RECEIVE PHONE CALL-------------------------------------------------------------------------------------------------- 65
6.7. RECEIVE DRESS IMAGES---------------------------------------------------------------------------------------------- 66
6.8. RECEIVE DRESS MODELS--------------------------------------------------------------------------------------------------- 67
8.1. RATINGS BASED RECOMMENDATIONS--------------------------------------------------------------------------------72
8.3. VIEW RECOMMENDATIONS----------------------------------------------------------------------------------------- 74
8.4. AGGREGATE RECOMMENDATIONS--------------------------------------------------------------------------------75
9.1. ABOUT APPLICATIONLICATIONLICATION------------------------------------------------------------------------76
9.2. CONTACT US------------------------------------------------------------------------------------------------------------- 77
9.3. FAQS----------------------------------------------------------------------------------------------------------------------- 78
9.4. REPORT PROBLEM----------------------------------------------------------------------------------------------------- 79
9.5. TEXTUAL GUIDELINES------------------------------------------------------------------------------------------------- 80
9.6. USER FEEDBACK--------------------------------------------------------------------------------------------------------- 81
9.7. SUGGESTIONS----------------------------------------------------------------------------------------------------------- 82
9.8. ADMIN RESPONSE------------------------------------------------------------------------------------------------------ 83
5. SPECIFIC REQUIREMENTS 84
4.8. UC-2.3: DRESS CUSTOMIZATION 95
UC-2.10: ADD DRESS MODEL 104
UC-2.13: EDIT DRESS CATEGORY 105
UC-2.14: EDIT DRESS MODEL 106
UC-3.1: FIND TAILOR ON MAP 107
UC-3.6: CANCEL CUSTOMER REQUIREMENTS 111
UC-3.7: EDIT CUSTOMER REQUIREMENTS 112
UC-3.8: VIEW USER ON MAP 112
UC-4.3: DRESS ZOOM OUT 115
UC-4.5: VIEW AR GUIDE 116
UC-4.6: ADD AR GUIDE 117
UC-4.7: DELETE AR GUIDE 117
UC-5.2: VIEW ORDER DETAILS 119
UC-5.3: EDIT ORDER REQUIREMENTS 120
UC-5.4: CANCEL ORDER 120
UC-5.4: RATINGS 121
UC-5.6: CHOOSE COMMENTS 122
UC-5.7: ORDER QUEUE FOR TAILORS 123
6. Non-functional Requirements 144
6.1. Performance Requirements 144
6.1.2. Throughput 144
6.2. Reliability 144
6.3. Design Constraints 144
6.4. Accuracy and Precision 145
6.5. Portability 145
6.6. Security 145
7. GANTT CHART 145
8. CONCLUSION 145
9. REFERENCES 146
10. PLAGIARISM REPORT 146
1. Introduction
The following SRS document will provide the overview of the whole document that includes the
precise details of our product i.e. its features and functionalities, their use cases, its compatibility with hardware
and software on which it will run, and other sources like tools and technology which helps in developing, its
constraints and design, its performance and security and all other basic and miscellaneous functionalities will be
covered for the targeted audience or purpose.
1.1. Document Purpose

The purpose of this SRS document is to specify the basic and non-basic both the functionalities and
requirements of the proposed system. This document gives the detailed overview of what will be the main
features we can use while operating this system. The system works to assist tailors by automating the manual
data handling and the customers to book the tailors online for their desired orders. This document basically
gives an over view of the system that what will be the basic functionalities of the system when the product is
ready, using use cases, mockups and other related details of every atomic part of the proposed system.
Making it easier to examine each and every feature whether it is needed or not.
1.2. Product Scope

Automation is the new trend that makes life easier and comfortable, and with every new technology
created, people are becoming more dependent on these facilities. People rely on their gadgets a lot to solve most
life problems and for that reason this system will help them with stitching of their clothes through the system in
their very own home by saving time and other sources. The users will be able to design the stitching of their
cloth through the application by entering their details of their size, and some other special description if they
want some different thing done on their piece of cloth. This application allows tailors to take orders from
customers and return them within the estimated time. It allows the tailors to work from their shop from home by
just creating their account in application.
● The system we will be designing is a tailoring application which will help both the tailors and the
customer to get their work done by helping them with stitching of their clothes through the
application in their very own home by saving time.
● The user will be able to design the stitching of their cloth through the application by entering the
details of their size.
● This application allows tailors to take orders from customers and return them within the estimated
time.
● The system will help both the tailors and customers to get their work done by making and order from
home, saving their time and effort.
● It will allow a customer/tailor to customize the dresses and also show a customer that how he/she
will look in a certain dress through 3D model to
● Customers will be able to find different tailors for a specific work, within their budget and location.
● It will help a tailor to keep record of all the customers, without keeping a diary to take care of and
reducing stress of manual data handling.
1.3. Intended Audience

The following document can be read by our project teacher, students, developers, tailors and customers.
It will help us in order to know the main function of the proposed system very well and what should be added or
subtracted to make a system ideal. For developers like us, it will assist us to know what should be our priority,
what work should be done before so that the proposed system should be managed in the given time.
1.4. Definitions, Acronyms and Abbreviations
CNIC Computerized National Identity Card

Algorithms A basic idea on which the programs are built
Use case A diagram showing all the features and the actor who uses those features
3D Three dimensions (such as height, width and depth), like any object in the
real world. Example: your body is three-dimensional
NFRs Nonfunctional Requirements define system attributes such as security,
reliability, performance, maintainability, scalability, and usability.
2. Overall Description
People rely on their electronic gadgets a lot to solve most life problems and for that reason this
application will help them with stitching of their clothes through the application in their very own home by
saving time and other sources.
2.1. Product Perspective

This system is the same as some of the tailoring applications but it does have many improved and
different features and the main features of this application includes: Dress customization using 3D
modeling, Book a local tailor online and bringing a platform for tailors to advertise themselves by
maintaining their profile while this application is making their world more organized and reducing the
stress of manual handling of data.
This application will be able to run on android device. The android device must be connected to the internet as
this application works on internet.
2.2. Product Functions

Following are some of the product features:
● Tailors will be able to create their own profiles in which they will be able to provide their designs,
their charges etc.
● Customers will also be able to create their own profiles.
● Customers will be able to view the tailor’s profile.
● It will allow a customer/tailors to customize the dresses according to their likings.
● It will also show a customer that how he/she will look in a certain dress through 3D model.
● It will help a tailor to keep record of all the customers.
● It will help a customer to find different tailors for a specific work, within their budget and location.
2.3. User Characteristics

This system is based on three type of users which are mentioned below:
● Tailors: Tailors will be able to create and manage their own profile. They will be able to take
orders from the customers. They will be able to provide the feedback, report any problem, give any
suggestion, and keep their business record organized through data handling. They will be able to
contact the customers for order purposes. They will also be able to customize the 3D dress models.
● Customers: Customers will also be able to create and manage their own profiles. They will be able
to view the local tailor’s profiles. They will be able to place orders for the tailors and provide the
feedback, report any problems, and give any suggestions. They will be able to contact tailors for
order purposes. They will also be able to customize the 3D dress models for order purposes and can
use the AR feature of this system.
● Admins: Admins will also be able to add, delete and manage the profiles of the customers and the
tailors. They can also respond to the user feedback, they can also update the 3D models.
2.4. Operating Environment

This application will be an android application and will be operate able on any android devices. Also
this application needs an internet connection to work.
2.5. General Constraints

This application will also contain some constraints like, this application will only be functional if the
user has an internet connection. This application will not be able to provide delivery services for the users. This
application will also not be able to provide online payment services.
3. Requirement Elicitation Techniques.

The techniques we used to gather information for this document are:
 Brainstorming
Brainstorming is a method for generating ideas to solve a design problem. We did brainstorming about
our system that how it will work, from where and how the process will start and where it leads.
 Interviews
An interview is a conversation where questions are asked and answers are given. We took interviews of
some tailors and some customers as well in order to have a better understanding of this environment
including its problems so that we can provide a better solution in the form of our system that can provide
ease for both the customers and tailors.
 Observation
Observational research is a type of correlational (i.e., non-experimental) research in which a researcher
observes ongoing behavior. We have some observations about this tailor-customer environment and will
try to solve the problems and accommodate them accordingly.
4. Use Cases.
Following are the use cases of Stitchit:
Module 1: User Profiling

M1-UC1 Sign up
M1-UC2 Sign in
M1-UC3 Forget Password
M1-UC4 Remember me
M1-UC5 View Profile(Customer and Tailor)
M1-UC6 Edit profile(Customer and Tailor)
M1-UC7 Profile Settings
M1-UC8 Delete User
M1-UC9 Add Customer measurements
Module 2: 3D Dress Design
M2-UC1 View dress categories
M2-UC2 View dress models
M2-UC3 3D Dress customization
M2-UC4 Send 3D dress model as order
M2-UC5 Search 3D customize dresses
M2-UC6 Search 3D dress model by filters(colors)
M2-UC7 Add dress category
M2-UC8 Choose 3D dress design
M2-UC9 Textual guide for 3D models
M2-UC10 Add 3D dress models
M2-UC11 Delete dress category
M2-UC12 Delete 3D dress models
M2-UC13 Edit dress category
M2-UC14 Edit 3D dress model
Module 3: Book My Dress

M4-UC1 Find Tailor on Map
M4-UC2 Find Customer on Map
M4-UC3 Customer's Requirement
M4-UC4 Accept Dress Order
M4-UC5 Reject Dress Order
M4-UC6 Cancel Request
M4-UC7 Cancel Customer Requirements
M4-UC8 Edit requirements
M4-UC9 View user on Map
M4-UC10 View Profile(customer and tailor)
Module 4: AR Dress Design

M3-UC1 3D Dress placement(surface)
M3-UC2 360 Dress Rotate
M3-UC3 Dress Zoom in
M3-UC4 Dress Zoom Out
M3-UC5 View AR Guide
M3-UC6 Add AR Guide
M3-UC7 Delete AR Guide
Module 5: Order Details

M5-UC1 Place order
M5-UC2 View order Details
M5-UC3 Edit order requirements
M5-UC4 Cancel Order
M5-UC5 Ratings
M5-UC6 Order History
M5-UC7 Choose Comments
M5-UC8 Order queue for tailors
Module 6: Chat Box
M6-UC1 Send Text message
M6-UC2 Send Dress Images
M6-UC3 Send Dress Models
M6-UC5 Place Phone Call
M6-UC6 Receive Text Messages
M6-UC8 Receive Phone Call
M6-UC9 Receive Dress Images
M6-UC10 Receive Dress Models
Module 7: Notifications
M7-UC1 Add Notification
M7-UC2 Send SMS
M7-UC3 View Notification
M7-UC4 Delete notifications
M7-UC5 Push Notification
Module 8: Service Recommender

M8-UC1 Rating Based Recommender(search)
M8-UC2 Budget Based Recommender(search)
M8-UC3 View Recommendations
M8-UC4 Aggregate Recommender
Module 9: Help and Support

M9-UC1 About Application
M-9UC2 Contact Us
M9-UC3 View FAQs
M9-UC4 Report A Problem
M9-UC5 Textual Guidelines
M9-UC6 User Feedback
M9-UC7 Suggestions
M9-UC8 Admin response
4.1. Use Case(s) Diagram:
Following are the use case Diagram of Stitchit
Book My Dress
Customer requirements
User Profiling
Sign up Accept Dress Order
Sign in Reject Dress Order
Forget pd Edit requirement

asswor
Remember
meView profile
View Profile
Tailor Notifications
Edit profile
View notification
Settings
Delete notification
Figure 4.1.1: Tailor Use Case Diagram(1/3)
3D Dress Design
Order Details View Dress Category
View Order Details
Cancel View Dress Models
order
Dress Customization
Edit order
Choose Dress
Ratings Design
Order History 3D Dress Guide
Order Search customized Dresses
Queue Tailor Search by Filters
Choose
Comments
Figure 4.1.2: Tailor Use Case Diagram (2/3)

Chat Box
Send Text Message
Help and Support
Send Dress Images About Application
Send Dress Models

Contact Us
Place Phone
CallView FAQs
Report a Problem
Receive Text Textual
Receive Guidelines
Audio Call
Receive Dress Tailor User
edba
Feck
Images
Receive Dress Models Suggestions
Figure 4.1.3: Tailor Use Case Diagram (3/3)
View Dress
Categories Sign Up
View Dress
Models Sign in
Dress
omiza
Custtion
Edit Profile
Send Order forget pasword
Search Remember Me
ustomize
Cd Dresses
Search DressSetting
Model By filters
CustomerView Profile
Choose Dress Design
Logout
Text 3D Dress guide
3D Dress Models User profiling
Figure 4.1.4: Customer Use Case Diagram (1/4)

Chat Box
Send Text message Place Phone Order Details
Call
Place Video Call Place Dress Order
Send Dress Model Send Dress Images
Receive Phone Call View Order Details
Cancel order
Order History
Receive Video Ratings

Call Customer
Receive Text message
Receive Dress Model Edit Order
Receive Dress Model Requirements
choose comments
Book My Dress
Find Tailor on Map
Cancel request
AR Dress Design
3DModelPlacement
Edit Requirement
360 Dress Rotate
ViewTailor on
map Zoom Out
ViewTailor Profile Zoom In
Customer Requirments
Customer AR guide

Help And Support
About
Service Recommender application
Rating Based Recommender
Contact us View FAQ's
Budget Based Recommender Suggestion
View Recommendation s
Notifications Report a problem

View notification
Textual guide line
Delete notification Customer
User FeedBack
User Profiling AR Dress Design

Delete User
Add AR guide
View AR guide
3D Dress Design
Add Dress Category Delete AR guide
View Dress Category
Delete Dress Category
Add Dress
Model Help & Support Contact us FAQs
View Dress Model Admin
Delete Dress Administrator Response
Model
Figure 4.1.8: Admin Use Case Diagram(1/1)

4.2. Use Case(s):
Following are the use case tables of all the modules of Stitchit.
Module 1: User Management

Below are the uses cases for User Management.
1.1. Sign up
Use Case ID: UC-1.1

Use Case Name: Sign Up
Actors: Customer, Tailor
Description: This use case will help a customer and tailor to create their account to use this
application
Level: High
Trigger: The user will click on sign up button
Preconditions: 1. The user must download the application
2. There must be an email id of the user
Includes: None
Normal Flow: 1. First the user will download the application
2. User will open the application
3. A window will be displayed with two options i.e. sign up or sign in
4. User will select sign up button
5. A window will be displayed containing the form to be filled by user in
order to sign up for the account
Alternative None
Flows:
Exceptions: 1. Input is invalid
2. A message will be displayed beside the input field to enter valid
credentials
3. The user re-enters the input for that specific field
Post conditions: 1. User profile will be created once user filled the sign up form and submit it
Special None
Requirements:
Assumptions: 1. The user must provide the details eligible for that specific field which
Notes and 1. The user must provide the valid requirements and he cannot create an email
Issues: with associated with the applicationlication. Email Id must be created
before creating the account on this applicationlication
1.2. Sign in
Use Case ID: UC-1.2

Use Case Name: Sign In
Description: The user will be able to log into his account once his id is created, by entering the
email address and password he provided while creating his account.
Level: High
Trigger: User will click sign in button
Preconditions: 1. The application must be downloaded
2. The account must be created
Includes: UC: 1.1, 1.2

Normal Flow: 1. User will Open the application
2. User will click on sign in button
3. User will enter his email and password
4. User will log into his account
Alternative None
Flows:
Exceptions: 1. Sign in failed
2. System will display a message of invalid email or password
3. User will enter the valid email and password
4. User will log into his account
Post conditions: 1. User will be able to log into his account
Special None
Requirements:
Assumptions: 1. The user must remember the right email and password to log into his
account
Notes and 1. The user must enter a valid email and password to avoid any issues
Issues:
1.3. Forget Password
Use Case ID: UC-1.3

Use Case Name: Forget Password
Description: The user can log into his account even if he forgets his password by clicking
forgot password which will send an email with a pin code and that will let a user
to create new password
Level: High
Trigger: User will click on Forget password button
Preconditions: 1. The account must be created
2. The user must provide the valid email
Includes: UC: 1.1, 1.2, 1.3
Normal Flow: 1. The user opens the application
2. Sign in window will be displayed
3. The user enter email and password
4. System will prompt the user if the provided email and password doesn’t
match with the email and password provided by the user while creating
his account
5. User will click on forget password
6. An email will be sent to the user by the system containing the PIN
7. A new window will be displayed with the space to enter PIN
8. User will enter the PIN
9. A new window will be displayed with to create a new password and
confirm password fields
10. User will enter the new password and confirm it
Alternative None
Flows:
Exceptions: 1. Invalid email
2. System will prompt a message to enter valid email address
3. User will enter a valid email address
4. A PIN will be generated to through that email provided
5. A new window will be displayed with a field to enter PIN \
6. User will enter PIN
Post conditions: 1. A new Password will be created to log into user’s account
Special None
Requirements:
Assumptions: 1. User must remember his valid email in order to remove further issues
Notes and 1. The email provided by the user must be valid else the new password
Issues: cannot be generated
1.4. Remember me
Use Case ID: UC-1.4

Use Case Name: Remember me
Description: This use case will help a user by not letting him enter his email and password
every time he opens the application. System will do this for user
Level: Medium
Trigger: When the user click remember me button
Includes: UC: 1.1,1.2,1.3
Normal Flow: 1. User opens the application
2. Sign in window will be displayed
3. User enters his valid email and password
4. System will prompt a dialog box of remember me
5. User will on click remember me button
6. User email and password will be saved by the system
Alternative None
Flows:
Exceptions: None
Post conditions: 1. User’s email and password will be saved by the system
Special None
Requirements:
Assumptions: None
Notes and 1. The user must enter a valid email and password
Issues:
1.5. View profile
Use Case ID: 1.5

Use Case Name: View profile
Description: The customer and tailor will be able to see their profile
Level: High
Trigger: When the customer or tailor clicks on profile button
Preconditions: 1. The profile must be created
Includes: UC: 1.1, 1.2
2. User clicks the main menu
3. User clicks on profile
4. The profile will be displayed
Alternative None
Flows:
Exceptions: None
Post conditions: 1. The profile will be successfully displayed
Special None
Requirements:
Assumptions: None
Notes and None
Issues:
1.6. Edit profile
Use Case ID: 1.6

Use Case Name: Edit profile
Actors: Customers, tailors
Description: The tailors and customers can easily edit their profile later after creating their
account to make changes or update their profile information
Level: Medium
Trigger: When the user clicks on edit profile button in the profile
Preconditions: 1. Profile must be created
Includes: UC: 1.1, 1.2, 1.5
2. User clicks on profile from the side menu of their profile
3. User’s profile will be displayed
4. User will click on edit profile
5. A new window will be displayed with editing options
Alternative None
Flows:
Exceptions: 1. Input is invalid
2. A message will be displayed beside the input field to enter valid
credentials
3. The user re-enters the input for that specific field
Post conditions: 1. The user will be able to edit his profile successfully
Special None
Requirements:
Assumptions: 1. The tailor should know how to use application
2. The tailor should know English language
Notes and 1. The user must enter valid input for that specific field.
Issues:
1.7. Profile setting
Use Case ID: 1.7

Use Case Name: Profile setting
Description: The tailor and customer will be able to change the settings of their profile
Level: Medium
Trigger: When the user clicks the profile setting button in their profile
Includes: UC: 1.1,1.2,1.5
2. User clicks on profile from the side menu of their profile
3. User’s profile will be displayed
4. User will click on edit profile
5. A new window will be displayed with editing options
Alternative None
Flows:
Exceptions: None
Post conditions: 1. The user will be able to successfully change the setting of their profile i.e.
language, font.
Special None
Requirements:
Assumptions: 1. The user should know how to use application
2. The user should know English language
Notes and None
Issues:
1.8. Delete User
Use Case ID: 1.8

Use Case Name: Delete User
Actors: Admin
Description: The admin can delete a user (tailor or customer) on the basis of their id
status(not used for months) and reputation(Bad ratings)
Level: High
Trigger: When the admin clicks delete user button
2. Admin should be log in
3. Warning will be sent to user by admin
Includes: UC: 1.1
Normal Flow: 1. The admin clicks on user profile
2. The admin clicks on delete profile
3. The profile will be deleted
Alternative None
Flows:
Exceptions: None
Post conditions: 1. The profile will be deleted of the customer and the tailor
Special None
Requirements:
Assumptions: 1. The admin must confirm the id is no more in use or deleted for valid
reasons
Notes and None
Issues:
1.9. Add customer’s measurements
Use Case ID: 1.9

Use Case Name: Add customer’s measurements
Actors: Customer, tailor
Description: The customer will be able to add his or her requirements
Level: High
Trigger: When the user clicks on add measurements button
Preconditions: 1. The profile must be created
Includes: UC:1.1, 1.2, 1.5
Normal Flow: 1.
Customer opens the application
2.
Customer clicks on sign up
3.
Customer fills the sign up form
4.
Customer will click on add measurements on the same page
5.
A window will be displayed with measurements to be filled
6.
Customer fill the form and submit it
Alternative 1.
Customer opens the profile
Flows: 2.
Customer clicks on profile from the side menu
3.
Customer will click on edit profile
4.
A window will be displayed with editing option of profile with an option
of adding measurements
5. Customer will clicks on add measurements
6. A window will be displayed to add one’s measurements
7. Customer adds his measurements
8. Customer clicks on submit
Alternative 1. Tailor opens his profile
Flows: 2. Tailor clicks on search bar
3. Tailor enters customer’s name
4. Tailor clicks on customer’ name
5. Customer’s profile will be displayed
6. Tailor clicks on add customer’s measurement
7. A page will be displayed to add one’s measurements
8. Tailor adds customer’s measurements
9. Tailor clicks on submit
Exceptions: 1. Incomplete form
2. System will prompt a message to add all measurements” complete the
form”
3. User enters input in all the fields
4. User clicks on submit
Post conditions: 1. Customer’s measurements will be added successfully
Special None
Requirements:
2. The tailor should know English language
Notes and None
Issues:
2. Module : 3D Dress Design
Below are the uses cases for 3D Dress Design
2.1. View Dress Categories
Use Case ID: UC-2.1

Use Case Name: View Dress Categories
Actors: Customer
Description: Customer will have the option to select category of dresses
Level: High
Trigger: User select dress categories option
Preconditions: 1. User must have an account
2. User must be Sign in
Includes: UC-1.2
Normal Flow: 1. User will select the gallery from main menu.
2. User select dress categories option.
Alternative 1. User will select the gallery from Side Menu.
Flows: 2. User then select dress categories option.
Exceptions: N/A
Post conditions: 1. User will be able to view the different dress categories
Special N/A
Requirements:
Assumptions: 1. User have the knowledge of using application
2. User knows how to open gallery
3. User should know how to open side menu
Notes and
Issues: N/A
2.2. View Dress Models
Use Case ID: UC-2.2

Use Case Name: View Dress Models
Actors: Customer ,Tailor s
Description: This will allow user to see the 3D view of the dresses.
Level: High
Trigger: User will click on Dress Models option.
Preconditions: 1. User must be sign in
2. There must be some model to select from gallery
Includes: UC-1.2, UC-2.1
2. User then select a specific category that he wants to see.
3. User select the Dress Model
Flows: 2. User then select a specific category that he wants to see.
3. User select the Dress Model.
Exceptions: N/A
Post conditions: 1. 3D view of dresses will be shown.
Special N/A
Requirements:
2. User knows how to select gallery form main menu and side menu
Notes and
Issues: N/A
2.3. Dress Customization
Use Case ID: UC-2.3

Use Case Name: Dress Customization
Actors: Customer ,Tailor s
Description: This will allow user to Customize the 3D Dress model.

Level: High
Trigger: User click on Customize button.
Preconditions: 1. User must sign in.
2. User should have selected the Dress Model
Includes: UC-1.2, UC-2.1, UC-2.2
4. User click the customize button.
4. User clicks the customize button.
Exceptions: N/A
Post conditions: 1. User can customize the 3D dress model according to his/her desire.
Special N/A
Requirements:
Assumptions: 1. User should know how to select 3D dress model from gallery.
2. User should know how to customize the 3D model
Notes and
Issues: N/A.
2.4. Send 3D dress model as order
Use Case ID: UC-2.4

Use Case Name: Send dress model as order
Actors: Customer s
Description: User will have the option to send customized dress as Order.
Level: High
Trigger: User will click on send as order button.
2. User should have selected the 3D Dress Model
Includes: UC-1.2, UC-2.1, UC-2.2, UC-2.3
4. User will click on Send as Order button to send the 3D dress model for
order
Alternative 1. User will select the gallery from Side Menu

4. User will click on the Send as Order button to send the model for order
Exceptions: N/A
Post conditions: 1. The 3D model of the dress will be send to the tailor.
Special None.
Requirements:
Assumptions: 1. User have the knowledge of using application.
2. User knows how to select gallery form main menu and side menu.
Notes and
Issues: None.
2.5. Search Customize 3D Dresses
Use Case ID: UC-2.5

Use Case Name: Search customize 3D Dresses
Actors: Customer s
Description: User will have the option to search customize 3D design that he saved.
Level: Medium
Trigger: User will click on Search Button
2. User Selected the gallery
3. User have saved customized dress before search
3. User click on the search button.
Alternative 1. User will select the Search customize dress from the side menu.
Flows: 2. User then click on search button.
Exceptions: N/A
Post conditions: 1. Saved customized 3D dress model will be shown.
Special User must be connected to internet
Requirements:
2. User knows how to select Search option form Side menu and from
gallery
Notes and
Issues: None.
2.6. Search 3D dress model by filters
Use Case ID: UC-2.6

Use Case Name: Search 3D dress models by filters
Actors: Customer s
Description: User will have the option to search the dress model in the gallery by filters
Level: Medium
Trigger: User click on search 3D dress by filter button.
Preconditions: 1. User Selected the gallery
2. User have selected the category
3. User click on the search by filter (color) button.
Alternative N/A
Flows:
Exceptions: N/A
Post conditions: 1. User will be able applicationly filter of different color.
Special N/A
Requirements:
Assumptions: 1. User should have the knowledge of using application
2. User should know how to select Search option form Side menu and from
gallery
3. User should know how to search with filters
Notes and
Issues: N/A
2.7. Add dress category
Use Case ID: UC-2.7

Use Case Name: Add dress category
Actors: Admin s
Description: User will be able to add new dress categories

Level: High
Trigger: User click on add dress category button.
2. User selected the gallery
Includes: UC-1.2,
Normal Flow: 1. User select the gallery
2. User click on add new categories button
Alternative N/A
Flows:
Exceptions: 1. If the category exist with the same name
2. Message displayed in front of name option “Category already exist with
the same name”.
3. User enter name again
4. User click on add category button.
Post conditions: 1. User will provide the information about the categories.
Special N/A
Requirements:
Assumptions: N/A
Notes and
Issues: N/A
2.8. Choose 3D Dress Design
Use Case ID: UC-2.8

Use Case Name: Choose 3D Dress Design
Actors: Customer s asss
Description: User will able to select the 3D dress design.

Level: High
Trigger: User click on 3D dress model option.
Preconditions: 1. User must have selected the gallery
2. User must have selected the Category
Includes: UC-1.2, UC-2.1, UC-2.2,
2. User then select a specific category that he want to view.
3. User select the 3D Dress Model by clicking on it.
Alternative N/A
Flows:
Exceptions: N/A
Post conditions: 1. 3D dress model will be shown to the screen of the user
Special None.
Requirements:
Assumptions: 1. User should have knowledge of using application
2. User should know the basic English
Notes and
Issues: None.
2.9. Textual guide for 3D model
Use Case ID: UC-2.9

Use Case Name: Textual guide for 3D model
Actors: Customer , tailor
Description: User will get the guide about how to customize the 3D design
Level: High
Trigger: User will select 3D textual guide option.
Preconditions: 1. User must be sign in.
2. User must have selected the gallery
Includes: UC-1.2, UC-2.1,
2. User select the 3D textual guide option
Alternative N/A
Flows:
Exceptions: N/A
Post conditions: 1. Textual guide for 3D model will be open.
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:
2.10. Add Dress Model
Use Case ID: UC-2.10

Use Case Name: Add 3D Dress Model
Actors: Admin
Description: User will be able to add the model of new dresses in the gallery
Level: High
Trigger: User will click on add 3D dress model button.
3. User must have selected the category
Includes: UC-1.2
2. User select the category
3. User click on add 3D Dress model button
Alternative N/A
Flows:
Exceptions: N/A
Post conditions: 1. New model will be added to the categories
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:
2.11. Delete Dress Category

Use Case Name: Delete Dress Category
Actors: Admin
Description: User will be able to Delete the Category of dresses from the gallery
Level: High
Trigger: User will click on delete dress category button.
Includes: UC-1.2
3. User click on Delete Dress Category button.
Alternative 1. User will select the gallery from side menu.
Flows: 2. User select the category
3. User click on Delete Dress Category button.
Exceptions: N/A
Post conditions: 1. Dress category will be deleted from the gallery.
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:
2.12. Delete 3D Dress Model

Use Case Name: Delete 3D Dress Model
Actors: Admin
Description: User will be able to Delete the 3D model of dresses from the gallery
Level: High
Trigger: User will click on Delete 3D model button.
3. User must have selected the Dress model
Includes: UC-1.2
4. User click on Delete Dress model
Alternative N/A
Flows:
Exceptions: N/A
Post conditions: 1. 3D models of dress will be deleted from the category.
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:
2.13. Edit Dress Category

Use Case Name: Edit Dress Category
Actors: Admin
Description: User will be able to edit the Category of dresses from the gallery
Level: High
Trigger: User will select edit dress category option.
Includes: UC-1.2
3. User click on edit dress category option
3. User click on edit dress category
Exceptions: N/A
post conditions: 1. User will be able to edit the dress categories.
Special N/A
Requirements:
Assumptions: N/A
Notes and
Issues: N/A
2.14. Edit 3D Dress Model

Use Case Name: Edit Dress Model
Actors: Admin
Description: User will be able to edit 3D dresses model from the gallery
Level: High
Trigger: User will click on edit 3D model button.
3. User must have selected the model
Includes: None
3. User will select the model to edit
4. User will click on edit 3D model button.
3. User will select the model
4. User will click on edit 3D model button
Exceptions: N/A
post conditions: 1. User will be able to edit the 3D dress model.
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:
Below are the uses cases for Book My Dress
3.1. Find tailor on map

Use Case ID: UC-3.1
Use Case Name: Find tailor on map
Actors: Customer
Description: This use case will allow a customer to find a tailor on a map according to their
requirements i.e. location, budget.
Level: High
Trigger: When the user clicks on find tailor button
Preconditions: 1. The location must be turned on of the customer’s phone
Includes: UC-1.2
Normal Flow: 1. Customer open the application
2. A window will be displayed which contains the button “find tailor”
3. Customer will click the button “Find tailor”
4. A map will be displayed with the tailor’s shops highlighted on the map
5. Customer will select a tailor
Alternative None
Flows:
Exceptions: 1. Location access denied
2. Customer will go to his phone settings to enable his location
3. Customer will open the application again
4. Customer will click the button “Find tailor”
5. A map will be displayed with the tailor’s shops highlighted on the map
6. Customer will select a tailor
Post conditions: 1. Customer will be able to select tailor
Special None
Requirements:
Assumptions: 1. The customer should know how to use application
2. The customer should know how to use maps
Notes and 1. The location of the user must be enabled
Issues:
3.2.Customer’s requirement
Use Case ID: UC-3.2

Use Case Name: Customer’s requirement
Actors: Customer
Description: It will allow a customer to upload the requirements of a particular dress he
wants to get stitched
Level: Medium
Trigger: When the customer clicks on add requirements option
Includes: UC-1.2
Normal Flow: 1. Customer opens the application
2. A window will be displayed with two options i.e. Signup or sign in
3. Customer clicks on sign in
4. Customer will click on settings
5. Customer will click on edit profile
6. Customer will update the field of customer’s requirements
Alternative None
Flows:
Exceptions: None
Post conditions: 1. Customer will be able to upload and update his requirements for a specific
dress or specific kind of work
Special None
Requirements:
Assumptions: 1. The customer should know how to use application
2. The customer should be able to read and understand English language
Notes and 1. The customer should upload the requirements that can be easily
Issues: understood by the tailor
3.3.Accept dress order
Use Case ID: UC-3.3

Use Case Name: Accept dress order
Actors: Tailor
Description: When the customer sends request to tailor for the stitching of cloths, the tailor can
then accept or reject the request.
Level: High
Trigger: When the customer sends requests, tailor will click the accept button
Preconditions: 1. The customer must send the request in order for the tailor to accept the
request
Includes: UC-1.2
Normal Flow: 1. Customer sends request to tailor
2. Tailor opens the request
3. Tailor will see his request
4. Tailor have now two options i.e. accept or reject
5. Tailor will click on accept order
Alternative None
Flows:
Exceptions: 1. Request cannot be sent
2. System will prompt a message to check internet connection
3. Customer will check the internet connection
4. Customer will resend the request to tailor
5. Request sent.
Post conditions: 1. The order of the customer will be accepted by the tailor
Special None
Requirements:
2. The user must know the basics of English language
Notes and 1. The customer must enter the valid requirements that should be easily
3.4.Reject dress order
Use Case ID: UC-3.4

Use Case Name: Reject dress order
Actors: Tailor
Description: When the customer sends request to tailor for the stitching of cloths, the tailor can
then accept or reject the request
Level: High
Trigger: When the customer sends requests, tailor will click the reject button.
Preconditions: 1. The customer must send the request in order for the tailor to reject the
request
Includes: UC-1.2
Normal Flow: 1. Customer sends request to tailor
2. Tailor opens the request
3. Tailor will see his request
4. Tailor have now two options i.e. accept or reject
5. Tailor will click on reject order
Alternative None
Flows:
Exceptions: 1. Request cannot be sent
2. System will prompt a message to check internet connection
3. Customer will check the internet connection
4. Customer will resend the request to tailor
5. Request sent.
Post conditions: 1. The order of the customer will be rejected by the tailor
Special None
Requirements:
Notes and 1. The customer must enter the valid requirements that should be easily
3.5.Cancel Order
Use Case ID: UC-3.6

Use Case Name: Cancel order
Actors: Customer
Description: Customer will be able to cancel the order after he have made it due to any
reason
Level: High
Trigger: When the customer clicks the cancel button of the order he made before
Preconditions: 1. The order must be made before
Includes: UC-1.2
Normal Flow: 1. Customer opens his profile
2. Customer make an order/request to the tailor
3. Tailor didn’t accept the order
4. Customer cancels the request
Alternative None
Flows:
Exceptions: None
Post conditions: The request will be cancelled successfully
Special None
Requirements:
Notes and 1. The customer can only cancel a request when he have made one before
Issues:
3.6.Cancel customer’s requirements
Use Case ID: UC-3.6

Use Case Name: Cancel customer’s requirements
Actors: Customer
Description: Customer will be able to cancel the requirements he uploaded
Level: High
Trigger: When the customer will click the cancel button.
Preconditions: 1. Customer must have uploaded the requirements
Includes: UC-3.2
2. Customer clicks on add requirements
3. Customers adds requirements
4. Customer will click on cancel requirements
5. The requirements will be removed
Alternative None
Flows:
Exceptions: None
Post conditions: 1. The user will be able to remove the requirements successfully
Special None
Requirements:
Notes and 1. The customer can only cancel a request when he have made one before
Issues:
3.7.Edit customer’s requirements
Use Case ID: UC-3.7

Use Case Name: Edit customer’s requirements
Actors: Customer
Description: It will let a customer to make changes in a requirements he uploaded before
Level: Medium
Trigger: When the customer clicks on edit requirements
Preconditions: 1. The requirements must be added first
Includes: UC-3.2
2. Customer clicks on add requirements
3. Customers adds requirements
4. Customer will click on edit requirements
5. The requirements will be edited
Alternative None
Flows:
Exceptions: None
Post conditions: 1. User will be able edit the requirements successfully
Special None
Requirements:
Notes and 1. The customer can only edit a requirement when he have made one before
Issues:
3.8. View tailor on map
Use Case ID: UC-3.8

Use Case Name: View tailor on map
Actors: Customers
Description: The customer will be able to view tailors on map
Level: Medium
Trigger: When the customer will click on view map button
Preconditions: 1. The location of cell phone must be enabled
Includes: UC-3.1
Normal Flow: 1. Customer clicks on view map
2. A window will be displayed with a map on it
Alternative None
Flows:
Exceptions: 1. Location access denied
2. Customer will go to his phone settings to enable his location
3. Customer will open the application again
4. Customer will click the button “view map”
5. A map will be displayed
Post conditions: 1. Customer and tailor will be able to view map
Special None
Requirements:
2. The user should know how to use maps
Notes and 1. The location of the user must be enabled
Issues:
3.9.View profile (Customer & Tailor)
Use Case ID: UC-3.9

Use Case Name: View profile
Description: The customer will be able to view tailor’s profile and the tailor will also be able
to view customer’s profile which are public
Level: High
Trigger: When the customer or tailor clicks view profile
2. Tailor’s profile must not be private
Includes: UC-1.2
Normal Flow: 1. Customer opens the application
2. Customer search for tailors
3. Customer click on a view tailors profile
4. Tailors profile will be displayed
5. Same for the customers
Alternative None
Flows:
Exceptions: None
Post conditions: 1. The tailor and customer will be able to view profiles
Below are the uses cases for AR Dress Design
4.1. 3D Dress Placement (surface)

Use Case ID: UC-4.1
Use Case Name: 3D Dress Placement (surface)
Actors: Customer
Description: User will be able to detect the surface by his/her mobile camera.
Level: High
Trigger: User click on detect Surface button.
2. User must have selected the dress categories.
3. User must have selected the 3D Dress Model
Includes: UC-2.1, UC-2.2,
2. User then select the Dress Category
4. User click on detect surface button.
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. User will be able to detect the surface for the placement of the 3D model.
Special N/A
Requirements:
2. User should know how to select gallery
3. User should know how to hold the phone while detecting surface.
Notes and
Issues: N/A
4.2.360 Dress Rotate
Use Case ID: UC-4.2

Use Case Name: 360 Dress Rotate
Actors: Customer
Description: User will be able to rotate the dress model in 360 degree
Level: High
Trigger: User select Rotate option
2. User must have selected the Dress Model
3. User must have detected the surface
Normal Flow: 1. User place the augmented model on detected surface.
2. User click on rotate option.
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. User can check the complete view of model by rotating it in 360
degree.
Special N/A
Requirements:
3. User should know how to select model from gallery
4. User should know how to hold phone while placing augmented
model
Notes and
Issues: None.
4.3.Dress Zoom in
Use Case ID: UC-4.3

Use Case Name: Dress Zoom in
Actors: Customer
Description: User will be able to Zoom in on the Dress
Level: High
Trigger: User select Zoom in button
Preconditions: 1. User have placed the augmented dress model
Includes: UC-2.1, UC-2.2, UC-3.1, UC-4.1
Normal Flow: 1. User select the 3D dress model to place in augmented reality.
2. User detect the surface.
3. User click on zoom in button
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. User will be able to view the details by zooming in on the 3D dress
model in augmented reality
Special N/A
Requirements:
model
Notes and
Issues: None.
4.4.Dress Zoom Out
Use Case ID: UC-4.4

Use Case Name: Dress Zoom Out
Actors: Customer
Description: User will be able to Zoom Out on the Dress
Level: High
Trigger: User will select the zoom out button.
Preconditions: 1. User have placed the augmented dress model
Normal Flow: 1. User select the 3D dress model to place in augmented reality.
2. User detect the surface.
3. User click on zoom in button
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. User can view complete 3D Dress model by zooming out

Special N/A
Requirements:
model
Notes and
Issues: N/A
4.5.View AR guide
Use Case ID: UC-4.5

Use Case Name: View AR guide
Actors: Customer
Description: User will be guided how to use augmented reality
Level: High
Trigger: User select the AR guide option
2. User will select the AR guide option
Flows: 2. User will select the AR guide option
Exceptions: N/A
Postconditions: 1. Textual AR guide will be open for the user.

Special N/A
Requirements:
3. User should know how to select the AR guide
Notes and
Issues: N/A
4.6.Add AR guide
Use Case ID: UC-4.6

Use Case Name: Add AR guide
Actors: Admin
Description: User will be able to add new guide of AR
Level: Medium
Trigger: User will select the add AR guide button.
Preconditions: 1. User must be in gallery.
2. User must select the AR option
2. User will select the AR option
3. User will click on add AR guide button.
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. New guide will be added to the AR menu

Special N/A
Requirements:
3. User should know how to add new AR guide
Notes and N/A
Issues:
4.7.Delete AR guide
Use Case ID: UC-4.7

Use Case Name: Delete AR guide
Actors: Admin
Description: User will be able to Delete AR guide from the AR menu
Level: Medium
Trigger: User will select the Delete AR guide button.
2. User must have selected the AR guide
2. User will select the AR option
3. User will select the AR guide
4. User click on Delete AR guide button
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. The AR guide will be deleted from the gallery.
Special N/A
Requirements:
Assumptions: N/A
Notes and
Issues: N/A
Below are the uses cases for Oder Details
5.1.Place Dress Order
Use Case ID: UC-5.1

Use Case Name: Place Dress Order
Description: It will allow user to place the order of his/her dress.
Level: High
Trigger: User will click on place order button.
Preconditions: 1. User must have a account
Includes: UC-1.1,
Normal Flow: 1. User will sign in.
2. User will click on place order button.
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. user will be able to place the dress order
Special N/A
Requirements:
Assumptions: N/A
Notes and
Issues: N/A
5.2. View Order details
Use Case ID: UC-5.2

Use Case Name: View Order Details
Description: It will allow user to view the order details that he/she accepted/placed.
Level: Medium
Trigger: User click on view details button.
Preconditions: 1. User must have account
2. User select the Tailor for order
3. User Send the Order
4. Order accepted by the user
Includes: UC-1.1, UC-3.1,UC-5.1
Normal Flow: 1. User select the Order from order list
2. User click on the order details button.
Alternative 1. User will sign in
Flows: 2. User will select order list from the side menu
3. User will select the order
Exceptions: N/A
Postconditions: 1. User can see the order details
Special N/A
Requirements:
Assumptions: N/A
Notes and
Issues: N/A
5.3.Edit Order requirements
Use Case ID: UC-5.3

Use Case Name: Edit Order requirements
Actors: Customer
Description: It will allow user to edit the order requirements that he/she send for the order
Level: High
Trigger: User will Select the Edit Order option
Preconditions: 1. User must have account
2. User must have placed the order
Includes: UC-1.1, UC-4.1,UC-5.1
Normal Flow: 1. User Select the Order
2. User select the edit option
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. User will add new requirement and edit old requirement for the
order
Special N/A
Requirements:
2. User should know the basic English.
Notes and N/A
Issues:
5.4.Cancel Order
Use Case ID: UC-5.4

Use Case Name: Cancel Order
Actors: Tailor
Description: It will allow user to cancel the order that he/she accept
Level: High
Trigger: User will click on cancel button
Preconditions: 1. User must be sing in
2. Customer must have send the request order to tailor
Includes: UC-1.1,
Normal Flow: 1. User will get the order request from customer.
2. User will select order.
3. User will click on cancel button
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. It will cancel the selected order
Special None.
Requirements:
2. User should know how to select the order from order details
Notes and
Issues: None.
5.5.Rating
Use Case ID: UC-5.5

Use Case Name: Rating
Actors: Customer , Tailor
Description: User can rate the work of other user
Level: Medium
Trigger: User will click on rating button.
2. User get order
3. Order must be completed
Includes: UC-1.1,UC-4.5,UC-5.1,UC-5.2
Normal Flow: 1. User will select the Order details
2. User will select the completed Order
3. User will select the rating option
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. Rating stars will be visible to the user
Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:
5.6.Order History
Use Case ID: UC-5.6

Use Case Name: Order History
Description: It will allow user to view the history of orders that he/she completed.
Level: Medium
Trigger: User will click on history button.
2. User must completed one or more Order
Includes: UC-1.1,UC-4.5
Normal Flow: 1. User will select Order Details
2. User will select Order History
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. List of completed order will be displayed.
Special N/A
Requirements:
Assumptions: 1. User must have the knowledge of using application
2. User Should know how to select side menu
3. User should know how to select order details
Notes and
Issues: N/A
5.7.Choose comments
Use Case ID: UC-5.7

Use Case Name: Choose Comments
Actors: Customer
Description: It will allow user to select the comment for the tailor which describe how was
the work that he does
Level: Medium
Trigger: User will select comment option
2. Order must be completed
3. User must selected the star rating first
Includes: UC-1.1,UC-4.5,UC-5.1,UC-5.2
Normal Flow: 1. User will select the Order details
2. User will select the completed Order
3. User will select the rating option
4. User will select the comments option.
Alternative N/A
Flows:
Exceptions: N/A
Postconditions: 1. Comments will be select.

Special N/A
Requirements:
Assumptions: N/A
Notes and N/A
Issues:
5.8.Order Queue for tailor
Use Case ID: UC-5.8

Use Case Name: Order Queue for tailor
Actors: Tailor
Description: User can see the pending orders in list
Level: Medium
Trigger: User will select the Order queue option
Preconditions: 1. User must be sign in
2. User must have already accepted one or more orders
Includes: UC-1.1,UC-3.5
Normal Flow: 1. User select the Order details
2. User select the pending order
Alternative 1. User select the side menu
Flows: 2. Select the Order Queue
Exceptions: N/A
Postconditions: 1. All the pending order will be displayed
Special N/A
Requirements:
Assumptions: 1. User must have the knowledge of using application
2. User Should know how to select side menu
3. User should know how to select order details
Notes and N/A
Issues:
Module 6: Chat box
Below are the uses cases for Module-4
6.1. Send Text message
Use Case ID: UC:6.1

Use Case Name: Send Text message
Actors: Customer, Tailor, Admin
Description: This use case will allow the users to send text message i.e. customer can send text
message to tailor. Tailor can send a message to customer for order purposes. And
admin can send text message to both customer and tailor.
Level: High
Trigger: User will click on the Send text button.
Preconditions: 1. Internet should be available.
2. User should have an active sim card service.
3. User should sign in through his/her id.
4. User should choose the recipient.
Includes: UC:1.3
Normal Flow: 1. User opens the main page of the application.
2. System shows the button of sign in and sign up.
3. User clicks the sign in button.
4. User signs in.
5. User clicks on the Send text message button.
6. Then chooses the recipient he/she wishes to send it.
7. Then writes what they want to send.
8. Then clicks the Send button.
Alternative None
Flows:
Exceptions: 1. If the admin provides wrong information for signing in.
2. If no recipient is selected.
3. If no text is written.
Post conditions: The user will send a text successfully.
Special None
Requirements:
Assumptions: The user must know the English language and can use computer easily.
Notes and None
Issues:
6.2. Send Dress Images
Use Case ID: UC:6.2

Use Case Name: Send Dress Images
Description: This use case will allow the users to send images i.e. customer can send images to
tailor. Tailor can send an image to customer for order purposes
Level: High
Trigger: User will click on the Send image button.
Includes: UC:1.3
4. User signs in.
5. User clicks on the Send image button.
7. Then choose the image to send.
Alternative 1. User opens the main page of the application.
Flows: 2. System shows the button of sign in and sign up.
4. User signs in.
5. Clicks on the tailor/Customer profile.
6. User clicks on the Send image button.
7. Then choose the image to send.
Exceptions: 7. If the user provides wrong information for signing in.
9. If no image is selected.
Post conditions: The user will send an image successfully.
Special None
Requirements:
Notes and None
Issues:
6.3. Send Dress Models
Use Case ID: UC:6.3
Use Case Name: Send Dress Model
Description: This use case will allow the users to send the 3D models of dresses i.e. customer
can send dress models to tailor.
Level: High
Trigger: User will click on the Send model button.
Includes: UC:1.3, UC:2.3
4. User signs in.
5. User clicks on the Send model button.
7. Then choose the model they want to send.
Alternative 1. Customer opens the main page of the application.
3. Customer clicks the sign in button.
4. Customer signs in.
5. Customer clicks on the View Models button.
6. Customer selects a dress and clicks Send as Order button.
3. If no model is selected.
Post conditions: The user will send a model successfully.
Special 1. User should have an active sim card service.
Requirements:
Notes and None
Issues:
6.4. Place a Phone Call
Use Case ID: UC:6.4

Use Case Name: Place a Phone call
Description: This use case will allow the users to place a phone call i.e. customer can phone
call tailor. Tailor can call customer for order purposes.
Level: High
Trigger: User will click on the phone call button.
Includes: UC:1.3, UC:4.1, UC:4.2, UC:1.6
4. User signs in.
5. Then chooses the recipient he/she wishes to call.
6. User clicks on the phone call button.
Alternative 10. User opens the main page of the application.
13. User signs in.
14. Clicks on the tailor/Customer profile.
15. User clicks on the phone call button.
Post conditions: The user will be able to place a phone call successfully.
Special None
Requirements:
Notes and None
Issues:
6.5.Receive Text message
Use Case ID: UC:6.5

Use Case Name: Receive Text message
Description: User will be asked to allow the sender to send message.
Level: High
Trigger: User will click on the Allow/Delete massage.
4. A user should receive a message.
Includes: UC:1.3
4. User signs in.
5. User clicks on the inbox button.
6. User then choose a new message to view.
7. User then will click on the allow/Delete message button.
Alternative None
Flows:
Post conditions: The user will receive a text successfully.
Special None
Requirements:
Notes and None
Issues:
6.6.Receive phone Call
Use Case ID: UC:6.6

Use Case Name: Receive Phone Call
Description: User will be asked to accept/reject a phone call.
Level: High
Trigger: User will click on the accept/reject phone call.
4. A user should receive a phone call.
Includes: UC:1.3
4. User signs in.
5. If user receives a phone call.
6. User then will click on the accept/reject button.
Alternative None
Flows:
Post conditions: The user will receive a phone call successfully.
Special None
Requirements:
Notes and None
Issues:
6.7.Receive Dress Images
Use Case ID: UC:6.7

Use Case Name: Receive Dress Images
Description: User will be asked to accept/reject Dress images.
Level: High
Trigger: User will click on the accept/reject Dress Images
4. A user should receive Dress images
Includes: UC:1.3
4. User signs in.
5. If user receives dress images.
Alternative None
Flows:
Post conditions: The user will receive dress images successfully.
Special None
Requirements:
Notes and None
Issues:
6.8. Receive Dress Models
Use Case ID: UC:6.8

Use Case Name: Receive Dress Models
Description: User will be asked to accept/reject Dress model.
Level: High
Trigger: User will click on the accept/reject Dress model
4. A user should receive Dress model
Includes: UC:1.3
4. User signs in.
5. If user receives dress models.
Alternative None
Flows:
Post conditions: The user will receive dress images successfully.
Special None
Requirements:
Notes and None
Issues:
Module 7: Notification
Below are the uses cases for notification.
7.1. View notification
Use Case ID: 7.1
Use Case Name: View notification
Description: The user must be able view the notification generated by the system, customer,
tailor or admin
Level: High
Trigger: When the user opens his or her notification
Preconditions: 1. User must be logged into his account
Includes: UC-1.2
Normal Flow: 1. User clicks on notification icon
2. User view the notification
Alternative None
Flows:
Exceptions: None
Post conditions: 1. The user will be able to view the notification
Special None
Requirements:
Notes and None
Issues:
7.2.Send SMS
Use Case ID: 7.2
Use Case Name: Send SMS
Actors: System
Description: The system will generate a SMS to customer and tailor when they create the
account and when they place an order
Level: Medium
Trigger: When the customer or tailor create their account or place an order
Preconditions: 1. The user must create their account
2. The user must place an order
Includes: UC-1.1
Normal Flow: 1. User downloads the application
2. User clicks on sign up
3. User enter his details i.e. first name, last name, contact etc.
4. User clicks on sign up button
5. User will receive a SMS
Alternative 1. User opens his profile
Flows: 2. User places an order
3. User will receive a SMS of placing order
Exceptions: None
Post conditions: 1. System will be able to send SMS notification successfully
Special None
Requirements:
Notes and None
Issues:
7.3.Push notification
Use Case ID: 7.3

Use Case Name: Push notification
Actors: System
Description: The system will generate alert dialog box when user confirms a cancelation or
when the location is turned off while opening maps
Level: High
Trigger: When the user opens maps without turning on the location on the phone or when
confirmation is needed for cancelation or acceptation
Preconditions: 1. The user must cancel an order or request
2. The user must open maps
Includes: None
Normal Flow: 1. User opens profile
2. User open maps
3. System will generate an alert dialog box “turn on your location”
Alternative 1. User opens profile
Flows: 2. User places an order or request
3. User cancels that order or request
4. System will generate a dialog box for confirmation “Confirm cancel”
Exceptions: None
Post conditions: 1. The system will be able to successfully generate a dialog box
Special None
Requirements:
2. The tailor should know how to use maps
Notes and 1. The location of the user must be disabled
Issues: 2. The customer can only cancel a request when he have made one before
7.4.Inbox requests
Use Case ID: 7.4
Use Case Name: Inbox requests
Actors: Customers, tailors
Description: The customer and tailor can send request to each other for the stitching purposes,
and those request will be stored as inbox requests
Level: High
Trigger: When the customer or tailor send request
Preconditions: 1. The tailor or customer must be logged in
2. The tailor or customer must send request
Includes: UC-2.4
Normal Flow: 1. Customer logs into his profile
2. Customer sends request to tailor for the stitching of their cloths
3. A inbox request will be sent to tailor
Alternative 1. Tailor logs into his profile
Flows: 2. Tailor sends request to customer when their cloths will be stitched
3. A inbox request will be sent to customer
Exceptions: None
Post conditions: 1. A inbox request will be successfully sent to tailor and customer
Special None
Requirements:
Notes and None
Issues:
Module 8: System Recommender:
8.1. Ratings Based Recommendations
Use Case ID: UC:8.1

Use Case Name: Ratings Based Recommender
Actors: Customer
Description: Uses will be provided some recommendations on the basis of the ratings. I.e.
customers will get recommended tailors for their requirements and vice versa.
Level: Medium
Trigger: User will click on the recommendations button.
3. User should provide some requirements.
Includes: UC-1.3,UC-4.3,UC-4.4
4. User signs in.
5. User defines his/her requirements.
6. User clicks on the recommendations button.
Alternative None
Flows:
2. If requirements does not match any recommendations
Post conditions: The user will be provided with some recommendations.
Special None
Requirements:
Notes and None
Issues:
8.2.Budget Based Recommendations
Use Case ID: UC:8.2

Use Case Name: Budget Based Recommender
Actors: Customer
Description: Uses will be provided some recommendations on the basis of the budget. I.e.
customers will get recommended tailors for their requirements and vice versa.
Level: Medium
Includes: UC:1.3,UC:4.1,UC:4.2
4. User signs in.
Alternative None
Flows:
Post conditions: The user will be provided with some recommendations.
Special None
Requirements:
Notes and None
Issues:
8.3.View Recommendations
Use Case ID: UC:8.3

Use Case Name: View Recommendations
Actors: Customer
Description: Uses will be provided some recommendations I.e. customers will get
recommended tailors for their requirements and vice versa.
Level: Medium
10. User signs in.
Alternative None
Flows:
Post conditions: The user will be able to view recommendations
Special None
Requirements:
Notes and None
Issues:
8.4. Aggregate Recommendations
Use Case ID: UC:8.4

Use Case Name: Aggregate recommender
Actors: Customer,
Description: Uses will be provided some recommendations I.e. customers will get
recommended tailors for their requirements
Level: Medium
4. User signs in.
Alternative None
Flows:
Post conditions: The user will be able to view the aggregated recommendations
Special None
Requirements:
Notes and None
Issues:
Module 9: Help and Support:
9.1. About Application
Use Case ID: UC:9.1

Use Case Name: About Application
Actors: Customer, Tailor, Admin
Description: Uses will be provided with the purpose/description of the application.
Level: Medium
Trigger: User will click on the About Application button.
Includes: UC:1.3
4. User signs in.
5. User clicks on the Help and Support button.
6. User clicks on the About Application button.
Alternative None
Flows:
Post conditions: The user will be able to view the description about application.
Special None
Requirements:
Notes and None
Issues:
9.2. Contact Us
Use Case ID: UC:9.2

Use Case Name: Contact Us
Description: Users can contact the admins related to the application.
Level: Medium
Trigger: User will click on the Contact Us button.
Includes: UC:1.3
4. User signs in.
6. User clicks on the Contact Us button.
Alternative None
Flows:
Post conditions: The user will be able to contact the admins through the application..
Special None
Requirements:
Notes and None
Issues:
9.3. FAQs
Use Case ID: UC:9.3

Use Case Name: FAQs
Description: Uses will be provided with the most frequently asked questions along with their
answers.
Level: Medium
Trigger: User will click on the FAQs button.
Includes: UC:1.3
4. User signs in.
6. Then clicks on the FAQs button.
Alternative None
Flows:
Post conditions: The user will be able to view the description about application.
Special None
Requirements:
Notes and None
Issues:
9.4. Report problem
Use Case ID: UC:9.4

Use Case Name: Repost problem
Description: Users can contact the admins in order to report any problem. This problem can be
related to any other user as well.
Level: Medium
Trigger: User will click on the Report a problem button.
Includes: UC:1.3
4. User signs in.
6. User clicks on the Report a Problem button.
Alternative None
Flows:
Post conditions: The user will be able to contact the admins through the application.
Special None
Requirements:
Notes and None
Issues:
9.5. Textual guidelines
Use Case ID: UC:9.5

Use Case Name: Textual guidelines
Description: Users can view Guidelines in order to understand the working of the application
better.
Level: Medium
Trigger: User will click on the Guidelines button.
Includes: UC:1.3
4. User signs in.
6. User clicks on the Guidelines button.
Alternative None
Flows:
Post conditions: The user will be asked for about the specific feature they want guidelines. And
then they will be able to view the guidelines.
Special None
Requirements:
Notes and None
Issues:
9.6. User Feedback
Use Case ID: UC:9.6

Use Case Name: User Feedback
Description: Users will be asked to give their feedback about the application after using it for
some time.
Level: Medium
Trigger: User will click on feedback button.
Includes: UC:1.3
4. User signs in.
6. User clicks on the Feedback button.
Alternative None
Flows:
Post conditions: The user will be able to provide their feedback about the application.
Special None
Requirements:
Notes and None
Issues:
9.7. Suggestions
Use Case ID: UC:9.7

Use Case Name: Suggestions
Description: Users can give any suggestions about the application. It can be about anything in
order to improve the application.
Level: Medium
Trigger: User will click on the Suggestions button.
Includes: UC:1.3
4. User signs in.
6. User clicks on the Suggestions button.
Alternative None
Flows:
Post conditions: The user will be able to provide suggestions to improve the application.
Special None
Requirements:
Notes and None
Issues:
9.8. Admin response
Use Case ID: UC:9.8

Use Case Name: Respond Feedback
Actors: Admin
Description: Admin will respond to the customers and tailors on their given feedback.
Level: Medium
Trigger: User will click on respond feedback button.
Includes: UC:1.3
4. User signs in.
6. User clicks on the Feedback button.
7. Then user will choose the feedback to respond.
8. Then user will write the response.
Alternative None
Flows:
Post conditions: Admins will be able to respond the feedback customers and tailors have provided.
Special None
Requirements:
Notes and None
Issues:
5. Specific Requirements
Following are the FR’s of Stichit
Module 1: User Management
UC-1.1: Sign up
Identifier 1.1.1
Title First name
Requirement The user should be able for enter his name in order to
create his account.
Source Team Member 2 (Linta Anmol)
Rationale User will be able to create his account
Restrictions and Risk This field should be filled
Dependencies None
Priority High
Table 1: First name
Identifier 1.1.2
Title Last name
Requirement The user should be able to enter his last name in order to
create account.
Restrictions and Risk This field should be filled
Dependencies 1.1.1
Priority Medium
Table 2: Last name
Identifier 1.1.3
Title Phone number
Requirement User must enter his number, so in case of forgetting
password, user can recover it from his phone number.
Restrictions and Risk The user cannot recover his id if there is no number.
Dependencies 1.1.1,1.1.2
Priority Medium
Table 3: Phone number
Identifier 1.1.4
Title Gender
Requirement The user will be able to add his gender
Source None
Restrictions and Risk Team Member 2 (Linta Anmol)
Priority High/Medium/Low
Table 4: Gender
Identifier 1.1.5
Title Email
Requirement In order to create account, user must provide email id.
Rationale User will be able to create account only he can access
through email
Restrictions and Risk Email should be uniquely identified.
Dependencies 1.1.1,1.1.2,1.1.3
Priority High
Table 5: Email
Identifier 1.1.6
Title Password
Requirement To create account, user must enter password.
Rationale User will be able to create account and make it secure
Restrictions and Risk The user must remember the password
Dependencies 1.1.1,1.1.2,1.1.3,1.1.5
Priority High
Table 6: Password
Identifier 1.1.7
Title Confirm password
Requirement To verify the above entered password is correct or not.
Rationale To see if the above entered password does not contain any
wrong letter or sign.
Restrictions and Risk It should be exactly same as password entered before
Dependencies 1.1.1,1.1.2,1.1.3,1.1.5,1.1.6
Priority High
Table 7: Confirm password
Identifier 1.1.9
Title Sign up button
Requirement The user must be able to sign up
Rationale To ensure that the user provide all the details in order to
create his account
Restrictions and Risk User will be unable to login without signing up to create
his account
Dependencies 1.1.1,1.1.2,1.1.3,1.1.5,1.1.6,1.1.7,1.1.8
Priority High
Table 8: Sign up button

UC 1.2: sign in
Identifier 1.2.1
Title Email
Requirement In order to log into his account user must provide email
Rationale Without email, user cannot use the system
Restrictions and Risk It should be the one provided in the sign up form, else the
user won’t be able to log into his account
Dependencies 1.1.9
Priority High
Table 9: Email
Identifier 1.2.2
Title Password
Requirement To open account, user must enter password
Rationale Without password user cannot log into account
Restrictions and Risk User should remember it
Dependencies 1.1.9
Priority High
Table 10: password
Identifier 1.2.3
Title Forget password
Requirement User must be able to access id even if he forgets password
Rationale To ensure user won’t lose any data that is present inside
the application
Restrictions and Risk User must remember the alternative email or contact no.
Dependencies None
Priority Medium
Table 11: Forget password
Identifier 1.2.4
Title Remember me
Requirement To remember user email and its password
Rationale To assist user not to enter email and password every time
Restrictions and Risk None
Dependencies None
Priority Low
Table 12: Remember me
Identifier 1.2.3
Title sign in
Requirement The user must be able to log into is account
Rationale Without logging in, the user cannot enter into his account
Restrictions and Risk User must remember his credentials to log in
Priority High
Table 13: sign in
UC-1.3: Forget password
Identifier 1.3.1
Title Email
Requirement The user must be able to enter email
Rationale To ensure the recovery of user’s account
Restrictions and Risk User must enter the email id which is already registered.
Dependencies None
Priority High
Table 14: Email
Identifier 1.3.2
Title Phone number
Requirement User should be able to enter number for the recovery og his
account
Rationale User can access the account by providing the number
Restrictions and Risk User should enter the same number, he entered while
creating his account.
Dependencies None
Priority Medium
Table 15:Phone number
Identifier 1.3.4
Title Send code
Requirement User must be able to enter the receive the code that was
sent to user through the alternate email and phone number
Rationale To recover user’s account
Restrictions and Risk Should be careful about case sensitive code
Priority Medium
Table 16: Send code
Identifier 1.3.5
Title Enter code
Requirement User must be able to enter the code in the given space to
access its account
Rationale To access account
Restrictions and Risk Code should be same as sent by system
Dependencies 1.3.4
Priority Medium
Table 17: Enter code
UC-1.4: Remember me
Identifier 1.4.1
Title Check box
Requirement To remember user email and its password
Source None
Rationale To assist user not to enter email and password every time
Priority Low
Table 18: Check box
UC-1.5: View Profile
Identifier 1.5.1
Title First name
Requirement The user should be able to see his first name
Rationale User will be able to view his details in his profile
Dependencies 1.1.9
Priority High
Table 19: First name
Identifier 1.5.2
Title Last name
Requirement The user should be able to see his last name
Dependencies 1.1.9
Priority Medium
Table 20: Last name
Identifier 1.5.3
Title Contact number
Requirement The user should be able to see his phone number
Dependencies 1.1.9
Priority Medium
Table 21: contact number
Identifier 1.5.4
Title Gender
Requirement The user should be able to see his gender
Dependencies 1.1.9
Priority Medium
Table 22: gender
Identifier 1.5.5
Title Email
Requirement The user should be able to see his email
Dependencies 1.1.9
Priority High
Table 23: Email
UC-1.6: Edit Profile
Identifier 1.6.1
Title First name
Requirement The user should be able to enter his first name in order to
change his name or spelling while editing his profile
Rationale To ensure user that he can change his details whenever he
wants
Restrictions and Risk This field should be filled with valid requirements
Dependencies None
Priority High
Table 24: First name
Identifier 1.6.2
Title Last name
Requirement The user should be able for enter his last name in order to
change his name or spelling while editing his profile
wants
Dependencies 1.1.9
Priority Medium
Table 25: Last name
Identifier 1.6.3
Title Contact number
Requirement User must enter his number, so in case of forgetting
password, user can recover it from his phone number.
wants
Dependencies 1.1.9
Priority Medium
Table 26: Contact number
Identifier 1.6.4
Title Gender
Requirement The user will be able to create
wants
Dependencies 1.1.9
Priority Medium
Table 27: Gender
Identifier 1.6.5
Title Email
Requirement In order to create account, user must provide email id.
wants
Restrictions and Risk Email should be uniquely identified.
Dependencies 1.1.9
Priority High
Table 28: Email
Identifier 1.6.6
Title Update Profile
Requirement The user must be able to sign up
Rationale To ensure that the user provide all the details in order to
create his account
Restrictions and Risk User will be unable to login without signing up to create
his account
Dependencies None
Priority High
Table 29: Update profile
Module 2: 3D Dress Design
UC-2.1: View Dress Categories
Identifier 2.1.1
Title Select category
Requirement User can be able to select different categories of dress from
gallery.
Source Team Member 1 (Abdul Rehman Sohail)
Rationale User have option to see different dress.
Restrictions and Risk N/A
Dependencies N/A
Priority High
Table 30: Select category
Identifier 2.1.2
Title View category
Requirement User can see different categories
Rationale User have different dress categories to select
Dependencies N/A
Priority Medium
Table 31: View category
Identifier 2.1.3
Title Search category
Requirement User will able to search category
Rationale User can search the category if he doesn’t find one
Dependencies N/A
Priority Medium
Table 32: Search category
Identifier 2.1.4
Title Men’s clothing
Requirement User will choose the men's clothing category
Rationale Customer will be able to view the men’s clothing models
Restrictions and Risk Customer must choose men’ clothing category
Dependencies N/A
Priority Medium
Table 33: Men’s clothing
Identifier 2.1.5
Title Women’s clothing
Requirement Customer will choose the women's clothing category
Rationale Customer will be able to view the women’s clothing
models.
Restrictions and Risk Customer must choose women’s clothing category.
Dependencies 1.1.3
Priority Medium
Table 34: Women’s clothing
Identifier 2.1.6
Title Formal clothing
Requirement Customer will choose the Formal clothing category after
choosing men/women category.
Source
Rationale Customer will be able to view the formal clothing models.
Restrictions and Risk Customer must choose formal clothing category.
Dependencies 1.1.3
Priority Medium
Table 35: Formal clothing
Identifier 2.1.7
Title Informal clothing
Requirement Customer will choose the informal clothing category after
Source
Rationale Customer will be able to view the informal clothing
models.
Restrictions and Risk Customer must choose informal clothing category.
Dependencies 1.1.3
Priority Medium
Table 36: Informal clothing
Identifier 2.1.8
Title Casual clothing
Requirement Customer will choose the casual clothing category after
Source
Rationale Customer will be able to view the casual clothing models.
Restrictions and Risk Customer must choose casual clothing category.
Dependencies 1.1.3
Priority Medium
Table 37: Casual clothing

UC-2.2: View Dress Model
Identifier 2.2.1
Title Display 3D model
Requirement This will display the 3D model of dress to the user
Rationale To provide the user with 3D dress model for better
understanding
Restrictions and Risk The model should be drawn accurately and precisely
Dependencies N/A
Priority High
Table 38: Display 3D dress model
Identifier 2.2.2
Title Interact with the 3D Model
Requirement This will provide the user with the ability to interact with
each 3D model of the Dress
Rationale To make the understanding of the 3D model better
Restrictions and Risk The model should be drawn accurately and precisely
Dependencies 2.2.1
Priority High
Table 39: Interact with the 3D model
Identifier 2.2.3
Title Zoom in on the 3D model
Requirement This will provide the user with the ability to zoom in on 3D
model
Rationale To make the viewing of model easier and provide more
depth
Restrictions and Risk The model should stay intact and pixels should not
collapse
Dependencies 2.2.1
Priority Medium
Table 40: Zoom in on the 3D Model
Identifier 2.2.4
Title Zoom out on the 3D model
Requirement This will provide the user with the ability to zoom out on
3D model
Rationale To make the viewing of model easier and provide clear
picture of the model
collapse
Dependencies 2.2.1
Priority Medium
Table 41: Zoom out on the 3D Model
Identifier 2.2.5
Title Rotate the 3D model clockwise
Requirement This will provide the user with the ability to rotate the
model clockwise and see it from other side
Rationale To make the viewing of model easier and provide the
complete picture of each model
collapse
Dependencies 2.2.1
Priority Medium
Table 42: Rotate the 3D Model clockwise
Identifier 2.2.6
Title Rotate the 3D model anticlockwise
model anticlockwise and see it from other side
collapse
Dependencies 2.2.1,
2.2.5
Priority Medium
Table 43: Rotate the 3D Model anticlockwise
Identifier 2.2.7
Title Swipe Right
Requirement User will swipe right to view the complete model.
Source
Rationale Users will be able to view the next model of the particular
category.
Restrictions and Risk User must swipe right to view the complete model.
Dependencies 2.2.1
Priority High
Table 44: Swipe right
Identifier 2.2.8
Title Swipe left
Requirement User will swipe left to view the complete model.
Source
Rationale Users will be able to view the previous model of the
particular category.
Restrictions and Risk User should swipe left to view the complete model.
Dependencies 2.2.1
Priority High
Table 45: Swipe left
4.8.UC-2.3: Dress Customization
Identifier 2.3.1
Requirement This will provide the user with 3D model of the Dress
Rationale To make 3D model ready to customize
collapse
Dependencies N/A
Priority High
Table 46: Display 3D Model
Identifier 2.3.2
Title Display Embellishments Tray
Requirement This will provide the user with different features in a tray.
Rationale User can use these features to customize the dress
Restrictions and Risk The features should stay intact and pixels should not
collapse
Dependencies 2.3.1
Priority Medium
Table 47: Display Elements Tray
Identifier 2.3.3
Title Applicationly embellishments on Dress
Requirement This will provide the user to customize the Dress design
Rationale User can customize dress with these design
Dependencies 2.3.1
2.3.2
Priority Medium
Table 48: Applicationly element on dress
Identifier 2.3.4
Requirement This will provide the user with the ability to zoom in on 3D
model
depth
collapse
Dependencies 2.3.1
Priority Medium
Table 49: Zoom in on the 3D Model
Identifier 2.3.5
3D model
collapse
Dependencies 2.3.1
Priority Medium
Table 50: Zoom out on the 3D Model
Identifier 2.3.6
Title Rotate the 3D model clockwise
collapse
Dependencies 2.3.1
Priority Medium
Table 51: Rotate the 3D Model clockwise
Identifier 2.3.7
Title Rotate the 3D model anticlockwise
collapse
Priority Medium
Table 52: Rotate the 3D Model anticlockwise
Identifier 2.3.8
Title Save customized 3D Model
Requirement This will provide the user with the ability to save the Dress
Model
Rationale To allow user to continue his customization or send it to
other
Restrictions and Risk The model should be customized first.
Dependencies 2.3.3
Priority Medium
Table 53: Save customized 3D Model
Identifier 2.3.9
Title Swipe Right
Source
category.
Dependencies 2.2.1
Priority High
Identifier 2.3.10
Title Swipe left
Source
Dependencies 2.2.1
Priority High
UC-2.4: Send model as order
Identifier 2.4.1
Title Send model
Requirement This will provide the user with the ability to send the
model for order
Rationale To allow the user to stich the dress according to model
Restrictions and Risk The model should send and receive by the user easily
Dependencies N/A
Priority High
Table 56: Send Model
Identifier 2.4.2
Title Select user to send
Requirement This will provide the user with the ability to select the user
to send model
Rationale To allow user to send model to a other user
Restrictions and Risk The User must be available to receive the model
Dependencies 2.4.2
Priority Medium
Table 57: Select user to send
Identifier 2.4.3
Title Search User
Requirement This will provide the user with the ability to search User to
send the model
Rationale To allow user to send model to a specific user
Dependencies 2.4.2
Priority Medium
Table 58: Search User
Identifier 2.4.4
Title Confirm send
Requirement This will provide the user to confirm to send Model
Rationale To allow user to send model to a specific user
Dependencies 2.4.2
Priority Medium
Table 59: Confirm send
UC-2.5: Search customized dresses
Identifier 2.5.1
Title Search Dress model
Requirement This will provide the user to search the model.
Rationale To help user to search customized dress that he saved
Restrictions and Risk The Dress should be customized once and saved before it
searched
Dependencies N/A
Priority Medium
Table 60: Search Dress Model
Identifier 2.5.2
Title Select customized Dress
Requirement This will provide the user to continue its customization
where he left
Rationale To help user to customize model again
Restrictions and Risk There must exist one or more saved models
Dependencies 2.5.1
Priority Medium
Table 61: Select Customized Dress
Identifier 2.5.3
Requirement This will provide the user with 3D model of the Dress
Rationale To make 3D model ready to customize
collapse
Dependencies 2.5.1
2.5.2
Priority High
Table 62: Display 3D Model
UC-2.6: Search Dress model by filter
Identifier 2.6.1
Title Search by colors
Requirement This will provide the user with the ability to search design
by colors
Rationale To allow user to search easily by applicationlying filters
Restrictions and Risk There must be one or more design saved in system
Dependencies N/A
Priority Medium
Table 63: Search by colors
Identifier 2.6.2
Title Search by category
Requirement This will provide the user with the ability to search design
by category
Rationale To allow user to search easily by applicationlying filters
Dependencies N/A
Priority Medium
Table 64: Search by category
Identifier 2.6.3
Title Confirm Search
Requirement This will provide the user to confirm his search
Rationale To allow user to search design
Dependencies N/A
Priority Medium
Table 65: Confirm Search
UC-2.7: Add dress category
Identifier 2.7.1
Title Dress category name
Requirement This will provide the user with the ability to enter a name
for dress category
Rationale To allow user to name the category
Dependencies N/A
Priority Low
Table 66: Dress Category Name
Identifier 2.7.2
Title Dress Category Details
Requirement This will provide the user to add details about the category
in two or three lines
Rationale To allow the user to see the details of category
Dependencies N/A
Priority Medium
Table 67: Dress Category Details
Identifier 2.7.3
Title Dress category thumbnail
Requirement This will provide the user to add image of category.
Rationale It will allow user to see the category image
Dependencies N/A
Priority Medium
Table 68: Dress category thumbnail
UC-2.8: Choose Dress Design
Identifier 2.8.1
Title Display List of design
Requirement This will provide the user with the ability to see the
different design
Rationale To help user to see all design in one list
Dependencies N/A
Priority Medium
Table 69: Display list of design
Identifier 2.8.2
Title Select Design
Requirement This will provide the user with the ability to select the
design
Rationale To help user to select the design
Restrictions and Risk There must be some design displayed in list
Dependencies 2.8.1
Priority Medium
Table 70: Select Design
Identifier 2.8.3
Title Display Design
Requirement This will provide the user with the ability to see the Design
Rationale To make the viewing of design easier
Dependencies N/A
Priority Medium
Table 71: Display Design
Identifier 2.8.4
Requirement This will provide the user with the ability to zoom in on
Design
Rationale To make the viewing of Design easier and provide more
depth
collapse
Dependencies 2.8.1
Priority Medium
Table 72: Zoom in on the 3D model
Identifier 2.8.5
Design
Rationale To make the viewing of Design easier and provide clear
picture of the Design
collapse
Dependencies 2.9.1
Priority Medium
Table 73: Zoom out on the 3D model
Identifier 2.8.6
Title Swipe Right
Source
category.
Dependencies 2.2.1
Priority High
Identifier 2.8.7
Title Swipe left
Source
Dependencies 2.2.1
Priority High
UC-2.9: Textual guide for 3D model
Identifier 2.9.1
Title Select Guide
Requirement This will provide the user with the ability of viewing text
guide
Source Team members
Rationale To guide user how to customize 3D model
Dependencies N/A
Priority Medium
Table 76: Select Guide
Identifier 2.9.2
Title Page down
Requirement This will provide the user with the ability to page down the
user guide
Rationale To help user to read all the page
Dependencies 2.10.1
Priority Medium
Table 77: Page down
Identifier 2.9.3
Title Page up
Requirement This will provide the user with the ability to page up the
user guide
Rationale To help user to read all the page
Dependencies 2.10.1
2.10.2
Priority Medium
Table 78: Page Up
Identifier 2.9.4
Title Next page
Requirement This will provide the user with the ability to go to the next
page of guide
Rationale To help user to read all the pages
Dependencies 2.10.1
Priority Medium
Table 79: Next Page
Identifier 2.9.5
Title Previous page
Requirement This will provide the user with the ability to go to the
previous page
Dependencies 2.10.1
Priority Medium
Table 80: previous page
UC-2.10: Add Dress model
Identifier 2.10.1
Title Add model name
Requirement This will provide the user with the ability to name the
model
Rationale To help user to see the name of dress model
Dependencies N/A
Priority Medium
Table 81: Add model name
Identifier 2.10.2
Title Add model details
Requirement This will provide the user to write about the model in two
or three lines
Rationale It will help to create the description of dress model
Dependencies N/A
Priority Medium
Table 82: Add model details
Identifier 2.10.3
Title Add model thumbnail
Requirement This will provide the user to post a thumbnail of model
Rationale To help user to see how the model look like
Dependencies N/A
Priority Medium
Table 83: Add model image
UC-2.11: Delete Dress Category
Identifier 2.11.1
Title Select Dress category
dress category
Rationale To help user to select multiple or single category
Restrictions and Risk There must be some category in the gallery
Dependencies N/A
Priority Medium
Table 84: Select Dress category
Identifier 2.11.2
Title Confirm delete
Requirement This will provide the user to delete the category
Rationale It will allow user to delete category from the gallery
Restrictions and Risk There must be one or more category in the gallery
Dependencies N/A
Priority Medium
Table 85: Confirm delete
UC-2.12: Delete Dress model
Identifier 2.12.1
Title Select model dress
dress model
Rationale To help user to select multiple or single model
Restrictions and Risk There must be one or more models in category
Dependencies N/A
Priority Medium
Table 86: Select model dress
Identifier 2.12.2
Requirement This will provide the user to delete the model
Rationale It will delete the models from categories
Restrictions and Risk There must be some models in the categories
Dependencies N/A
Priority Medium
Table 87: Confirm Delete
UC-2.13: Edit dress category
Identifier 2.13.1
Title Edit Name
Requirement This will provide the user with the ability to edit name of
category
Rationale It will allow user to edit name of category.
Dependencies N/A
Priority Medium
Table 88: Edit Name
Identifier 2.13.2
Title Edit details
Requirement This will provide the user with the ability to edit details of
the category
Rationale It will allow user to edit details of category.
Dependencies N/A
Priority Medium
Table 89: Edit details
Identifier 2.13.3
Title Edit thumbnail
Requirement This will provide the user with the ability to edit thumbnail
of the category
Rationale It will allow user to edit thumbnail of category.
Dependencies N/A
Priority Medium
Table 90: Edit thumbnail
UC-2.14: Edit Dress model
Identifier 2.14.1
Title Edit Name
Requirement This will provide the user with the ability to edit name of
model
Rationale It will allow user to edit name of model.
Dependencies N/A
Priority Medium
Table 91: Edit Name
Identifier 2.14.2
Title Edit details
Requirement This will provide the user with the ability to edit details of
the model
Rationale It will allow user to edit details of model
Dependencies N/A
Priority Medium
Table 92: Edit details
Identifier 2.14.3
Title Edit thumbnail
Requirement This will provide the user with the ability to edit thumbnail
of the model
Rationale It will allow user to edit thumbnail of model
Dependencies N/A
Priority Medium
Table 93: Edit thumbnail
UC-3.1: Find tailor on map
Identifier 3.1.1
Title Open map for customer
Requirement Customer must be able to open the map to see available
tailors
Rationale To make it more graphical and easier to view on map
Restrictions and Risk Location of the phone of user must be turned on in order to
search for the tailor
Dependencies None
Priority High
Table 94: Open map for customer
Identifier 3.1.2
Title Search for tailor
Requirement The customer will be able to search for tailor
Rationale To enable the customer to search for tailor
Restrictions and Risk Location of the phone of user must be turned on in order to
search for the tailor
Dependencies 5.1.1
Priority High
Table 96: search for tailor
Identifier 3.1.3
Title View tailor Profile
Requirement It helps the customer to view the profile of the different
tailors on the map
Rationale To enable the customer to view different tailors profile and
select the best among them on the basis of their needs
Restrictions and Risk The tailor’s profile must public
Priority High
Table 97: view tailor profile
UC-3.2: Customer requirement
Identifier 3.2.1
Title Add customer’s requirements
Requirement It will allow a customer to enter their requirements for
some specific dress
Rationale To enable a customer to add their requirements and find a
tailor who will do their work in a within the customer’s
budget
Dependencies None
Priority Medium
Table 98: add customer requirements
Identifier 3.2.2
Title View customer’s requirements
Requirement It will allow a customer to view their requirements and also
a tailor to view customer’s requirements and contact a one
whose requirements seems reasonable for them
Rationale To enable a customer and tailor to view customer’s
requirement
Dependencies 5.4.1
Priority Medium
Table 99: View customer’s requirements
Identifier 3.2.3
Title Edit customer’s requirements
Requirement It will allow a customer to edit their requirements if they
want to add something or remove something from the one
they made earlier
Rationale To enable customer to edit their requirements
Dependencies 5.4.1
Priority Medium
Table 100: edit customer requirements
Identifier 3.2.4
Title Submit requirements
Requirement It will allow a customer to submit their requirements they
added or updated
Rationale To enable the customer to submit their requirements
Priority High
Table 101: Submit requirements
UC-3.3: Accept Dress order
Identifier 3.3.1
Title View request
Requirement It will allow a tailor to view customer’s request and
customer to view tailor’s request
Rationale To enable both the customer and tailor to view each other’s
requests
Dependencies 5.4.4
Priority High
Table 102: view request
Identifier 3.3.2
Title Select request
Requirement It will allow a tailor to select customer’s request and
customer to select tailor’s request
Rationale To enable both the customer and tailor to select each
other’s requests
Dependencies 5.5.1
Priority High
Table 103: Select request
Identifier 3.3.3
Title View profile
Requirement It will allow a customer to view tailor’s profile and tailor to
view customer’s profile public entities
profiles
Restrictions and Risk Tailor won’t be able to view customer’s private profile
information
Dependencies 5.5.1
Priority Medium
Table 104: View profile
Identifier 3.3.4
Title Accept request
Requirement It will allow a tailor to accept customer’s request and
customer to accept tailor’s request
Rationale To enable both the customer and tailor to accept each
other’s requests
Priority High
Table 105: Accept request
UC-3.4: Reject Dress Order
Identifier 3.4.1
Title View request
Requirement It will allow a tailor to view customer’s request and
customer to view tailor’s request
requests
Dependencies 5.4.4
Priority High
Table 106: View request
Identifier 3.4.2
Requirement It will allow a tailor to select customer’s request and
customer to select tailor’s request
Rationale To enable both the customer and tailor to select each
other’s requests
Dependencies 5.6.1
Priority High
Identifier 3.4.3
Title Reject request
Requirement It will allow a tailor to reject customer’s request and
customer to reject tailor’s request
Rationale To enable both the customer and tailor to reject each
other’s requests
Priority High
Table 108: Reject request
Identifier 3.4.4
Title Confirm reject
Requirement It will allow a customer or tailor to confirm the rejection
Rationale It will enable a customer or tailor to confirm the rejection
to ensure rejection
Dependencies 5.6.3
Priority High
Table 109: Confirm reject
UC-3.5: Cancel Order
Identifier 3.5.1
Requirement It will allow a tailor to select their own request and
customer to select theirs request
Rationale To enable both the customer and tailor to select their own
requests
Dependencies 5.4.4
Priority High
Identifier 3.5.2
Title Confirm cancelation
Requirement It will allow a customer or tailor to confirm the cancelation
Rationale It will enable a customer or tailor to confirm the
cancelation to ensure cancelation
Dependencies 5.7.1
Priority High
Table 111: Confirm cancelation
UC-3.6: Cancel customer requirements
Identifier 3.6.1
Title Select requirements
Requirement It will allow a customer to select their requirements
Rationale To enable the customer to select their requirements
Dependencies 5.4.1
Priority High
Table 112: Select requirements
Identifier 3.6.2
Title Confirm cancelation
Requirement It will allow a customer to confirm the cancelation of their
requirements
Rationale It will enable a customer to confirm the cancelation to
ensure cancelation
Dependencies 5.8.1
Priority High
Table 113: Confirm cancelation
UC-3.7: Edit Customer requirements
Identifier 3.7.1
Title Add requirements
Requirement It will allow a customer to enter their requirements for
some specific dress
Rationale To enable a customer to add their requirements while
editing
Dependencies 5.4.1
Priority Medium
Table 114: Add requirements
Identifier 3.7.2
Title Delete requirements
Requirement It will allow a customer to delete their requirements
Rationale To enable a customer to delete their requirement
Dependencies 5.4.1
Priority Medium
Table 115: Delete requirements
Identifier 3.7.3
Title Submit requirements
Requirement It will allow a customer to submit their requirements they
added or updated
Rationale To enable the customer to submit their requirements
Dependencies 5.9.1
Priority High
Table 116: submit requirements
UC-3.8: view user on map
Identifier 3.8.1
Title Zoom out
Requirement It will allow the user to zoom out the map
Rationale To enable User to see map clearly
Dependencies 3.1
Priority Medium
Table 117: zoom out
Identifier 3.8.2
Title Zoom in
Requirement It will allow user too Zoom in on the map
Rationale To enable user to see map clearly
Dependencies 3.1
Priority Medium
Table 118: zoom in
Identifier 3.8.3
Title View map
Requirement The user should have clicked the view map button
Rationale The user will be able to view the maps
Restrictions and Risk Location must be turned on
Dependencies 3.1
Priority High
Table 119: view map
Identifier 3.8.3
Title Select by filter
Requirement The user should have clicked select by filter
Rationale User will be able to see select by filter
Dependencies 3.1
Priority Medium
Table 120: Search by filter
UC-3.9: View Profile(C&T)
Identifier 3.9.1
Title Select profile
Requirement User will be able to select his/her profile
Rationale To enable the user to select his profile
Dependencies 3.1
Priority High
Table 121: select profile
Identifier 3.9.2
Title View profile
Requirement User will be able to view his/her profile
Rationale It will allow user to see profile reviews
Dependencies 3.1
Priority Medium
Table 121: view profile
Identifier 3.9.3
Title Send message
Requirement It will allow user with the ability to send message to the
profile owner
Rationale User will communicate
Restrictions and Risk Profile must exist
Dependencies None
Priority High
Table 122: send message

UC-4.1: 3D Dress placement (surface)
Identifier 4.1.1
Title Detect surface
Requirement This will provide the user with the ability to detect the
surface to deploy AR model of dress
Rationale For the deployment of the AR model
Restrictions and Risk Surface should be plain and clear for better placement
Dependencies N/A
Priority High
Table 123: Detect surface
Identifier 4.1.2
Title Place AR Dress Model
Requirement The user will be able to view a simulation of a Dress in AR
Rationale It will show the simulation of dress in real time
environment
Restrictions and Risk The User phone should support AR
Dependencies 3.1.1
Priority High
Table 124: Place AR Dress Model
Identifier 4.1.3
Title Change color of Dress using AR
Requirement The user will be able to change the color of dress in AR
Rationale It will show the simulation of dress in real time
environment
Dependencies 3.1.1
3.1.2
Priority High
Table 125: Change color of Dress using AR
UC-4.2: 360 Dress Rotate
Identifier 4.2.1
Title Rotate the AR model clockwise
complete picture of each model in real time environment
Dependencies N/A
Priority Medium
Table 126: Rotate the AR Model clockwise
Identifier 4.2.2
Title Rotate the AR model anticlockwise
complete picture of each model in real time environment
Dependencies N/A
Priority Medium
Table 127: Rotate the AR Model anticlockwise
UC-4.3: Dress zoom out
Identifier 4.3.1
Title Zoom in on the AR Model
Requirement This will provide the user with the ability to zoom in on
AR model
depth
Dependencies 2.3.1
Priority Medium
Table 128: Zoom in on the AR Model
UC-4.4: Dress Zoom out
Identifier 4.4.1
Title Zoom out on the AR model
AR model
collapse
Dependencies N/A
Priority Medium
Table 129: Zoom out on the AR Model
UC-4.5: View AR guide
Identifier 4.5.2
Title Page down
Requirement This will provide the user with the ability to page down the
user guide
Rationale To help user to read full page
Dependencies 2.10.1
Priority Medium
Table 130: Page down
Identifier 4.5.3
Title Page up
Requirement This will provide the user with the ability to page up the
user guide
Rationale To help user to read full page
Dependencies 3.5.1
Priority Medium
Table 131: Page Up
Identifier 4.5.4
Title Next page
Requirement This will provide the user with the ability to go to the next
page of guide
Dependencies 3.5.1
Priority Medium
Table 132: Next Page
Identifier 4.5.5
Title Previous page
Requirement This will provide the user with the ability to go to the
previous page
Dependencies 3.5.1
Priority Medium
Table 133: previous page
UC-4.6: Add AR Guide
Identifier 4.6.1
Title Choose file to upload
Requirement This will provide the user with the ability to choose file
from their system
Rationale It will upload the AR guide
Dependencies N/A
Priority Medium
Table 134: Choose File to upload
Identifier 4.6.2
Title Upload file
Requirement This will provide the user with the ability to upload the file
Rationale It will upload the AR guide
Restrictions and Risk File must be chosen first before clicking on upload
Dependencies 3.6.1
Priority Medium
Table 135: Upload file
UC-4.7: Delete AR guide
Identifier 4.7.1
Title Select guide
guide
Rationale To help user to select guide
Dependencies N/A
Priority Medium
Table 136: Select guide
Identifier 4.7.2
Requirement This will provide the user with the ability to delete the
guide
Rationale To help user to delete the guide
Restrictions and Risk File must be chosen first before clicking on upload
Dependencies 3.7.1
Priority Medium
Table 137: confirm delete
UC-5.1: Place Dress Order
Identifier 5.1.1
Title Send dress model
Requirement This will provide the user with the ability to send the dress
model to the tailor to stich
Rationale To help tailor to understand the design of dress
collapse
Dependencies N/A
Priority Medium
Table 138: Send dress model
Identifier 5.1.2
Title Send Measurement
Requirement This will provide the user with the ability to send the
Measurement to the tailor
Rationale To help tailor to stich the suit according to the
measurements
collapse
Dependencies N/A
Priority High
Table 139: Send Measurement
Identifier 5.1.3
Title Confirm order
Requirement This will provide the user with the ability to confirm the
order
Rationale It will allow tailor to start work according to the
requirements
Restrictions and Risk All the requirement should be full filed before placing the
dress model
Dependencies N/A
Priority High
Table 140: confirm order
UC-5.2: View order details
Identifier 5.2.1
Title List of orders
Requirement This will provide the list of orders that user have
confirmed
Rationale To help user to see which order is in progress
Dependencies N/A
Priority High
Table 141: List of orders
Identifier 5.2.2
Title Choose dress order
dress from the list.
Rationale To help user to see the order details
Dependencies N/A
Priority High
Table 142: List of orders
Identifier 5.2.2
Title View Dress Order
Requirement This will provide the user with the ability to see the details
of order
Rationale To help user to see details of order
Dependencies N/A
Priority High
Table 143: View Dress Order
UC-5.3: Edit order requirements
Identifier 5.3.1
Title Edit measurements
Requirement It will help Users to edit measurements before they place
the order
Rationale To help user to give measurements accurately
Dependencies N/A
Priority Medium
Table 145: Edit measurements
Identifier 5.3.2
Title Edit dress Model
Requirement It will help Users to edit Dress model
Rationale To help user to send correct Dress model
Dependencies N/A
Priority Medium
Table 146: Edit Dress Model
Identifier 5.3.3
Title Edit requirements
Requirement It will help Users to edit requirements for the dress
Rationale To help user to send correct requirement to the user
Restrictions and Risk There must be some requirements to edit
Dependencies N/A
Priority Medium
Table 147: Edit Requirements
UC-5.4: Cancel order
Identifier 5.4.1
Title Select order
Requirement User can select the order to cancel it
Rationale Without selecting the order it cannot be canceled
Dependencies N/A
Priority High
Table 148: View Select order
Identifier 5.4.2
Title Confirm Cancelation
Requirement It will allow user to cancel the order that is in progress or
in queue
Rationale To help user to change the tailor by canceling the order
Restrictions and Risk There should be one or more order in the list
Dependencies 5.3.1
Priority High
Table 149: Confirm Cancelation
UC-5.4: Ratings
Identifier 5.5.1
Title Show Stars
Requirement It will allow user to see 5 stars on the screen
Rationale To help user to give rating
Dependencies N/A
Priority Medium
Table 150: Show Stars
Identifier 5.5.2
Title Submit ratings
Requirement It will allow user to submit his rating about the work
Rationale To help user to give rating to the worker
Dependencies 5.5.1
Priority Medium
Table 151: Submit rating
UC-5.5: Order history
Identifier 5.5.1
Title View order History
Requirement It will allow user to see its previous orders
Rationale To help user to see completed orders
Dependencies N/A
Priority Medium
Table 152: View history
Identifier 5.5.2
Title Select Order
Requirement It will allow user to see the previous order details
Rationale To help user to see complete details of previous orders
Restrictions and Risk There must be one or more order in the list of history
Dependencies 5.4.1
Priority Medium
Table 153: Select Order
Identifier 5.5.3
Title Delete Order
Requirement It will allow user to Delete the Order
Rationale To help user to delete previous record
Restrictions and Risk There must be one or more order in the list of history
Dependencies 5.4.1
Priority Low
Table 154: Delete Order
UC-5.6: Choose Comments
Identifier 5.6.1
Title Show comments
Requirement It will display the comments on the screen
Rationale To select the comments
Dependencies N/A
Priority Medium
Table 155: Show comments
Identifier 5.6.2
Title Select comments
Requirement It will allow the user with the ability to select the
comments
Rationale To help user to submit the comments
Dependencies N/A
Priority Medium
Table 156: Select comments
UC-5.7: Order queue for tailors
Identifier 5.7.1
Title View Order queue
Requirement It will help User to see the order list that are pending
Rationale To help User to see pending orders
Dependencies N/A
Priority Medium
Table 157: View Order Queue
Identifier 5.7.2
Title Select Dress Order
Requirement It will help User to Select the Order from the list
Rationale To see the order details
Restrictions and Risk There must be one or more order in the list
Dependencies N/A
Priority Medium
Table 158: Select Dress Order
Identifier 5.7.3
Title View Order details
Requirement It will help User to see the complete details of the order
Rationale To see the order details
Restrictions and Risk There must be one or more order in the list
Dependencies 5.7.2
Priority Medium
Table 159: View Order Details
Module 6: Chat Box

UC-6.1: Send Text message
Identifier 6.1.1
Title Text Field
Requirement User will click on the text field and then write the text they
want to send.
Source Team Member 3 (Maida Shaheen)
Rationale User will be able to write the text they want to send.
Restrictions and Risk User should click on the text field to write.
Dependencies None
Priority Medium
Table 160: Text Field
Identifier 6.1.2
Title Send message
Requirement User will click on the send button to send the message they
have written.
Rationale User will be able to send the message they have written.
Restrictions and Risk User should enter the recipient before sending the message.
Dependencies None
Priority Medium
Table 161: Send Message
Identifier 6.1.3
Title Remove message
Requirement User will click on remove message button to remove a
particular message.
Rationale User will be able to remove the message they want.
Restrictions and Risk User should select a message to remove.
Dependencies 6.1.2
Priority Medium
UC-6.2: Send Dress Images Table 162: Remove Message
Identifier 6.2.1
Title Open Gallery
Requirement User will click on the open gallery button to view the
images from his/her gallery.
Rationale User will be able to view the image from the gallery in
order to send it.
Restrictions and Risk User should allow the application to access his/her gallery.
Dependencies None
Priority Medium
Table 163: Open Gallery
Identifier 6.2.2
Title Select Images
Requirement User will click on the open gallery button to view the
images from his/her gallery and then select it to send it.
Rationale User will be able to select the image from the gallery in
order to send it.
Restrictions and Risk User should allow the application to access his/her gallery.
Dependencies 6.2.1
Priority Medium
Table 164: Select Image
Identifier 6.2.3
Title Send Images
Requirement User will click on the send button to send the selected
image.
Rationale User will be able to send the selected image.
Restrictions and Risk User should select an image before clicking send button.
Dependencies 6.2.2
Priority Medium
UC-6.3: Send dress model Table 165: Send Images
Identifier 6.3.1
Title Open 3D Model Gallery
Requirement User will click on the open 3D Model gallery button to
view the models from gallery.
Rationale User will be able to view the 3D models from the gallery in
order to send it.
Restrictions and Risk User should click on the open 3D Gallery button.
Dependencies None
Priority Medium
Table 166: Open Model Gallery
Identifier 6.3.2
Title Select Category
Requirement User will click on a particular category to view the images
in the gallery.
Rationale User will be able select the category they want to send the
model from.
Restrictions and Risk User should click on the open 3D gallery button.
Dependencies 6.3.1
Priority Medium
Table 167: Select Category
Identifier 6.3.3
Title Select Model
Requirement User will click on a particular dress model to select for
sending purposes.
Rationale User will be able select the model he/she wants to send.
Restrictions and Risk User should click on the open 3D gallery button.
Dependencies 6.3.1, 6.3.2
Priority Medium
Table 168: Select Model
Identifier 6.3.4
Title Send Model
Requirement User will click on the send button to send the selected
model.
Rationale User will be able to send the selected model.
Restrictions and Risk User should select a model before clicking send button.
Dependencies 6.3.3
Priority Medium
UC-6.4: Place a Phone Call Table 169: Send Model
Identifier 6.4.1
Title Click on Call Icon
Requirement User will click on the call icon to initiate the call.
Rationale User will be able to place a phone call.
Restrictions and Risk User should select a recipient before initiating a call.
Dependencies None
Priority High
Table 170: Click on Call Icon
Identifier 6.4.2
Title Cancel Call
Requirement User will click on the cancel call button to cancel an
Initiated call.
Rationale User will be able to cancel an Initiated call.
Restrictions and Risk User should have initiated a phone call.
Dependencies 6.5.1
Priority High
Table 171: Cancel Call
Identifier 6.4.3
Title Mute Call
Requirement User will click on the mute voice button to mute his/her
audio in a call.
Rationale User will be able to mute his/her audio.
Restrictions and Risk User should have initiated an audio call.
Dependencies 6.5.1
Priority High
Table 172: Mute Call
Identifier 6.4.4
Title Unmute Voice
Requirement User will click on the unmute voice button to unmute
his/her audio in a call.
Rationale User will be able to unmute his/her audio.
Restrictions and Risk User should have initiated an audio call. And the user
should have muted the call earlier.
Priority High
Table 173: Unmute Voice
UC-6.5: Receive Text Message
Identifier 6.5.1
Title Accept Message
Requirement User will click on the accept button to allow the other user
to send him/her text messages.
Rationale User will be able to allow the other user to send him/her
text messages.
Restrictions and Risk User should have received a text message.
Dependencies None
Priority High
Table 174: Accept Message
Identifier 6.5.2
Title Reject Message
Requirement User will click on the reject button to block the other user
to send him/her text messages.
Rationale User will be able to block the other user to send him/her
text messages.
Dependencies None
Priority High
Table 175: Reject Message
Identifier 6.5.3
Title Display Message
Requirement User will click on the message in order to view it.
Rationale User will be able to view the message the other user sent
him/her.
Dependencies None
Priority High
Table 176: Display Message
UC-6.6: Receive a Phone Call
Identifier 6.6.1
Title Accept call
to phone call him/her.
Rationale User will be able to allow the other user to phone call
him/her.
Restrictions and Risk User should have received a phone call.
Dependencies 6.5.205
Priority High
Table 177: Accept Call
Identifier 6.6.2
Title Reject Call
to phone call him/her.
Rationale User will be able to block the other user to phone call
him/her.
Restrictions and Risk User should have received a phone call.
Priority High
Table 178: Reject Cal
Identifier 6.6.3
Title Mute Voice
Requirement User will click on the mute voice button to mute his/her
audio in a call.
Rationale User will be able to mute his/her audio.
Restrictions and Risk User should have received a audio call.
Dependencies None
Priority High
Table 179: Mute Voice
Identifier 6.6.4
Title Unmute Voice
Requirement User will click on the unmute voice button to unmute
his/her audio in a call.
Rationale User will be able to unmute his/her audio.
Restrictions and Risk User should have received an audio call. And the user
should have muted the call earlier.
Priority High
Table 180: Unmute Voice
UC-6.7: Receive Dress Images
Identifier 6.7.1
Title Accept images
to send him/her images.
images.
Restrictions and Risk User should have received an image.
Dependencies 6.2.3
Priority High
Table 181: Accept Images
Identifier 6.7.2
Title Reject images
to send him/her images.
images.
Restrictions and Risk User should have received an image..
Dependencies 6.2.3
Priority High
Table 182: Reject Images
Identifier 6.7.3
Title Open image
to send him/her images so he/she can view them.
Rationale User will be able to view images the other user have sent
him/her.
Restrictions and Risk User should have received images.
Dependencies 6.2.3
Priority High
Table 183: Open Image
UC-6.8: Receive Dress Models
Identifier 6.8.1
Title Accept Dress Models
to send him/her 3D models.
3D models.
Restrictions and Risk User should have received a 3D model.
Dependencies 6.3.3
Priority High
Table 184: Accept Dress Models
Identifier 6.8.2
Title Reject Dress Models
to send him/her 3D models.
3D models.
Restrictions and Risk User should have received 3D models.
Dependencies 6.3.3
Priority High
Table 185: Reject Dress Models
Identifier 6.8.3
Title Open 3D models
to send him/her 3D models so he/she can view them.
Rationale User will be able to view 3D models the other user have
sent him/her.
Restrictions and Risk User should have received 3D models.
Dependencies 6.3.3
Priority High
Table 186: Open 3D Models
Module 7: Notification
UC-7.1: View notification
Identifier 7.1.1
Title Show notification
Requirement User will be able to see the notification of his profile
Rationale All the notification of profile will be shown
Restrictions and Risk There must be some notification
Dependencies None
Priority medium
Table 187: Show notification
Identifier 7.1.2
Title Select notification
Requirement User will be able to select the notification of his profile
Rationale Notification will be selected
Restrictions and Risk There must be some notification
Dependencies None
Priority Medium
Table 188: Select notification
Identifier 7.1.3
Title Delete notification
Requirement User will be able to delete the notification of his profile
Rationale Notification will be deleted
Restrictions and Risk User must be selected one or more notification
Dependencies 7.1.2
Priority Medium
Table 189: Delete notification
UC-7.2: Send SMS on sing up and order placement
Identifier 7.2.1
Title Send SMS
Requirement User will get the SMS on sign up and order placement
Rationale Confirmation message will be delivered
Restrictions and Risk Must place order or sign up
Dependencies None
Priority medium
Table 190: Send SMS
UC-7.3: Push notification
Identifier 7.3.1
Title Slide Screen
Requirement User will be able to slide the screen to see the notification
Rationale To see the full notification
Dependencies None
Priority medium
Table 191: Slide Screen
Identifier 7.3.2
Title Setting
Requirement User will be able to open setting of notification
Rationale To open the setting of notification
Dependencies None
Priority medium
Table 192: Setting
Identifier 7.3.3
Title Mute or Unmute
Requirement User will be able to mute or unmute the notification
Rationale User will be able to mute or unmute coming notification
according to their need
Dependencies None
Priority medium
Table 193: Mute or Unmute
UC-7.4: Inbox request
Identifier 7.4.1
Title View request
Requirement User will be able to see the request messages
Rationale It will provide privacy to the user
Dependencies None
Priority medium
Table 194: view request
Identifier 7.4.2
Title Accept request
Requirement User will be able to chat with the person
Rationale It will provide the way to communicate with other user
Dependencies None
Priority Medium
Table 195: Accept request
Module 8: Service Recommender

UC-8.1: Rating Based Recommender
Identifier 8.1.1
Title Select Rating Based Recommendation
Requirement User will click the Rating Based Recommendations button
to select this category.
Rationale User will be able to select Rating Based Recommendation.
Restrictions and Risk User should have entered some requirements.
Dependencies None
Priority High
Table 197: Select Rating Based Recommendation
Identifier 8.1.2
Title View Rating Based Recommendation
Requirement User will click the Rating Based Recommendations button
to view this category.
Rationale User will be able to view Rating Based Recommendation.
Dependencies None
Priority High
UC-8.2: Budget based: Table 198: View Rating Based Recommendation
Identifier 8.2.1
Title Select Budget Based Recommendation
Requirement User will click the Budget Based Recommendations button
to select this category.
Rationale User will be able to select Budget Based Recommendation.
Dependencies None
Priority High
Table 199: Select Budget Based Recommendation
Identifier 8.2.2
Title View Budget Based Recommendation
Requirement User will click the Budget Based Recommendations button
to view this category.
Rationale User will be able to view Budget Based Recommendation.
Dependencies None
Priority High
Table 200: View Budget Based Recommendation
UC 8.3: View Recommendations
Identifier 8.3.1
Title Select filter
Requirement User will select a filter for recommendations.
Rationale User will be able to select a filter for certain
recommendations.
Dependencies None
Priority High
Table 201: Select Filter
Identifier 8.3.2
Title View Recommendation
Requirement User will select a recommendation to view.
Rationale User will be able to view the selected Recommendation.
Dependencies 8.3.1
Priority High
Table 202: View Recommendation
UC 8.4: Aggregate Recommendations
Identifier 8.4.1
Title Select recommender
Requirement User will be able to select the recommender
Rationale Recommender will be selected for view purpose
Dependencies None
Priority High
Table 203: Select recommender
Identifier 8.4.2
Title View recommender
Requirement User will be able to view the recommender
Rationale User will be able the recommender
Dependencies None
Priority High
Table 204: View recommender
Module 9: Help and Support
UC-9.1: About Application

Identifier 9.1.1
Title View Page
Requirement User will click on the About Application button to view the
page.
Rationale User will be able to view the About Application.
Restrictions and Risk None.
Dependencies None
Priority Medium
Table 205: View Page
Identifier 9.1.2
Title Page up
Requirement User will click on page up button to view the upper side of
the page.
Rationale User will be able to view the upper side of the page
Restrictions and Risk User should have opened the about page.
Dependencies 9.1.2
Priority Low
Table 206: Page up
Identifier 9.1.3
Title Page down
Requirement User will click on page down button to view the lower side
of the page.
Rationale User will be able to view the lower side of the page
Dependencies 9.1.2
Priority Low
Table 207: Page Down
Identifier 9.1.4
Title Previous Page
Requirement User will click on previous page button to view the
previous page.
Rationale User will be able to view the previous page
Dependencies 9.1.2
Priority Low
Table 208: Previous Page
Identifier 9.1.5
Title Next Page
Requirement User will click on next page button to view the previous
page.
Rationale User will be able to view the next page
Dependencies 9.1.2
Priority Low
Table 209: Next Page
Identifier 9.1.6
Title Update Info
Requirement Admin will click on the update info button.
Rationale User will be able to update the information in the about
application page.
Restrictions and Risk There should be an existing about application page to edit.
Dependencies 9.1.2
Priority Medium
UC-9.2: Contact Us Table 210: Update Info

Identifier 9.2.1
Title Report a Problem
Requirement User will click on the report a problem button.
Rationale User will be able to report a problem
Restrictions and Risk User should have clicked the contact us button
Dependencies None
Priority Low
Table 211: Report a Problem
Identifier 9.2.2
Title Suggestions
Requirement User will click on the give suggestions buttons.
Rationale User will be able to give suggestions about the application.
Restrictions and Risk User should have clicked the contact us button.
Dependencies None
Priority Medium
Table 212: Suggestions
Identifier 9.2.3
Title User Feedback About Application
Requirement User will click on the give Feedback buttons.
Rationale User will be able to provide feedback about the
application.
Dependencies None
Priority Medium
Table 213: User Feedback about Application
Identifier 9.2.4
Title Display Contact
Requirement User will click on view contact button.
Rationale User will be able to view contact.
Dependencies None
Priority Medium
UC-9.3: FAQs Table 214: Display Contact
Identifier 9.3.1
Title View FAQs
Requirement User will click on the FAQs buttons.
Rationale User will be able to view the FAQs.
Restrictions and Risk User should have clicked the FAQs button.
Dependencies None
Priority Medium
Table 215: View FAQs
Identifier 9.3.2
Title Add New FAQs
Requirement User will click on the Add FAQs buttons.
Rationale User will be able to Add new FAQs.
Restrictions and Risk User should have signed in as an admin.
Dependencies None
Priority Medium
Table 216: Add New FAQs
Identifier 9.3.3
Title Edit FAQs
Requirement User will click on the edit FAQs buttons.
Rationale User will be able to edit the existing FAQs.
Dependencies None
Priority Medium
Table 217: Edit FAQs
Identifier 9.3.4
Title Delete FAQs
Requirement User will click on the delete FAQs buttons.
Rationale User will be able to delete the existing FAQs.
Dependencies None
Priority Medium
Table 218: Delete FAQs
Identifier 9.3.5
Title Search FAQs
Requirement User will click on the search FAQs buttons.
Rationale User will be able to search the FAQs.
Dependencies None
Priority Medium
Table 219: Search FAQs
UC-9.4: Report a Problem
Identifier 9.4.1
Title Text Body
Requirement User will click on text body to type the problem.
Rationale User will be able to type the problem.
Restrictions and Risk User should have clicked the Report a problem button
Dependencies None
Priority Medium
Table 220: Text Body
Identifier 9.4.2
Title Send Images
Requirement User will click on send images button to attach images.
Rationale User will be able to send images to the admin.
Restrictions and Risk User should have clicked the Report a problem button.
Dependencies None
Priority Medium
Table 221: Send Images
Identifier 9.4.3
Title Send files
Requirement User will click on send files button to attach files.
Rationale User will be able to send files to the admin.
Restrictions and Risk User should have clicked the Report a problem button.
Dependencies None
Priority Medium
Table 222: Send Files
UC-9.5: Textual Guidelines
Identifier 9.5.1
Title Display guide
Requirement User will click on guideline to view it.
Rationale User will be able to view the guidelines.
Restrictions and Risk User should have opened the guideline page.
Dependencies None
Priority Low
Table 223: Display Guideline
Identifier 9.5.2
Title Select Language
Requirement User will click on the language button to select the
preferred one.
Rationale User will be able to select the language of the guideline.
Dependencies 9.5.1
Priority Low
Table 224: Select Language
Identifier 9.5.3
Title Page up
Requirement User will click on page up button to view the upper side of
the page.
Rationale User will be able to view the upper side of the page
Dependencies None
Priority Low
Table 225: Page up
Identifier 9.5.4
Title Page down
Requirement User will click on page down button to view the lower side
of the page.
Rationale User will be able to view the lower side of the page
Dependencies 9.1.2
Priority Low
Table 226: Page Down
Identifier 9.5.4
Title Previous Page
Requirement User will click on previous page button to view the
previous page.
Rationale User will be able to view the previous page
Dependencies 9.1.2
Priority Low
Table 227: Previous Page
Identifier 9.5.5
Title Next Page
Requirement User will click on next page button to view the previous
page.
Rationale User will be able to view the next page
Dependencies 9.1.2
Priority Low
UC-9.6: User Feedback Table 228: Next Page
Identifier 9.6.1
Title Comments
Requirement User will click on comments button.
Rationale User will be able to comments about the application.
Restrictions and Risk User should have clicked the feedback button.
Dependencies None
Priority Low
Table 229: Comments
Identifier 9.6.2
Title Stars
Requirement User will click on stars.
Rationale User will be able to rate the application out of five stars.
Restrictions and Risk User should have clicked the feedback button.
Dependencies None
Priority Low
Table 230: Stars
Identifier 9.6.3
Title Submit
Requirement User will click on submit button.
Rationale User will be able to provide his/her feedback about the
application.
Restrictions and Risk User should have filled the stars and comment section.
Priority Low
Table 231: Submit
UC-9.7: Suggestion
Identifier 9.7.1
Title Text Body
Requirement User will click on text body to type the suggestion.
Rationale User will be able to type the suggestion.
Restrictions and Risk User should have clicked the Suggestion button
Dependencies None
Priority Medium
Table 232: Text Body
Identifier 9.7.2
Title Submit
Requirement User will click on submit button.
Rationale User will be able to provide his/her suggestion about the
application.
Restrictions and Risk User should have filled the text body.
Dependencies 9.7.1
Priority Low
UC-9.8: Admin Response Table 233: Submit
Identifier 9.8.1
Title Select Feedback
Requirement User will click on feedback button.
Rationale User will be able to select the user feedback category.
Restrictions and Risk User should have signed in as admin.
Dependencies None
Priority Low
Table 234: Select Feedback
Identifier 9.8.2
Title Select Suggestion
Requirement User will click on Suggestion button.
Rationale User will be able to select the Suggestion category.
Dependencies None
Priority Low
Table 235: Select Suggestion
Identifier 9.8.3
Title Select Reported problems
Requirement User will click on Reported problems button.
Rationale User will be able to select the Reported problems category.
Dependencies None
Priority Low
Table 236: Select Reported Problems
Identifier 9.8.4
Title View Feedback
Requirement User will click on feedback button.
Rationale User will be able to view the user feedback category.
Dependencies None
Priority Low
Table 237: View Feedback
Identifier 9.8.4
Title View Suggestion
Requirement User will click on Suggestion button.
Rationale User will be able to View the Suggestion category.
Dependencies None
Priority Low
Table 238: View Suggestion
Identifier 9.8.5
Title View Reported problems
Requirement User will click on Reported problems button.
Rationale User will be able to view the Reported problems category.
Dependencies None
Priority Low
Table 239: Select Reported Problems
Identifier 9.8.6
Title Admin Reply for Feedback
Requirement User will click on reply button.
Rationale User will be able to reply to the user feedback.
Dependencies None
Priority Medium
Table 240: Admin Reply for Feedback
Identifier 9.8.7
Title Admin Reply for Suggestions
Rationale User will be able to reply to the user Suggestions.
Dependencies None
Priority Medium
Table 241: Admin Reply for Suggestions
Identifier 9.8.8
Title Admin Reply for reported problems
Rationale User will be able to reply to the reported problems.
Dependencies None
Priority Medium
Table 242: Admin Reply for Reported Problem
6. Non-functional Requirements
Following are the NFRs for the system.
6.1. Performance Requirements
Following are some of the performance requirements of this system.

6.1.1. Response Time
System average response time will be 2ms and maximum should be 8ms
6.1.2. Throughput
It will be able to respond quickly to user action. There should be less delay i.e. 2ms in
fetching data from database
6.1.3. Capacity
It will be able to accommodate more than 10 thousands user data.
6.2. Reliability
Following is the reliabilities of our system.
6.2.1. Availability
System should be available 24/7
6.2.2. Usability
User will be master of using application in 1 day using our textual guide
6.3. Design Constraints
Following are the design constraints of our system.
6.3.1. Android Studio
It is programming language that will be used to develop the application for android
6.3.2. Mongo DB
It is programming language that will be used to develop the database for system
6.4. Accuracy and Precision
There are no precision requirements needed for this application. The accuracy of data is needed. The
content being uploaded needs to be accurate because it is very critical when user customized the dresses
6.5. Portability
• Person effort to move system is 50%.
• Modules can be changed up to 50% which can make system easy to port.
6.6. Security
System will have password encryption rule that is user password will be encrypted and saved the
hash of the password in database and when user login again the hash from data base and password
from user will be compare.
7. Gantt chart
Figure 1: Gantt chart
8. Conclusion
This document will help the developer and customer to understand the whole application via
documentation, it will help him to know about the modules, what this project is going to do and what will be the
process behind the development phase.
9. References
Web links:
• https://play.google.com/store/applications/details?id=in.vining.tailormaster&hl=en
• https://alternativeto.net/software/tailor/
• https://www.producthunt.com/alternatives/tailor-3
Book links:
SOFTWARE ENGINEERING, Ninth Edition, Ian Sommerville
• https://edisciplinas.usp.br/pluginfile.php/2150022/mod_resource/content/1/1429431793.203Soft
ware%20Engineering%20by%20Somerville.pdf
Software Engineering A Practitioner’s Applicationroach, seventh edition, roger s. pressman, Ph.D.
• http://dinus.ac.id/repository/docs/ajar/RPL-
7th_ed_software_engineering_a_practitioners_applicationroach_by_roger_s._pressman_.pdf
10.Plagiarism Report

Stichit SRS

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

Stichit SRS

Uploaded by

Copyright:

Available Formats

COMSATS University Islamabad,

Park Road, Chak Shahzad, Islamabad Pakistan

Software Requirements Specification

Submission Date: 3rd October, 2019

Original Version 1.0

Bachelor of Science in Computer Science (2016-2020)

Department of Computer Science 1

1.1. Document Purpose

1.2. Product Scope

1.3. Intended Audience

CNIC Computerized National Identity Card

2.1. Product Perspective

2.2. Product Functions

2.3. User Characteristics

2.4. Operating Environment

2.5. General Constraints

3. Requirement Elicitation Techniques.

Module 1: User Profiling

Module 3: Book My Dress

Module 4: AR Dress Design

Module 5: Order Details

Module 8: Service Recommender

Module 9: Help and Support

Sign in Reject Dress Order

Forget pd Edit requirement

Figure 4.1.1: Tailor Use Case Diagram(1/3)

Figure 4.1.2: Tailor Use Case Diagram (2/3)

Send Dress Models

Figure 4.1.3: Tailor Use Case Diagram (3/3)

Send Order forget pasword

3D Dress Models User profiling

Figure 4.1.4: Customer Use Case Diagram (1/4)

Receive Video Ratings

Figure 4.1.5: Customer Use Case Diagram (2/4)

ViewTailor Profile Zoom In

Figure 4.1.6: Customer Use Case Diagram (3/4)

Notifications Report a problem

Figure 4.1.7: Customer Use Case Diagram (4/4)

User Profiling AR Dress Design

Figure 4.1.8: Admin Use Case Diagram(1/1)

Module 1: User Management

Use Case ID: UC-1.1

Use Case ID: UC-1.2

Includes: UC: 1.1, 1.2

Use Case ID: UC-1.3

Use Case ID: UC-1.4

Use Case ID: 1.5

Use Case ID: 1.6

Use Case ID: 1.7

Use Case ID: 1.8

Use Case ID: 1.9

Use Case ID: UC-2.1

Use Case ID: UC-2.2

Use Case ID: UC-2.3

Description: This will allow user to Customize the 3D Dress model.

Use Case ID: UC-2.4

Alternative 1. User will select the gallery from Side Menu

Use Case ID: UC-2.5

Use Case ID: UC-2.6

Use Case ID: UC-2.7

Description: User will be able to add new dress categories

Use Case ID: UC-2.8

Description: User will able to select the 3D dress design.