CHAPTER ONE

INTRODUCTION

1.0 Introduction

Online Tailoring Management System is a system aimed to assist in management of

tailoring activities within the industry. It will provide online services to customers

such as measurement submission to their tailors, check whether their garments are

finished and help in proper keeping of records. This will ensure availability of right

information, information safety, easy storage, access and retrieval. The study aims at

building a computerized tailoring management system that would be more effective

and efficient than the existing manual system

1.1 Background information

Tailoring has been known to dominate by unlearned people. It has been seen as a

profession for the dropouts in the Kenyan systems and elsewhere. Tailors use

traditional manual systems to book in their clients. The clients have to travel to

location of the tailor shop to get their measurement taken. These measurements are

written on papers or books. A method pose a high threat in terms of security of their

information i.e., can get lost, unauthorized people can easily access the information,

data confidentiality and integrity not maintained. No proper backups and the system

is tedious. Online tailoring management system will solve all these problems,

automate the tailor shops, and enhance accessibility irrespective of geographical

locations provided there is internet.

1
1.2 Aim of the study

The project is aimed to automate the tailoring sector, which is manually maintained.

After the automation, this will mean better services and good keeping of records, data

integrity, data security, quick search and paperless environment. The project has

mainly tackled management of information for the customers and in decision-

making.

Every user of the system will have to log into the system using username and

password so that security and authentication will be ensured. Once logged in, a

customer can make and order, check dress status or even give feedback. The system

administrator is able to manage customer information and update records.

1.3 Objectives of the Study

1. Automate the current manual tailoring system and maintain a searchable

customer, product.

2. To enable customers to send their measurements to their tailors for their clothes

to be made.

3. To provide information about the cost, of material to be used and quantity in

terms of pairs needed.

4. To compute the total of material, quantity and duration and avails that

information to the customer.

5. To enable report generation

6. To create a data bank for easy access or retrieval of customer details, orders

placed and the users who registered to the system.

2
1.4 Problem Statement

Currently customers have to walk to the tailor shops to get their measurements taken

for the tailoring of their garments. Their details are taken and kept on papers.

Customers too need to move from their offices to go and check for the clothes

whether there complete or not. This is time consuming and costly. Due to the manual

systems in use, the whole process tends to be low. Customers too have no prior

information on cost of netting their garments.

1.5 Proposed Solution

The proposed online tailoring management system will eliminate all these manual

intervention sand increase the speed of the whole process. The system will allow

customers to register online and successfully submit their measurements. The system

has inbuilt validation system to validate the entered data. The customer can login

tithe system to check on the status of the clothes for collection. The system will show

the already completed garments for clients to collect. The system also provides

information about the cost of each garment the customer intends to be knit. This data

will be stored in the database for further reference or audit.

1.6 Justification

Online Tailoring management system will break the geographical barriers and bring

the whole process into a quick and easy way to access tailors. It will automate the

traditional tailoring system into a modern computerized system. This will enhance

data retrieval, storage and security. It is also cost effective since it will cut down on

travelling cost to get your measurements taken and also going to check if your clothe

has been made and is ready for collection. The clients can access their online tailors

3
24/7 and at any location provided, they are connected tithe internet. Due to the

advancement in telecommunication e.g. undersea cabling, internet-accessing speed is

expected to double as the cost reduces. This will make this system more efficient to

use and offer competitive edge in the market.

1.7 Scope of the Study:

The Online Tailoring Management System will permit to register and deliver

measurements tithe tailor for the next process to follow.

It also maintains clients’ information and generating various reports about the tailor

shop. The main users of the project are clients and system Administrator. It also

enables customers to check the status of their garments i.e. if ready or not for

collection. The system provides information about the cost, the fabric type the

customer want his/her dress knit from, the duration a customer wants the dress

finished, the type of material to be used, quantity in terms of pairs needed and most

importantly, the system computes the total cost and avails that information to the

customer. However, online payment has not been achieved, but the customer is

expected to pay either immobile money transfer services like m-peas, papal or cash

when they come to pick their clothes.

4
 CHAPTER TWO

LITERATURE REVIEW

2.0 Introduction

Online tailoring management system is a web-based system, which made up of

independent components or web pages, working together for a common purpose.

Such systems are available on the internet for the users to accomplish some purpose.

James (2019) defined internet as a system, which provides an opportunity to millions

of people to get access to a large amount of stored data and connected to each other

despite distances.

Increased rate of satisfaction to recognize the need for better-quality cloths design

and samples. With the advancement of information technology, online tailoring

system emerged as an important output for efficient and timely delivery of quality

design and services. Earlier, tailoring requests are used manually but with the

advancement of technology and internet, the trend changed towards the proper online

tailoring systems.

A tailor is a person that makes, repairs, and alters garments such as suits, coats, and

dresses. (answers.com, 2012)

A tailor makes custom cloths wear of various styles like jackets, skirts or trousers

that go with them, for men or women. An alteration is a person who specials in

adjusting the fit of completed garments, usually ready-to-wear, or restyles them.

Designers is the one who choose combinations of line, proportion, color, and texture

for intended garments. They may have no sewing or patternmaking skills, and may

5
only sketch or conceptualize garments. ( Lancaster, 2013)

2.1 Origins of the Term Bespoke tailoring

According to Poole (1846), the term bespoke arose when in the old days; a customer

would choose a bolt of cloth in a tailor’s shop, whereupon the tailor would mark it as

being “bespoken for”. It has come to mean a traditional form of tailoring in which a

uniquely individualized pattern drafted for each client, and the optimal traditional

tailoring technique used to realize the shape of the final garment. The two principle

reasons for bespoke tailored clothing are as follows:

 Difficulty attaining a good fit from ready-to-wear garments

 Access to a wider range of styles and

cloth designs (Poole, 1846)

According to English Hardy (2003), a good tailor should be able to overcome all of

the potential shortcomings, and not only create a masterpiece that fits, but should also

guide his client towards a style that is better suited to his/her body. He says that a

skilled tailor can make simple clothing from common cloth, but with time and

practice they can learn to create garments of great beauty that provide significant

protection to their wearer. (Hardy, 2013)

2.2 Developments in Tailoring Industry

In Uganda, there has been development of tailoring school where a total number of

50 students are enrolled. They also currently employ four staff members who are

specialized in different areas of dressmaking and designing. During the last two

years, 58 students have successfully graduated from this institution, some of which

6
have chosen to team up in order to start up their own businesses. The school strongly

encourage students to form teams, since it is easier for a group than for a single

individual to handle the challenges of establishing an own business. (Margaret, 2011)

According to Richard (2012), he brought a rebellious streak to the heritage of suit

making; he has become a pillar of the modern menswear establishment. His bold

color and innovative twists have proved irresistible to the rock n' roll elite.

Modernization of the style and approach of the traditional tailors to current designs

has brought increased profits, time wastage and reduced the number of tailors who

depended on traditional technologies within the Savile Row in London (Ozwald et.al,

2013).

According to Shaw (2001), he says that the only man who behaves sensibly is his

tailor shop is the one who takes his measurements anew every time he sees me, while

all the rest go on with their old measurements and expect me to fit them.(Shaw,

2001).

2.3 Becoming a Twenty-First Century Tailor Shop

The growth of online retail and advances in web technologies has enabled smaller

bespoke manufacturers to re brighten cottage industry practices to reach global

audiences. Bespoke industries are experiencing a strong resurgence with the advent

of collective digital market places such StanfordRow.com.

The ruling cited Oxford English Dictionary definition of bespoke as "made to order",

and considered that despite the fact a bespoke suit was "fully handmade and the

pattern cut from scratch, with an intermediary baste stage which involved a first
7
fitting so that adjustments could be made to a half-made suit", while a suit made-to-

measure "would be cut, usually by machine, from an existing pattern, and adjusted

according to the customer's measurements", "both fully bespoke and made-to-

measure suits were "made to order" in that they were made to the customer's precise

measurements and specifications, unlike off-the peg suits". (Michael at.al 2011)

2.4 Moving online

According to Custom Tailors and Designers Association-CTDA (2012) At Gaebler,

we are seeing a trend in tailor shop startups toward a greater integration of

technology with traditional tailoring business activities. While many older shops are

hesitant to embrace technology-rich business models, younger entrepreneurs are

capturing market share by leveraging technology on multiple fronts:

2.4.1 Distance Tailoring.

Distance tailoring allows startups to expand their reach beyond the geographic

limitations of the local marketplace. Customers perform their own measurements

(with guidance) and place orders online. Although many tailors use this approach to

take advantage of cheap labor overseas, it is possible to leverage a distance-tailoring

framework. (gaebler.com, 2012)

2.4.2 Integrated Backend Solutions

Tailor shops are like small and medium business in the sense that there are multiple

behind-the- scenes business tasks that must be routinely performed. With today's

technology, accounting, billing, inventory, shipping and other software solutions can

be integrated to create a highly functional and seamless backend system.

8
(gaebler.com, 2012)

2.4.3 Social Media Marketing

Social media resources like Facebook and Twitter allow tailor shop startups to

convert satisfied customers to brand advocates. By actively engaging your customers

on these and other sites, you can encourage positive conversations around your

products and your brand (gaebler.com, 2012).

As the technology of garment production is advancing, many small-scale suit tailors

are gradually developing their capacity to garment manufacturing level while others

are still struggling to be considered in the industry. (Leykun et.al, 2012)

9
 CHAPTER THREE

RESEARCH METHODOLOGY
3.0 Introduction

The term methodology means the techniques and procedures adopted by conducting

a research study. It outlines how data will collected, and the tools for collecting data,

system methodology, the proposed system input and output, users and system

development tools.

3.1 Finding Techniques

It shows how data collected from the users of the system. The data collection

techniques to use include:

3.1.1 Observation

This technique will used to collect information about the current system operates and

its processes. This involves systematically watching and recording the behaviors and

characteristics of operations and processes. It gives more detailed and context related

information and can adapt to events as they occur, however, the method may be time

consuming.

3.1.2 Interviews

An oral interview will conduct where in via way of means, I will interview enterprise

owners, suppliers, customers and different people to get a deeper perception of the

way the will work. I choose this approach as it offers extra data from diverse

interviewees and gives extra flexibility because the possibility to restructure

questions is there, in case of interview. It desired, as it will offer a more in-depth

touch among the customers and the developer therefore dispelling the chance of the

10
finished system rejected via way of means of customers. This approach also:

 Permits rationalization of questions

 Has excessive reaction fee than written questionnaires

 It is appropriate to use with each literate and illiterates

 Get complete variety and intensity of data

 Develops dating with client

3.1.3 Secondary Data Collection

This is records I will acquire from current reasserts e.g. from the books, internet,

journals and magazines that in which accrued with the aid of using different

researchers and evaluation became done. It is from these records that I will then

examine with the number one records and make a very last selection and conclusion.

3.2 System Development Methodology

(SDLC) System development methodology is a technique that used to show how the

proposed system would developed. In this case, the methodology used will be a

waterfall model.

3.2.1 Waterfall Model

It is comprised of the stages that the developer will use when developing the system.

It is a sequential models hence the name waterfall. The developer has to finish with

one stage before going to the next one. It comprises of the feasibility study, analysis

phase, design phase, coding phase, testing phase, implementation phase and finally

the maintenance phase. It is a simple model and easy to use and understand. With

waterfall development based methodologies, the analysts and users proceed

sequentially from one phase to the next. The deliverables from each phase are
11
voluminous and presented to the project sponsor for approval as the project moves

from phase to phase. Once the sponsor approves the phase it ends and the next phase

begins.

Figure 3.1: Waterfall

Model

3.2.1.1 Feasibility study

Here, I will carry out a study to gain an understanding of the customers’ current

system and problems experienced in this system through interviews, observations,

participations etc. I will use the obtained data to determine the reliability of the

system proposed in terms of technical, economic and social feasibilities.

3.2.1.2 Requirements analysis:

At this stage, I will gather information about what the customer needs and define the

problems the system expected to solve. I will also include customers’ business

context, product functions and its compatibility. I will gather requirements such as

12
software like the programming language to use, database model and hardware needed

such as laptop, printers etc.

3.2.1.3 Design

At this stage, I will make an overall design of the system architecture and physical

design, which includes User interface and Database design. It is at this stage that I

will identify any faults before moving onto the next stage. The output of this stage is

the design specification, which is used, in the next stage of implementation.

3.2.1.4 Coding/Implementation

At this stage, I will begin coding as per the design specification. The output of this

step is one or more product components built according to a pre-defined coding

standard and debugged, tested and integrated to satisfy the system architecture

requirements.

3.2.1.5 Testing

In this stage, I will ensure both individual and integrated whole methodically verified

to ensure they are error free and satisfy customer requirements. I use testing of

individual code and modules, system testing of the product and ensuring the testing

conducted by or on behalf of the customer. I will ensure bugs found corrected before

moving to the next stage. I will also prepare, review and publish Product

documentation at this stage.

3.2.1.6 Installation

Once the product has been tested and certified as fit for use. The system is prepared

for use at customer site. I will do delivery via internet or physical delivery depending

on user needs.

13
3.2.1.7 Maintenance

This stage occurs after installation. It involves making modifications on the system to

improve performance. Such changes are user initiated or as result of bugs, being

discovered which initially not known. These modifications recorded for

documentation and system update.

3.2.1.8 Benefits of waterfall model

 It improves on quality: getting requirements and design first helps to catch

and correct possible errors at the design stage than at the testing stage, after

all components have been integrated.

 Simple and easy to understand and use

 Easy to manage due to the rigidity of deliverables and review process

 Phases are processed and completed one at a time

3.3 Conclusion

The online tailoring system will ease the managing customers with the aid of using

permitting them to ship their size on line as a result slicing on delivery fees and time.

It will ease verbal exchange between tailor, customer. It presents facts approximately

the price, the cloth kind the client need his/her get dressed knit from, the urgency at

which a client desires the get dressed finished, the sort of fabric to be used, amount in

phrases of pairs wished and maximum importantly, the device computes the entire

price and avails that facts to the client. Therefore, this device could be greater useful

to implement.

14
3.4 System Analysis

3.4.1 Existing System

The existing system found to be manual, i.e. customers’ information is caped in

books, there also required to walk to the tailor shop to get their measurements taken.

Customers also go to the tailor shops to check on the progress of their garments.

3.4.2 Problems of Existing System

Considering the above section, many problems associated with the existing manual

system, they include the following:

 Duplication in records of the customers.

 There is a problem of storage of the taken measurements i.e. can easily get lost.

 Information retrieval from these sources is not easy

3.4.3 Requirements Analysis

This are the analysis taking before taking over the project.

3.4.3.1 User Requirements

It is very important to get users of the system fully involved such that the

problem of change management does not arise. The system expected to be:

 Easy to learn and use

 Improve on the efficiency of information storage and retrieval

 Produce results faster i.e. measurements submission or checking clothe

status, therefore reducing on time wasted during travelling.

 Provides attractive interfaces with easy navigation throughout the system

 Faster, flexible and convenient.

 A system that stores data and produces reports timely and accurately
15
3.4.3.2 Functional Requirements

Functional requirements capture the intended behavior of the system. This behavior

may expressed as services, tasks or functions the system is required to perform.

Therefore, the proposed system is able to:

 Capture customer information, store it and make it available at the time of need.

 Present the users with a real-time display on the garments status.

 Generate reports accurately and timely

 Display customer information details

 Computes the total cost of a garment depending on the selected fabric, type of

material, quantity and duration and avails that information to the customer.

3.4.3.3 Non-functional Requirements (NFR)

Non-functional requirements are requirements, which specify criteria that can used to

judge the operation of a system, rather than specific behaviors.

This contrasted with functional requirements that specify specific behavior or

functions. Systems must exhibit software quality attributes, such as accuracy,

performance, cost, security and modifiability plus usability, i.e. simple to use for

intended users. NFRs help to achieve the functional requirement of a system. Thus,

the proposed system does the following:

 The system has high performance and reliability level. The mean time between

failures, mean time to repair, and accuracy are very high.

 The system has user-friendly interfaces. This ensures the ease with which the

system can learned and used. The system can allow users to install and operate it

with little or no training.

16
  Handles growing amounts of work in a graceful manner as can be readily

enlarged i.e. the ease, with which the system modified to handle a large increase

in users, workload or transactions.

 The system prevents unauthorized access to the system with user authentication

via loginon system.

3.4.3.4 System Requirements

This are the requirement needed in system.

3.4.3.4.1 Hardware requirements

ITEMS QUANTITY PRICE

Computer 1 100,000
Processor:
core2dual
3GB RAM
500 HDD
External back up (disks) 2 12,000
500 GB
Research and internet 2,000
costs
Printing and 3,000
photocopying
Stationary 3,000
Transport 4,000
Labor costs 5,000
TOTAL 129,000

Table 1: Hardware Requirements

17
3.4.3.4.2 Software Component System Requirement:

 Browsers: Microsoft Internet Explorer, Firefox, Opera.

 Server: Xampp

 Operating System: Windows XP, 7, 8 and 10.

 Back end: MySQL.

 Front end: PHP Script and scripting done using JavaScript.

3.4.4: Use Case Diagram

A use case diagram shows the interaction between the system and its environment.

The components of a use case diagram are:

 Actors: Represent external entities of the system i.e. People who interact with the

system that modeled. For example, customers and system administrator will be

the actors of the proposed system.

 Use Cases: Use cases functional in some parts of the system. E.g, the recording

data and submitting of their measurements.

 Associations: Associations shown between actors and use cases, by drawing a

solid line between them. This only represents that and actor uses the use case.

13
18
 Figure 3. 2: Use case

3.5 Data Flow Diagram

Data flow diagrams (DFDs) used to illustrate the flow of information in a system.

They are hardware independent and do not reflect decision points. They demonstrate

information and how flows between specific processes in a system. They provide one

kind of documentation for reports. These diagrams help to show how data moves and

changes through the system in a graphical top- down fashion. They also help to give

graphical representation of the system’s components, processes and the interfaces

between them. When it came to conveying how data flows through systems (and how

that data transformed in the process), DFDs were the method of choice over technical

descriptions for three principal reasons:

 DFDs are easier to understand by technical and non-technical audiences.

19
  They provide a high-level system overview, complete with boundaries and

connections to other systems.

 They provide a detailed representation of the system components.

The diagram below shows the flow of data through the proposed system. It

depicts the flow of information and the transformation that applied as data

moves from input to output

Figure 3.3: Decigram to show information flow in the proposed system

3.6 SYSTEM DESIGN

3.6.0 : Introduction

This involves transforming the software requirements into an architecture that

20
describes its toplevel structure and identifies the software components and

developing a detailed design for each software components. For each requirement, a

set of one or more design elements will produced. A model is a representation of

reality and can built for existing systems as a way to understand those systems or

proposed systems as a way to document business requirements or technical design.

3.6.1 Data Modeling

This is a technique for organizing and documenting a system’s data.

3.6.1.1 Conceptual design

Conceptual design is the very first phase of design, in which drawings or solid

models are the dominant tools and products. The conceptual design phase provides a

description of the proposed system in terms of set of integrated ideas and concepts

about what it should do, behave and look like, that will be understandable by the

users in the manner intended.

3.6.1 Data Dictionary

This contains all data definitions for cross-referencing and for managing and

21
 controlling access to the information repository/database. It provides a very thorough

interface description (comparable to Interface Control Documents) that is

independent of the model itself. Changes made to a model may be applied to the data

dictionary to determine if the changes have affected the model’s interface to other

systems. Data dictionaries do not contain any actual data from the database, only

book keeping information for managing it. Without a data dictionary, however, a

database management system cannot access data from the database. Below are the

illustrations:

Table 3.1 Description of user

login

Table 2: Description of customer’s information

22
Table 3: Description of top dresses measurement

Table 4: Description of bottom dresses measurement

23
 Table 6: Description of the finished

Table 7: Description of the design administration

24
 CHAPTER FOUR

SYSTEM IMPLEMENTATION

4.0 Introduction

It is the processes of putting the proposed system in operation. Some of the Activities

undertaken by the analyst are Training personnel who will use the system. There is also

provision of user manual and help page for efficient use of the system.

Next is to install Computer Equipment and internet to help them connect with their clients in

the globe. This will facilitate the full functionality of this proposed system. Equipment

should acquire from recognized vendor. These include central processing unit (CPU),

Ethernet cables, routers, output and input devices e.g. keyboard, mouse, monitor and all

secondary storage devices. The hardware and software vendors have major responsibility for

installing these equipment. The analyst then determines the functional changes. E.g. may

analyze the job function changes caused by the computerized system.

4.1 Coding

Coding is the construction of the actual system using specific language. For this proposed

system, I have used PHP to actualize the system. It is a scripting language, more secure and

web based.

4.2 Application and Database Connection

The constructed system connected to the My SQL Database through a data environment. The

tables should create and normalized. The data should also validate. A connection should also

be set and established in the design of the respective forms.

4.3 Testing

25
Testing is the process of verifying and validating the system for the conformance with

specification and meeting the customer’s requirements. The objectives of testing are to

ensure that the system programs is error free, guarantee the system end users can interact

with the system well and ensure that the components of the system interface are working

well.

4.3.1 Functional Testing

The purpose of functional testing is to ensure that the program performs all the functions that

originally specified that all the input correctly accepted. It relates to the whole system and

does not require a technical understanding of the system. All the functions of the system as

originally specified systematically tested to ensure that nothing has accidentally omitted or

misinterpreted.

A positive attempt made to anticipate errors than an inexperienced user might make, and tests

made to check the effect of such errors and ensure that they do not result in incorrect actions

or bad data being stored in the database.

4.3.2 System Testing

This is where the system checked whether it has met the user requirements and performs as

per expectations. The following are the tests to use. On completion of the whole system, each

of it tested to ensure no errors have introduced. The system is tested with a realistic amount

of test data; although the researcher is not expected to spend days typing in hundreds of

records, the system should be tested with about 10 records in each of the main tables.

4.4 Test Data

The purpose of test data is to verify and make sure that the system is operating well and

according to the standards set. It involves checking the new system if it is working correctly.

26
It tested in modules to establish if there is any problem in any module. This is whereby each

module tested on its own. While testing entries should be inputted as they are to be

acceptable in the database else errors will occur. As an example, if customer phone number

should be in letters so the field should not accept text.

4.5 File Conversion

The analyst changes the existing files into a form where it can used by the new system. The

procedure is as follows; the analyst first record the file data then Transcribe the documents to

suitable media and Verifies data to ensure it is error free

4.6 Front End Segment

These are the interface of the software.

4.6.1 Physical Design:

Login Page

Fig 4.1: shows the admin login page

27
28
Dashboard

Fig 4.2: Dashboard

Customer Register

Fig 4.3: Register customers.

29
Customer update: This page display was to update customer details after they have been

registered for any error correction.

Fig 4.4: Customer update

4.7 Back End Segment

The backend segment refers to database table used and, how they are all connected. The

registration table: this is how the registration table database looks like.

Fig 4.5: User Registration

30
 Figure 4.7: Registration table.

Admin login table: the admin login must have access to the data base, which when the admin

logging the data base will able to recognize his logging detail else display error.

4.8 Summary

The next step is to set up computer equipment and internet to allow them to communicate with

clients all over the world. This will make the planned system's full functionality possible.

Functional testing ensures that the program performs all of the functions that originally specified.

It does not necessitate any technical knowledge of the system. Each of the main tables should

tested with about 10 records. This is when the system checks to see if it has fulfilled the user's

expectations and is performing as expected. It tested in modules to see if there was a problem

with any of them. The tests to use are as follows.

31
 CHAPTER FIVE

CONCLUSION AND RECOMMENDATIONS

5.0 Introduction

This chapter describes the objectives of the system stipulated in earlier chapter,

limitation of the system, conclusion and recommendation of the system.

5.2 Conclusions

The core reason for the establishment of a tailoring management system is to enable

the customers and administrators in a convenient, fair and timely manner of

interaction. Therefore, the IT used by whoever uses the system should support the

core objective of the system if it is to remain relevant. A lot still needs to done in the

department in order to make available technology effective. This may involve

training of the staffs on how to enter right and relevant data into the system and the

management to keep updating the hardware and software requirements of the system.

5.3 Recommendations

Training of all the members of the staff in the tailor shops to get accustomed to the

system will be a priority. A being a new system, some members of the staffs’

management will threaten that the computerized tailoring management system will

replace their jobs. I would recommend that management of the tailor shops educate

the staff on how this system will operate and how it will supplement their efforts, i.e.

customers will only visit them during clothes collection. For the efficiency of the

system, users of the need to be thoroughly educated about the operations of the

system especially on how to register, give their details, make orders and on how to

check on their dress status. They should also know how to login using username and

32
password which should keep confidential.

Access to the server room should physically guarded against unauthorized person;

the server room should be dust free and fully protected with an air conditioner of

1100BTU to prevent the server from over-heating. Backup media like External hard

disks, CDs, Diskettes and Flush disks can use for backups and storage of data.

5.4 Problem encountered

Problems Encountered during System Design: Limited time to finish up the work,

limited numbers of computers with the internet in the faculty hence it becomes

difficult to download PHP codes from the internet and inadequate financial support to

facilitate the project. It is because of time factor also that limited the development

and incorporation of online payment capabilities, however, the system displays

relevant information about the cost of knitting a specific garment ordered depending

on the fabric chosen, material used, quantity required and the urgency at which it is

required.

33
REFERENCES:

Dunn, Bill (14 April 2003). "The Battle for Savile Row". Business Week. Retrieved 9

January 2009.

Cooper, H. (1998). Synthesizing Research: A Guide for literature Reviews Norton, Kate

(31 October 2006). "Savile Row Never Goes Out of Style".

Business Week. Retrieved 9 January 2009.

Hardy Amies UK stores to close following sale to Fung Capital". Retail Week. 2008- 11-

11. Retrieved 2009-10-08.

Piet Schreuders, Adam Smith, Mark Lewisohn (30 Jun 2008). Beatles London: The

Ultimate Guide to Over 400 Beatles Sites in and Around London. Anova

Books.pp. 53.

U.S. Bureau of Labor Statistics (BLS), http: / / degree directory. Org / articles / Tailor _

How _ to _ Become _a _ Professional _ Tailor _ i n _ 5 _ Ste ps.html

Tailoring Software (For ladies/gents tailoring shop)-www.assersoft.com

http://www.thereporterethiopia.com/Society/the-promising-tailor-

industry.html

George Shaw (2001) retrieved 13 February 2012, from

http://www.askmen.com/fashion/keywords/tailored-clothes.html

Custom tailors and designers association (2012), http://www.gaebler.com/Opening-a-

TailorShop.htm

Gieves & Hawkes on No. 1 Savile Row - http://en.wikipedia.org/wiki/Bespoke

http://www.bbc.co.uk/britishstylegenius/content/21811.shtmlhttp://lotro-

wiki.com/index.php/Tailor

Lancaster (2013) Tailors in UK; http://www.ewhworkshop.biz

34
The Bespeaker’s Guide to Tailored Clothing for Women-01 January 2010

Tom Giles at [email protected] - http://www.bloomberg.com/news/2012-08-

08/etailor-startups-challenge-amazon-in-200-billion-market.html

Tender Tailor System, modified 2010 – http : // www .tendertailor .com /Why

TendingSystem.htm

Day, Peter (2003). "How secret agent Hardy Amies stayed in Vogue during the war".

London: The Telegraph. Retrieved-2009-10-09. Margaret - Head of Tailoring School

Uganda, (2011).

Paula Deitz (25 August 1996). "Savile Row's Ambassador to the Court of Kings".The

New York Times. Retrieved 9 January 2009.

35