201415

Submitted By : Rajan A. Makwana(BCA122626160)

Under The Guidance Of :

BCSP - 064
TAILOR SHOP MANAGEMENT SYSTEM
By
MAKWANA RAJAN ASHWINKUMAR
Enrolment No:
122626160
Under Guidance
Of

Submitted to the School of Computer and Information Sciences, IGNOU

in partial fulfillment of the requirements
for the award of the degree

Bachelors in Computer Applications (BCA)

Year of Submission 2014-15

Indira Gandhi National Open University

Maidan Garhi
New Delhi 110068.

Table of Content
Topics
1. Title of the Project
2. Introduction and Objective of the Projects
3. Project Category
4. Analysis Report (DFDs etc)
5. E-R Diagram
6. A Complete Structure of the Program
6.1 Number of Modules
6.2 Data Structure
6.3 Process Logic
6.4 Types of Output / Report Generation
6.5 Validation Checks
7. Tools / Platform, Languages to be used
8. Scope of Future Application

1.

TITLE OF THE PROJECT

TAILOR SHOP MANAGEMENT SYSTEM

(TSMS)

Submitted By

2. INTRODUCTION AND OBJECTIVE OF THE PROJECT

Project Definition
"Tailor Shop Management System" for tailor shop. Which should support and store all
record of Tailor shop.

Introduction
Sachins Shop began in 1999 in Vadodara, India. Since its founding, Sachins Shop has
become one of the largest apparel tailors shop and retailer in Vadodara, India.
Sachins Shop has established itself as a premier supplier of Indian classical wedding
dresses, gowns, girl dresses and other formal wear.
Since the expansion into apparel industry, Sachins Shop has experienced remarkable
growth and gain great recognition.
For over 5 years, Sachins Shop has been empowering Indian women to express their
personal style by offering the latest fashions at easily affordable prices. Its "Real Style,
Real Value" approach means staying ahead of the fashion curve with high-quality, ontrend designs.
Its exclusive merchandise is created by a design team in India. They take what's new
and then make it own, with a flattering shape and a feminine feeling. That includes
everything from the latest looks to fashion essentials. Two collections we're especially
proud of are. For the most shopping options. Customer will find complete collections
here in Sachins Dress shop

Existing Manual System

In existing system of Tailor Shop Management System. All work is done by paper.
Present System work like.
Measurement master take measurement of customer by require for create
garment./dresses. also record in customer register book.
Tailor record also store in them registrar. like them daily works, payment, etc.

External service provider record. his work, his payment given or not, store on paper.
Bill report generate by manual.
Report is generated about Garment, Dresses . This report is also need paperwork and
some manual effort.

DRAWBACK OF THE EXISTING SYSTEM:

There are many problems and inconveniences faced in the present existing system.
Since present system is working by means of paper work, there are many problem at
real time.
For the various report activities, filled on paper. The paper work is also time consuming
and may cause problems for the person to understand the details exactly if not written
properly, also the handwriting may not be legible. Some time measurement record
paper may misplace and problem create for garment creation, There are the chances of
getting lost of the important documents or papers.
There is also problem in maintaining the old records in different registrar files. There
are number of files for different records generated each year, it demands greater space
and care to store the old records.
So by the way following were the flows in the existing manual system, that were
identified during the system study phase.
The existing manual system stores the data on paper. This data is about customer
details, Measurement, Tailor record, External service provider record, payment , Bill
report etc. All of above data has taken on paper and stored in files/registers. There are
need of paper work for various reports .

Scope and Objective Of Project

Objectives

 To prepare the project users friendly with proper validations and various security
levels to have selected SQL-Server
To store, maintain and update record of customer at regularly as customer required.
To store Tailor, Service provided, they work details and salary record.
Can be give assuming date to the customer at on order date.
Huge details of all customers, tailors, workers can save only on single hard disk.
The features should be such that in future it can be linked with various departments in
shop, which ensures the minimization of the paper work.
The system should be developed in such a way that there is a fullest scope of
commercialization amongst any type of shop/ industries.

3. PROJECT CATEGORY

 Relational Database Management System (RDBMS)

Intranet

4. ANALYSIS REPORT(DFDs etc)

2

5. E-R DIAGRAM

6. A COMPLETE STRUCTRE OF THE PROGRAM

6.1.

Number of Modules

Master Module
o Customer Master
Addition
Modification
Remove
o Product Master
Addition
Modification
Remove
o Tailor Master
Addition
Modification
Remove
o User Master
Addition
Alteration
Activate / Deactivate
Measurement & Orders
o Customer Measurement
Addition
Modification
Remove
o Tailor Work Assignment

o Tailor Work Submission

 Billing
o Bill Generation
o Payment
o Pay Slip
Reports
o Bill
o Daily Collection
o Daily Work Assignment Collection
o Tailor Daily Work Assignment/Payment Collection
o Tailor Monthly Assignment/Payment Collection
o Tailor Yearly Assignment/Payment Collection

6.2.

Data Structure

Login Master

Sr.No.
1
2
3
4
5
6
7
8
9
10

Field Name
Login_Id
Password
Name
Address
Phone_No
Mobile_No
UserName
Email_Id
Seceret_Que
Seceret_Ans

Product Master

Sr.No.
1
2
3
4
5
6
7
8
9
10

FieldName
Product_Id
Product_Name
Product_Colour
Product_Type
Maker_Name
Brand_Name
Purches_Date
Product_Quntity
Product_Unit
Price

Tailors Master

Sr.No.
4
1
2
Sr.No.
31
42
53
64
7
5
8
6
9

Type
Num
Varchar
Char
Varchar
Num
Num
Char
Varchar
Varchar
Char

Type
Num
Char
Varchar
Varchar
Char
Char
Date/Time
Num
Num
Num

FieldName
Type
PaymentSlip/Details
Tailor_Id
Num
Tailor_Name
Char
FieldName
Type
Address
Varchar
Pay_Id
Num
Phone_No
Num
Tailor_Id
Num
Mobile_No
Num
DateOfPayment
Date/Time
Join_Date
Date/Time
Amount
Num
Resign_Date
Date/Time
Payment_Mode
Char
Expertise
Char
ChequeNo
Num
Work_Exprience
Num

Width
8
20
50
100
20
20
50
50
20
50

Description
Primary Key

Width
8
25
25
25
20
25
Date
15
15
10

Description
Primary Key

Width
8
50
Width
100
8
20
8
20
Date
Date
15
Date
8
10
10
10

Description
Primary Key
Description
Primary Key
Foreign Key
DD-MM-YYYY
DD-MM-YYYY
DD-MM-YYYY

*
Sr.No.
1
2
3
4
5
6
7
8
9
10
11

5
Sr.No.
1
2
3
4.
6
7
8
9
9

7
Sr.No.
1
2
3
4

Salary
FieldName
Salary_Id
Tailor_Id
Tailor_Name
NoOfDaysleave
NoOfDaysPresent
Tot_Salary
Deduction
Net_Salary
DateOfPayment
Payment_Mode
Cheque_No

Type
Num
Num
Char
Num
Num
Num
Num
Num
Date/Time
Char
Num

Width
8
8
50
10
10
15
15
15
Date
8
10

Type
Num
Char
Varchar
Num
Varchar
Char
Date/Time
Num
Num

Width
8
50
100
15
50
8
Date
9
10

Description
Primary Key
Foreign Key
Foreign Key

DD-MM-YYYY

Customer
FieldName
Customer_Id
Customer_Name
Address
Contact No
E_mail
Sex
DateofBirth
Age
DisconutEarn

Description
Primary Key
Not Null
Not Null

Male/Female
DD-MM-YYYY

Customer Measurment Details

FieldName
Customer_Id
Measurement_Id
Tailor_Id
Pattern_No

Bill

Type
Num
Num
Num
Num

Width
8
8
8
10

Description
Foreign Key
Foreign Key
Foreign Key
Foreign Key

Sr.No.
1
2
3
4

9
Sr.No.
1
2
3
4
5
6

10
Sr.No.
1
11
2
3
Sr.No.
4
1
5
2
6
37
48
59
6
10
11
12
13
14
15
16
17
18

FieldName
Bill_No
Customer_Id
Bill_Date
Total_Amount

Type
Num
Num
Date/Time
Num

Width
8
10
Date
15

Description
Primary Key
Foreign Key
DD-MM-YYYY

Type
Num
Num
Char
Num
Num
Num

Width
8
8
50
10
15
15

Description
Primary Key
Foreign Key

Bill Details
FieldName
Bill_No
Product_Id
Product_Name
Quantity
Rate
Amount

Measurment Details
FieldName
Measurement_Id
Orders
Customer_Id
Length
FieldName
Chest
Order_Id
Waist
OrderAssignDate
Waist_Length
OrderDileveryDate
Seat
Tailor_Id
Side_Cut
Product_Id
Sleeve_Round
Quntity
Sleeve_Length
Shoulder
Neck_Front
Neck_Length
Knee_Round
Knee_Length
Bottom
Bottom_Round
Leg_Length

Type
Num
Num
Double
Type
Double
Num
Double
Date/Time
Double
Date/Time
Double
Num
Double
Num
Double
Num
Double
Double
Double
Double
Double
Double
Double
Double
Double

Width
Description
8
Primary Key
8
Foreign Key
8
Width
Description
8
8
Primary Key
8
Date
DD-MM-YYYY
8
Date8
DD-MM-YYYY
8 8
Foreign Key
8 8
Foreign Key
10 8
8
8
8
8
8
8
8
8

6.3.

Process Logic

6.4.

Types Of Output/ Report Generation

Login Form
This form is kept for security purpose. The user can operate the system if user enters.
the correct user id and password and new user can register using register form.

Main Form
This form is the main form of the system. It displays the menu bar, the toolbar and the
status bar. The menu bar contains various menus for the forms reports and the
utilities.

Customer Master
This is database, which contains details about the contact persons and his name,
contact address, phone no. and etc.

Measurement/Customer Details
This is database, which contains details of customer's measurement for stitch various
dresses.

Order Details
This form contain order id, order assign date, order delivery date, Product Id, name,
Quantity, ant Tailor id.

Tailors
This form database which contains details about the contact of tailor his name, contact
address, phone no., expertise etc.

Output Screen (Reports)

Measurement/Customer Details
Order/Order details
Bill Receipt
Bill
Payment Slip/Salary Slip
Monthly Amount Collection
Half Yearly Amount Collection
Yearly Amount Collection
Monthly Tailor Wise Collection
Half Yearly Tailor Wise Collection
Yearly Tailor Wise Collection

Validation Checks

1. All text fields that take integers, as inputs will be validated so that only the digits are
allowed.
2. All text fields that take inputs as alphanumeric will be validated, so that only
alphabets are taken as parameters for input.
3. All fields that are mapped to Primary key will be validated so that the data is not
stored as NULL in the required fields.
4. All text fields max length, are set according to the mapped database fields, so that the
characters do not exceed the maximum length.
5. Before storing the data, all fields that take in NULL are store values as NULL.
6. All Date field values are stored as dd-MMM-yyyy format and will be consistent
through the system.
7. All database fields that take in a single value, as flag will content Digit.
8. Primary keys are IDENTITY columns, which makes then Auto-Increment value
field.
9. Data Stores in the reference table / column is validated through a Visual Graphical
Component like Combo, List Views, and Tree Views, which makes the Foreign Key
Value consistent and sure to be present in the Parent table.

7. TOOLS / PLATFORM, LANGUAGES TO BE USED

Front End Tools

Back End Tools

:- ASP.NET(Code Behind C#.net)

:- SQL Server 2005 (Express Edition)
Microsoft VISIO (UML modeling)

8. SCOPE OF FUTURE APPLICATION

2

This project makes for Sachins Tailor shop. They currently are handling the entire
customers' details in their record book.

This application for process development for new services.

Applicable to all customers' requirements.

Applicable to all type of fabric materials and consumable Product.

Applicable to processes like perches fabric marital, machines spear parts etc.

In future we can add remainder for customer ready dresses.

In future will be including also staff details.

In future perches stitch machines / service details of stitch machines details can be
added in application.

In next generation new dress design can be include in application as dress design
dictionary.