CHAPTER not know which outfit is suitable

 

 

 

 

 

 

 

 

 

 

 

 

 

CHAPTER 1

 

1.1       INTRODUCTION

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

This chapter contains the background, problem statement, objectives,
system and user scope, and project timeline.

 

1.2       BACKGROUND

WhatToWear? is a wardrobe management application designed for
general users that have problems in choosing their outfit to go to an event.
This application will recommends outfits for its users for any events. This
application has been developed on a website platform. The users have to insert
their physical features and the information of the events that they will go and
the application will determine which outfit will suit the users.

 

1.3       PROBLEM
STATEMENT

Choosing clothes from wardrobe is quite a time consuming for people
who does not have any idea on what to wear for an event or does not know which
outfit is suitable for the respective event. Nowadays, people live in a hectic
world and cannot afford to make a mistake including choosing the wrong outfits
for events.

 

1.4       OBJECTIVES

The objectives of the application are:

1.      To
help users wear an appropriate outfit for an event

2.      To
guide users to not wear the same kind of clothing only

3.      To
assist users in experimenting with different type of attires

 

1.5       SCOPE

The scope of the project explain the limitation for the system and
the user.

 

1.5.1    SYSTEM SCOPE

·        
Retrieve the user’s
physical features

·        
Retrieve the event’s
information

·        
Display the appropriate
attire for the users

·        
Store all data on
database which is the outfits and user’s information

 

1.5.2    USER
SCOPE

·        
Administrator

o   Can
manage the user’s database  and outfit’s
database

·        
Registered users

o   Can
insert physical features information

o   Can
insert event’s information

o   Can
save own results

 

 

1.6       PROJECT
TIMELINE

The project
timeline used for this project is shown in Table 1.1 below.

 

Table 1.1: WhatToWear? Gantt Chart

Task

1

2

3

4

5

6

7

8

9

10

11

12

13

14

Proposal draft

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Executive
summary

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Preparing
chapter 1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Preparing
chapter 2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Conduct a survey

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Progress 1
submission

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Chapter
3(Design, ERD)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Poster design

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Poster
presentation

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Progress 2
submission

 

 

 

 

 

 

 

 

 

 

 

 

 

 

                                                          CHAPTER 2                      

 

ANALYSIS & SYSTEM
REQUIREMENTS

 

2.1       INTRODUCTION 

This chapter contains the review of similar systems, comparisons
between those similar system and WhatToWear? system, new process flow, software
development methodology, requirement gathering techniques and tools and
technology.

 

2.2       REVIEW OF SIMILAR SYSTEM

2.2.1 HOMYFADS WARDROBE MANAGER (http://homyfads.sunlitgreen.com/)

Figure 2.1 HomyFads main menu

HomyFads Wardrobe Manager is a
virtual wardrobe software. With HomyFads Clothing Organizer users can sort
their collection by type, add comments and browse and search through their
collections of apparel and accessories. Users can tag each item of clothing
with all kinds of data – purchase date, color, size, material, cost, location
and many more. These data let users quickly search and sort through their
collection. For example, if they wish to wear something black they can just
type ‘black’ and get a list of every black items you own.

 

Advantages

·        
The users can do a quick search for clothes their desired clothes.

·        
The users can sort their clothes collection into many categories

Disadvantages

·        
No advice from expert whether the outfit is appropriate for the user.

2.2.2          CLOSET COUTURE (http://www.closetcouture.com/)

Figure 2.2 Closet couture main menu

 

Closet couture is a virtual closet aimed at women. Users can upload
pictures of their clothes and the site lets the users remove the background.
Users can then try the clothes out on a virtual model. This works with clothes
they own and clothes they might want to purchase, so users can mix, match, then
buy what they do not have. One of its feature
is that it has a network of stylists that can improve the users look for a fee.
They take a look at their user’s picture and virtual wardrobe and advise them
what to wear and buy.

 

Advantages

·        
The users can try the
picked clothes on virtual model provided from the application.

·        
The users can get
advice from stylists about their fashion.

 

Disadvantages

·        
The application is
aimed only for women.

·        
This application has
fees for advice from the stylists.

 

 

2.2.3    TOUCHCLOSET
(http://itunes.apple.com/app/touchcloset/id299230498)

Figure 2.3 TouchCloset main menu

TouchCloset is an iPhone/iPod
touch app that lets users take their wardrobe to the streets. Users upload
photos to an online account, organize their closet and put together outfits for
different occasions. This is pretty useful when the users are shopping.

 

Advantages

·        
The users can do a quick search for clothes their desired clothes.

·        
The users can sort their clothes collection into many categories.

 

Disadvantages

·        
There is no advice from expert whether the outfit is appropriate for the
user.

 

 

 

 

 

 

 

 

 

 

 

 

 

2.2.4    COMPARISON BETWEEN SIMILAR SYSTEM AND
PROPOSED SYSTEM

The comparison between Homypad Wardrobe Manager, Closet
Couture, TouchCloset and WhatToWear? is shown on table 2.1 below.

Table 2.1: Comparison between similar system and proposed
system

Features

Homypad

Closet Couture

TouchCloset

WhatToWear?

Log In

YES

YES

YES

YES

Specialist’s Help

NO

YES

NO

YES

Aimed For Both Gender

YES

NO

NO

YES

Can save result

YES

YES

YES

YES

Include Accessories

YES

NO
 

NO

YES

 

 

 

 

 

 

 

 

 

 

 

 

2.3       NEW
PROCESS FLOW

The process flow
for WhatToWear? system is shown on figure 2.4 below

                                                       

a

 

 

 

 

a

 

Figure 2.4: WhatToWear? process flow

The user first need to register or log in if they already has an
account in order to use this application. Then, they have to insert their age
and gender. After that, they need to insert their physical information such as
height, build, complexion, and their hair style. Then, they need to insert the
event’s information that they need to attend such as type of event, time of the
event, their event’s venue, their event’s lighting and the weather condition.
The users then will submit the information and the system then will proposed
the suitable outfit for the users based on the information given. The users
then will be given a choice whether to save their outfit result. Lastly, the
users can log out from the system.

 

 

 

 

2.4       SOFTWARE
DEVELOPMENT METHODOLOGY

The software development methodology used for this project is the
Waterfall. This is an efficient way to use because this method has a process
flow downward to the linear motion and that the forwarding phase only start
when the first phase has finished.

 

 

 

 

 

 

 

 

 

 

 

Figure 2.5: Waterfall diagram example

 

 

 

 

 

 

 

 

 

 

2.4.1    REQUIREMENT GATHERING AND ANALYSIS

 Firstly, all information from
people from various background are gathered using 10 survey questions in order
to ensure that the WhatToWear? system meet user requirement. Then, all of the
collected data are analyzed and evaluated using pie charts so that the users’
need could be truly understand and in order for the system to be fully
developed.

 

2.4.2    SYSTEM DESIGN

Equipped with the user requirement data collected earlier, the
system now can be designed by developers that will fit what is expected from
the user, especially in terms of the front – end design and user interface. The
tools that would be used are Wampserver as server, PhpMyAdmin which is a
database management software to manage user’s and outfit’s database and Adobe
Dreamweaver to create the interface. The finish constructed design of the
system is used in the implementation phase.

 

2.4.3    IMPLEMENTATION

Developers are now performing and executing the actual development
of the system. WhatToWear? system codes and algorithm are created and tested in
different unit and parts to ensure that every functionalities of the system are
running according to plan using the tools that was planned to use in the system
design phase.

 

 

 

 

 

2.4.4    TESTING

All the previous unit are integrated into one system to ensure that
the WhatToWear? functionality could work together and connected under one
system flow . Then the developer conducted User Acceptance Testing which is the
actual software users test the software to make
sure it can handle required tasks in real-world scenarios, according to the specifications

 

2.4.5    INSTALLATION AND DEPLOYMENT

After the overall system testing was a success, the system now is
installed in the user’s computer .In this case, WhatToWear?, which is a
web-based system can be view by the users on their internet browser.

 

2.4.6    MAINTENANCE

Developers will solve some defects and problems from WhatToWear?
system overtime and users might experience difficulties around the interface
which mean for more enhance and update.

 

 

 

 

 

 

 

 

 

2.5       REQUIREMENT GATHERING TECHNIQUES       

Distributing surveys related to the current and proposed system will
be used for gathering requirements to design the application. There were 35
respondents answered to the survey and they are from people from various
background.

Figure 2.6 Survey’s question 1

 

Based on
question above, most respondents are female. Therefore WhatToWear? target
audience are mostly females.

 

 

 

 

 

Figure 2.7 Survey’s question 2

 

Based on
question above, most respondents came from age 18 – 24 years old. Therefore WhaToWear?
target audience are mostly comes from age 18 – 24.

 

Figure 2.8 Survey’s question 3

 

Based on
question above, most respondents are having difficulties in finding the right
outfit in any event.

Figure 2.9 Survey’s question 4

 

Based on
question above, most respondents are sometimes having difficulties in finding
the right outfit for any event

Figure 2.10 Survey’s question 5

 

Based on
question above, most respondents are not sure whether ther have wore the
incorrect style for an event

Figure 2.11 Survey’s question 6

 

Based on
question above, most respondents like to shop for new clothes online. Therefore
they would likely to use WhaToWear? application

 

Figure 2.12 Survey’s question 7

 

Based on
question above, most respondents buy new clothes several times per month

Figure 2.13 Survey’s question 8

 

Based on
question above, most respondents are not sure whether they have knowledge about
fashion

 

Figure 2.14 Survey’s question 9

 

Based on
question above, most respondents know the current fashion trends but did not
really follow them

Figure 2.15 Survey’s question 10

 

Based on
question above, most respondents would like to use if there is an application
that will help them to find the right outfit for an event

 

 

2.6       TOOLS AND TECHNOLOGY

The tools that would be used to create WhatToWear? systems are:

1.      Wamp
Server as the server to connect between the system and the databases

2.      PhpMyAdmin
which is a database management software to manage user’s and outfit’s database.

3.       Adobe Dreamweaver as a tool create the
system’s interface.

CHAPTER 3

 

DESIGN

 

3.1       DATABASE DESIGN

This chapter contains the entity-relation diagram which is Use Case
Diagram and Data Dictionary for WhatToWear?

 

3.1.1    ENTITY-RELATION DIAGRAM

The explanation of the entity-relation diagram for WhatToWear? are:       

1.      The
users can create an account to use the application.

2.      The
users can log in into the system to use the application while the administrator
can log in into the system to manage the user’s account and to manage the
selection of clothes generated by the system to the users.

3.      The
users can insert their physical and event information.

4.      The
users can view their results and also their previous results that were saved.

 

Figure 3.1 WhaToWear? Use Case Diagram

3.1.2    DATA DICTIONARY (RELATIONS AND ATTRIBUTES)

The Data Dictionary for WhaToWear? are:

Table 3.1 WhatToWear? Data Dictionary

No.

Entity Description

Attribute

Attributes
Description or Comments

1.

User:
A user can be anyone in the community

username
password

Varchar (30)
Varchar (15)

2.

Top:
Top is the user’s item of clothing that covers at
least the chest, but which usually covers most of the upper body between the
neck and the waistline.

top id
colour
name
picture

Int (100)
Varchar (100)
Varchar (100)
Mediumblob

3.

Bottom:
Bottom is the user’s item of clothing that usually
covers most of the lower body between the hip and the leg.

bottom id
colour
name
picture

Int (100)
Varchar (100)
Varchar (100)
Mediumblob

4.

Shoe:
A covering for the user’s
foot

shoe id
colour
name
picture

Int (100)
Varchar (100)
Varchar (100)
Mediumblob

5.

Accessories:
An item used to contribute,
in a secondary manner, to the user’s outfit, often used to complete an
outfit and chosen to specifically complement the user’s look

accessories id
colour
name
picture

Int (100)
Varchar (100)
Varchar (100)
Mediumblob

6.

Save results:
User’s saved result of their outfit

username
date

Int (100)
Date

 

3.2       EARLY MOCK UP APPLICATION INTERFACE
DESIGN

Figure 3.2 WhatToWear? Home Page

 

This is the home page of the system. Registered users
must log in using their username and password and then click on the ‘Login’
button to use the application. After log in, users will be lead to the main
page. Users who use the application for the first time must sign up by clicking
the ‘Register Here’ button at the bottom right of the page.

Register

Figure 3.3 WhatToWear? Register Page

 

This  is the
register page. Unregistered users must first register themselves with an
username of their choice and their password and click the ‘Register’ button
before it can be used to log in into te application. Pressing the register
button will lead the users back to the log in page.

 

Figure 3.4 WhatToWear? Main Page

 

Submit

Figure 3.5 WhatToWear? Main Page

 

This is the main page of the system. The users have to insert their
age, gender, physical information, and event information and then click on the
‘Submit’ button at the bottom of the page in order for the system to propose
the suitable outfit for the users based on the information given.

 

Log Out

Save

Figure 3.6 WhatToWear? Result Page

This is the result page. The suitable outfit that was proposed by
the system for the users is showed on this page. The users is given the choice whether
to save their results by clicking on the ‘Save’ button. The users then can log
out from the system by clicking the ‘Log Out’ button.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CHAPTER FOUR

 

CONCLUSION

 

4.1       INTRODUCTION

This chapter contains the outcome of Final Year Project 1, problems
encountered during Final Year Project 1 period, and future planning for Final
Year Project 2.

 

4.2       OUTCOME OF FINAL YEAR PROJECT 1

This Final Year Project 1 has begun during Semester 2 2017/2018. WhatToWear?
project was proposed to Puan Rina binti Md Anwar, as the project supervisor
during the second week of the semester. 10 survey questions were given in order
for the project to meet the users’ requirement. During week 8 until 12, project
poster and project prototype were developed by project developer to be
evaluated on week 13. Project report, which consists of executive summary,
Chapter 1, Chapter 2, Chapter 3, and Conclusion was submitted on week 14 to
project’s supervisor and examiner. Overall, this project was done with ease and
has met its requirements.

 

 

 

 

 

 

4.3       PROBLEMS ENCOUNTERED

The whole project was done with ease although the timeline of the
project was not followed properly. There has been many obstacles while doing
the project such as meeting deadlines, compiling ideas, developing the system
codes and even dealing with the report itself. Such obstacles had been dealt
with one by one and it was a slow process. In the end, it all comes together.

 

4.4       PLANNING FOR FINAL YEAR PROJECT 2

This application will be updated from time to time. All features
will be taken into account and it will be implemented into the application
within the deadlines.

REFERENCE

 

1.      http://www.instantfundas.com/2010/07/5-best-wardrobe-management-software-for.html