ST.

MARY’S
UNIVERSITY
SCHOOL OF
GRADUATE STUDIES
ST. MARY’S UNIVERSITY
SCHOOL OF GRADUATE STUDIES

MAY 5, 2023
Addis Ababa, Ethiopia
ST. MARY’S
UNIVERSITY
SCHOOL OF
GRADUATE STUDIE
ONLINE TAILORING MANAGEMENT SYSTEM

By
1. Zekarias Getnet
2. Abebe Kelemu

I
Table of Contents
CHAPTER ONE..............................................................................................................................................1
1. INTRODUCTION...................................................................................................................................1
1.1. Background of the Organization..................................................................................................1
1.2. Statement of the problem...........................................................................................................1
1.3. Objectives of the project.............................................................................................................1
1.3.1. General objectives...............................................................................................................1
1.3.2. Specific objectives................................................................................................................1
1.4. Feasibility study...........................................................................................................................2
1.4.1. Technical feasibility..............................................................................................................2
1.4.2. Operational feasibility..........................................................................................................2
1.4.3. Economic feasibility.............................................................................................................3
1.5. Significance of the project...........................................................................................................3
1.6. Beneficiaries of the project..........................................................................................................3
1.7. Methodology...............................................................................................................................3
1.7.1. Data collection.....................................................................................................................3
1.7.2. System design and analysis tools.........................................................................................4
1.8. Scope and limitation of the project.............................................................................................5
1.8.1. Scope of the project.............................................................................................................5
1.8.2. Limitation of the project......................................................................................................5
1.9. Risk, assumption and constraints................................................................................................5
1.9.1. Risk.......................................................................................................................................5
1.9.2. Mitigation............................................................................................................................5
1.10. Budget allocation.....................................................................................................................6
1.11. Work plan................................................................................................................................6
CHAPTER TWO.............................................................................................................................................7
2. BUSINESS AREA ANALYSIS AND REQUIREMENT DEFINITION...............................................................7
2.1. Introduction.................................................................................................................................7
2.2. Business area analysis..................................................................................................................7
2.2.1. Detailed analysis..................................................................................................................7
2.2.2. Current system.....................................................................................................................7

II
 2.2.3. Proposed system..................................................................................................................8
2.3. Requirement Gathering...............................................................................................................8
2.3.1. Requirement Gathering Techniques....................................................................................8
2.4. Method of Communication..........................................................................................................9
2.4.1. Communication techniques.................................................................................................9
2.5. Requirement definition................................................................................................................9
2.5.1. Functional requirement.......................................................................................................9
2.5.2. User Requirements............................................................................................................10
2.5.3. Nonfunctional Requirements.............................................................................................10
CHAPTER THREE........................................................................................................................................12
3. System modeling...............................................................................................................................12
3.1 Introduction...............................................................................................................................12
3.2 System Use Case........................................................................................................................12
3.3 UI Identification.........................................................................................................................12
3.4 Business Rules Identification.....................................................................................................12
3.5 Actor Identification....................................................................................................................12
3.6 Use Case Diagram......................................................................................................................12
3.7 Use Case Description.................................................................................................................12
3.8 Sequence diagramming.............................................................................................................12
3.9 Activity Diagramming.................................................................................................................12
3.10 Class diagram.............................................................................................................................12
3.11 State chart diagram...................................................................................................................12
3.12 User interface Prototyping........................................................................................................12
CHAPTER FOUR..........................................................................................................................................12
4. System design....................................................................................................................................12
4.1 Database normalization.............................................................................................................12
4.1.1 First normal form...............................................................................................................12
4.1.2 Second normal form..........................................................................................................12
4.1.3 Third normal form..............................................................................................................12
4.2 Database table structure...........................................................................................................12
4.3 Deployment diagram.................................................................................................................12
4.4 Interface design.........................................................................................................................12
4.5 High fidelity prototype...............................................................................................................12

III
CHAPTER FIVE............................................................................................................................................12
5. Conclusion and recommendation......................................................................................................12
5.1 Conclusion.................................................................................................................................12
5.2 Recommendation......................................................................................................................12
REFERENCE................................................................................................................................................12
APPENDIX..................................................................................................................................................12

IV
CHAPTER ONE

1. INTRODUCTION

1.1. Background of the Organization

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 also 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 will be more effective and efficient than the existing manual system. Tailoring has
been known to be dominated by unlearned people. 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. This 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 and automate the tailor shops and enhance accessibility irrespective of geographical
locations provided there is internet.
1.2. Statement of the problem
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
slow. Customers too have no prior information on cost of netting their garments.
1.3. Objectives of the project
1.3.1. General objectives
The main objective of this project is to develop online tailoring management system and eliminate all
these manual interventions and increase the speed of the whole process.

1.3.2. Specific objectives

The specific objectives of the Online Tailoring Management System include:

1
  Automate the current manual tailoring system and maintain a searchable customer,
product database, maintain data security and user rights.
 To enable customers to send their measurements to their tailors for their clothes to be
made.
 To provide information about the cost, the fabric type, the urgency at which a customer
wants the dress finished, the type of material to be used and quantity in terms of pairs
needed.
 To compute the total cost depending on the selected fabric, type of material, quantity and
duration and avails that information to the customer.
 To enable report generation: it is able to give a report of finished garments to the clients
for collection and bookings made, administrator is able to view all the customers and
their details, finished garments and all the bookings made.
 To create a data bank for easy access or retrieval of customer details, orders placed and
the users who registered to the system.
1.4. Feasibility study
Feasibility study is essential to evaluate the cost and benefits of the new system. On the basis of
the feasibility study decision is taken on whether to proceed or to cancel the project.

Need of the feasibility study:

 It determines the potential of the existing system.

 It used to determine/finds out the problem of the existing system.
 To determine all goals of the new system.
 It finds all possible solutions of the problems of the existing system.
1.4.1. Technical feasibility
The system to be developed by using technologically system development techniques such as
PHP laravel framework and MySQL database without any problems and the group members
have enough capability to develop the project. So the system will be technically feasible.

1.4.2. Operational feasibility

The system to be developed will provide accurate, active, secured service and decreases labor of
workers and also it is not limited to particular groups or body. And also it is plat form
independent i.e. it run’s in all operating system.

2
 1.4.3. Economic feasibility
The system to be developed is economically feasible and the benefit is outweighing the cost.
Since this project already computerizes the existing system, by now the reduction of cost for
materials used in manual operation becomes beneficiary to the organization.

1.5. Significance of the project

The proposed online tailoring management system will eliminate all these manual interventions
and 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 to
the 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 get knit. This data will be stored in the database for further
reference or audit.

1.6. Beneficiaries of the project

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 24/7 and at any location provided they are connected to
the 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 a competitive edge in the market.

1.7. Methodology
1.7.1. Data collection
It shows how data will be collected from the users of the system. The data collection techniques
to be used include:

1.7.1.1. Observation

3
I will use this technique to collect information about how 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.

1.7.1.2. Interviews
I will conduct an oral interview whereby i will interview business owners, suppliers and buyers
to get a deeper insight of how the system is going to work. I prefer this method because it gives
more information from various interviewees and offers greater flexibility as the opportunity to
restructure questions is there, especially in case of unstructured interview. It’s preferred because
it will provide a closer contact between the users and the developer hence dispelling the
probability of the completed system being rejected by users.

This technique also:

 Permits clarification of questions

 Has high response rate than written questionnaires
 It is suitable for use with both literate and illiterates
 Get full range and depth of information
 Develops relationship with client
 Can be flexible with client
1.7.1.3. Secondary Data Collection
This is data I will collect from existing sources e.g. from the books, internet, journals and
magazines that where collected by other researchers and analysis was done. It is from this data
that I will then compare with the primary data and make a final decision and conclusion.

1.7.2. System design and analysis tools

At this stage i will make an overall design of the system architecture and physical design which
includes User interface and Database design. It’s 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.

System design tools

1. Edraw max and Microsoft Visio: Used to draw the Use Case Description, Use Case diagram, Sequence
Diagram, Class Diagram and Activity Diagram.

4
2. Microsoft word: We used Microsoft word to write our proposal.

Script Languages
 PHP laravel framework (HTML,CSS, Bootstrap)

Web Server
 Apache XAMPP server

Database Server
 MySQL Database Management System.

1.8. Scope and limitation of the project

1.8.1. Scope of the project
The Online Tailoring Management System will permit to register and deliver measurements to
the 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.

1.8.2. Limitation of the project

Online payment has not been achieved, but the customer is expected to pay either via mobile
money transfer services like tele birr, cbe birr or cash when they come to pick their clothes.

1.9. Risk, assumption and constraints

1.9.1. Risk
Some of the risks and threat that can affect this project are:-

 Hosting – some host may be unreliable

 Security risk – hackers and virus attack
 Time – not able to complete the project in time
 Cost of resources – not having adequate budget

1.9.2. Mitigation
 Look for reliable people/company to host your program.

5
  Use of security measures e.g. firewalls to protect from unauthorized people.
 I will ensure that project schedule is followed for the project to finish in time.
 Ensure that the required resources are available and within my budget.

1.10. Budget allocation

ITEMS PRICE(Birr)
Laptop Computer 50,000
External back up (disks) – @ 2 TB 8,000
Internet costs 6,000
Printing and photocopying 1,000
Transport 1,000
Total 66,000

1.11. Work plan

Time

Activities
May 25-

Aug 19-
May 20
Apr 12-

Apr 20-

Aug 15
Jun 17-

July 8-
Jun 17

Sep 20
Apr 20

July 5

Project Proposal
Requirement Analysis
Design
Implementation & Coding

Testing
project Defense

6
CHAPTER TWO
2. BUSINESS AREA ANALYSIS AND REQUIREMENT DEFINITION
2.1. Introduction
A tailor is one that makes, repairs, and alters garments such as suits, coats, and dresses. A tailor
makes custom cloths wear of various styles like jackets, skirts or trousers that go with them, for
men or women. An alterations specialist adjusts the fit of completed garments, usually ready-to-
wear, or restyles them. Designers choose combinations of line, proportion, color, and texture for
intended garments. They may have no sewing or patternmaking skills, and may only sketch or
conceptualize garments.

2.2. Business area analysis

2.2.1. Detailed analysis
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 is drafted for each client, and the optimal traditional tailoring technique is
used to realize the shape of the final garment. The two principle reasons for bespoke tailored
clothing are as follows:

1. Difficulty attaining a good fit from ready-to-wear garments

2. Access to a wider range of styles and cloth designs

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.

2.2.2. Current system

The existing system was found to be completely manual, i.e. customers’ information is captured
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.

7
 2.2.3. Proposed system
The online Tailoring system will ease the work of clients by allowing them to send their
measurement online thus cutting on transport expenses and time. It will ease communication
between the tailor and the client and also to access each other.

It provides information about the cost, the fabric type the customer want his/her dress knit from,
the urgency at which 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. Therefore, this system will be more beneficial to
implement.

2.3. Requirement Gathering

It shows how data will be collected from the users of the system. The data collection techniques
to be used include:

2.3.1. Requirement Gathering Techniques

2.3.1.1. Observation
I will use this technique to collect information about how 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.

2.3.1.2. Interviews
I will conduct an oral interview where by I will interview business owners, suppliers and buyers
to get a deeper insight of how the system is going to work. I prefer this method because it gives
more information from various interviewees and offers greater flexibility as the opportunity to
restructure questions is there, especially in case of unstructured interview. It’s preferred because
it will provide a closer contact between the users and the developer hence dispelling the
probability of the completed system being rejected by users.
This technique also:

 Permits clarification of questions

 Has high response rate than written questionnaires
 It is suitable for use with both literate and illiterates
 Get full range and depth of information
 Develops relationship with client

8
  Can be flexible with client

2.3.1.3. Secondary Data Collection

This is data I will collect from existing sources e.g. from the books, internet, journals and
magazines that where collected and analysis. It is from this data that I will then compare with the
primary data and make a final decision and conclusion.

2.4. Method of Communication

2.4.1. Communication techniques
2.5. Requirement definition
I will gather information about what the customer needs and define the problems the system is
expected to solve. I will also include customers’ business context, product functions and its
compatibility. I will gather functional requirement and nonfunctional requirements.

2.5.1. Functional requirement

Functional requirements capture the intended behavior of the system. This behavior may be
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
 Search and 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.

2.5.1.1. Essential Use case Modeling

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. Use case diagrams are employed in UML (Unified Modeling Language), a
standard notation for the modeling of real-world objects and systems.

2.5.1.2. Actor description

Customer

 Log in
 Register
 Make an order

9
  Give feedback
 Generate report

Administrator

 Update records
 Store records

2.5.1.3. Essential Use Case Description

Use case diagrams are used during requirement elicitations and analysis to represent the
functionality of the system. Use cases focuses on the behavior of the system from an external
point of view. A use case describes a function provided by the system that yields a visible result
for an actor. An actor describes any entity that interacts with the system.

2.5.2. 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 is 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 to and from 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

2.5.3. Nonfunctional Requirements

Non-functional requirements are requirements which specify criteria that can be used to judge
the operation of a system, rather than specific behaviors. This is 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. easy
to use for the 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.

10
  The system has user-friendly interfaces. This ensures the ease with which the system can
be learned or used. The system can allow users to install and operate it with little or no
training.
 Handles growing amounts of work in a graceful manner as can be readily enlarged i.e. the
ease, with which the system can be 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.

Title: Online Tailoring Management System Proposal

Dear [Client's Name],

Introduction:

We are pleased to present our proposal for the implementation of an Online Tailoring
Management System for your tailoring business. Our proposed system is aimed at assisting in the
efficient management of tailoring activities and streamlining your business operations within the
industry.

Objective:

The primary objective of the Online Tailoring Management System is to create a centralized
platform that enables you to manage customer orders, monitor work progress, track employee
productivity, and maintain accurate inventory records, all in one place. By leveraging modern
technology and industry best practices, our system will help improve overall operational
efficiency and customer satisfaction.

Key Features:

11
1. Customer Management:

- Online registration and login for customers

- User-friendly interface for customers to place orders and make payments

- Track order history and previous measurements

- Facilitate customer communications with real-time notifications

2. Order Management:

- Centralized dashboard for easy monitoring of customer orders

- Automated generation of cutting patterns based on customer measurements

- Schedule work assignments for tailors

- Real-time tracking of order progress/status

3. Inventory Management:

- Monitor stock levels of fabrics and materials

- Automated re-ordering when stock levels reach a predefined limit

- Detailed reporting on inventory usage and cost analysis

4. Employee Management:

- Employee registration and login with role-based access controls

- Track individual productivity metrics like work hours, orders completed, etc.

- Streamline payroll calculation based on hourly rates or salaries

12
5. Reports and Analytics:

- Generate comprehensive reports on order status, sales, revenue, etc.

- Analyze data trends to help identify growth opportunities and areas for improvement

- Customizable report templates to suit specific business requirements

Implementation Plan & Timeline:

Our team is prepared to commence the implementation process as soon as we receive your
approval. The project will be executed in four main phases: Planning & Scoping, Development,
Testing & Deployment, and Post-launch Support & Maintenance.

We estimate that the total implementation will take approximately three months from start to
finish, depending on your specific requirements and other factors.

Investment & Pricing:

We offer a competitive pricing structure for our Online Tailoring Management System, with
multiple plans to suit a variety of budgets and business sizes. Once we have a better
understanding of your specific needs and requirements, we will be able to provide you with a
tailored proposal that outlines investment costs and ongoing maintenance fees.

Conclusion:

We are confident that our proposed Online Tailoring Management System will greatly enhance
the efficiency of your tailoring business while providing exceptional value for your investment.
We look forward to the opportunity to work with you on this exciting project and contribute
positively to your business growth.

13
Please feel free to reach out if you have any questions or concerns about our proposal. We are
committed to ensuring your complete satisfaction.

Best Regards,

[Your Name]

[Your Company Name], Business Development Manager

14
15
CHAPTER THREE
3. System modeling
3.1 Introduction
3.2 System Use Case
3.3 UI Identification
3.4 Business Rules Identification
3.5 Actor Identification
3.6 Use Case Diagram
3.7 Use Case Description
3.8 Sequence diagramming
3.9 Activity Diagramming
3.10 Class diagram
3.11 State chart diagram
3.12 User interface Prototyping

CHAPTER FOUR
4. System design
4.1 Database normalization
4.1.1 First normal form
4.1.2 Second normal form
4.1.3 Third normal form
4.2 Database table structure
4.3 Deployment diagram
4.4 Interface design
4.5 High fidelity prototype

CHAPTER FIVE

5. Conclusion and recommendation

5.1 Conclusion
5.2 Recommendation

REFERENCE

APPENDIX

16