1

TEXTILES MANAGEMENT SYSTEM

CHAPTER-1
INTRODUCTION

1.1 INTRODUCTION:

Textiles Management system is a software for textiles industries, which aimed to

reducing the workload in the textile industry

The Textiles Management System is designed to allow the industry to keep track
of all employee details, textiles details, product details, supplier details and customer
details .it keep tracks of active employees as well as employee who have left the textile
industry

The Textiles management system includes Front office modules ,Back office
modules, Customer Management and Supplier Management. This will help authorized
used to insert, delete, update and view the various records related to employees ,sales,
purchase and many more details. This makes software to flexible use

1.2 COMPANY PROFILE:

Established in 2017, ROAD SIDE ROMEO aims at providing high standard

shopping experience in the state of Tamilnadu, particularly in Coimbatore district. It has
already been a favourite hangout spot for Shoppers.

1.3 ABSTRACT:

The Textile management system application is developed for managing the

textile shop. This project is made in C#.Net and the back end used is SQL server. The
idea of textile shop development is how to manage the textile shop in a good manner or
we can say managing the textile shop well from which people can get profit or just stay
out from the difficulties, how the things is proper in the shopping mall, what is the input
 2

in the shopping mall and what is the output how to track the goods are available there or
which is sort.

All this is auto track by the application from which there will be no any difficulties facing
by the management after all there are certain report generation based on the shopping mall
daily turnover, monthly turnover etc.

1.4 OBJECTIVE:

The main objectives of this project work are that:

 Implementing the functionality on login page to validate user and provide the
user appropriate features
 The admins can view and manage the sales, purchase.
 To view past sailed history for customers.
 To view all the transactions made for a particular day for the administrator.
 Maintain all the data in digital form which is more advantageous than paper
records.
 3

CHAPTER-2
SYSTEM ANALYSIS

2.1 EXITING SYTEM:

The existing system is not computerized and automated. And they keep Hard
records to keep transactions. The customer follow-ups and supplier follow-ups are
takes too time to check. In existing system no security has been provided to the data.
As the work is manual it consumes lot of money and time . it takes half of records to
find a specific record. As the calculations are done manually there is possibility of
incorrect calculation resulting in incorrect information. Tasks like fee receipt,
attendance management and salary generations are manually carried out. In our
system, attendance records once entered in maintained and retrieved easily. As we
see this reduces the manual work and manpower. Hence processing becomes faster

DISADVANTAGE OF EXISTING SYSTEM

 More human error.
 More strength and strain of manual labour needed.
 Repetition of the same procedures.
 Difficult to handle.
 Difficult to update data.
 Record keeping is difficult.

2.2 PROPOSED SYSTEM:

Multiuser environment is provided. In this when one user is updating a form
the other user cannot open the same form to avoid conflicts. Security to the data is
 4

provided by means of Login Form. Only authorized users can have access to the
system. The system allows users to maintain records of customers, suppliers, their
orders, raw materials, stock availability as well as bill generation. This system also
allows users to generate Customer reports, Supplier reports, sales and purchase
reports as well as raw material’s reports in the form of crystal reports.

EXPECTED ADVANTAGES OF PROPOSED SYSTEM

The system is very simple in design and to implement. The system requires
very low system resources and the system will work in almost all configurations.

It has got following features:

 Minimize manual data entry.

 No need to wait for office hours to make sales and purchase.
 User friendliness and interactive.
 Records are kept in databases which helps in easy report generations.
 Easy report generation and handlings
 5

CHAPTER-3
SYSTEM SPECIFICATION

3.1 Hardware Specification:-

Processor : Intel Core I3

Ram : 2 GB or above.
HDD : 160 GB.

3.2 Software Specification:-

Operating System : Windows 8

Front end : C#.NET
Back end : Microsoft SQL Server
Framework : .NET FRAMEWORK 3.5
 6

CHAPTER-4
SOFTWARE DESCRIPTION
4.1 FRONT END

The company has selected C#.NET as programming language for developing this
project. There are many advantages for this programming language and also it is very
user friendly
C#.NET

C# is an elegant and type-safe object-oriented language that enables developers

to build a variety of secure and robust applications that run on the .NET Framework.
You can use C# to create Windows client applications, XML Web services, distributed
components, client-server applications, database applications, and much, much more.
Visual C# provides an advanced code editor, convenient user interface designers,
integrated debugger, and many other tools to make it easier to develop applications
based on the C# language and the .NET Framework..

C# syntax is highly expressive, yet it is also simple and easy to learn. The curly-
brace syntax of C# will be instantly recognizable to anyone familiar with C, C++ or
Java. Developers who know any of these languages are typically able to begin to work
productively in C# within a very short C#

C# programs run on the .NET Framework, an integral component of Windows

that includes a virtual execution system called the common language runtime (CLR) and
a unified set of class libraries. The CLR is the commercial implementation by Microsoft
of the common language infrastructure (CLI), an international standard that is the basis
for creating execution and development environments in which languages and libraries
work together seamlessly.

4.2 BACK END

Microsoft SQL Server

 7

Microsoft SQL Server is a relational database management system developed

by Microsoft. As a database server, it is a software product with the primary function of
storing and retrieving data as requested by other software applications—which may run
either on the same computer or on another computer across a network (including the
Internet). Microsoft markets at least a dozen different editions of Microsoft SQL Server,
aimed at different audiences and for workloads ranging from small single-machine
applications to large Internet-facing applications with many concurrent users.

Originally released in 1989 as version 1.0 by Microsoft, in conjunction with Sybase,

SQL Server and its early versions were very similar to Sybase. However, the Microsoft-
Sybase partnership dissolved in the early 1990s, and Microsoft retained the rights to the
SQL Server trade name. Since then, Microsoft has released 2000, 2005 and 2008
versions, which feature more advanced options and better security.

Examples of some features include: XML data type support, dynamic management
views (DMVs), full-text search capability and database mirroring.

SQL Server is offered in several editions with different feature set and pricing options to
meet a variety of user needs, including the following:

 Enterprise: Designed for large enterprises with complex data requirements, data
warehousing and Web-enabled databases. Has all the features of SQL Server, and
its license pricing is the most expensive.
 Standard: Targeted toward small and medium organizations. Also supports e-
commerce and data warehousing.
 Workgroup: For small organizations. No size or user limits and may be used as
the backend database for small Web servers or branch offices.
 Express: Free for distribution. Has the fewest number of features and limits
database size and users. May be used as a replacement for an Access database.
 8

CHAPTER-5
PROJECT DESCRIPTION

5.1 MODULE DESCRIPTION:

CUSTOMER MANAGEMENT:
The admin can register regular customer in software by using the customer
registration form.

SALES :
 The admin can select particular customer and select items what they want.
 Admin can view past customer invoices and prices

PURCHASE:
 The admin can select particular supplier to purchase items
 Admin can also generate purchase invoices and reports
 9

DATA FLOW DIAGRAM:-

 10

ER DIAGRAM:-
 11

DATABASE DESIGN:-

Table Name: TblAccountHead

Primary Key: accountHeadId

Field Name Data Type Size Constraints Description

accountHeadId Int Primary Key Id

accountHeadPrefix Varchar 50 Not Null Account Head

accountType varchar 30 Not Null Accounting

Type

Table Name: TblItemType

Primary Key: itemTypeID
Field Name Data Type Size Constraints Description

itemTypeID Int Primary Key id

name varchar 50 Not Null

Category name

status Not Null status

 12

Table Name: TblPorductMaster

Primary Key: productId
Field name Data type Size Constraints Description

productId Int Primary Key Product ID

productName nvarchar 20 Not Null Product Name

itemTypeID int Foreign key Category of

Product

description varchar 20 Description

costPrice decimal 18,2 Not Null Cost price

sellingPrice decimal 18,2 Not Null Selling price

reorderPoint int Not Null Item Reorder

point

openingStock int Not Null Opening Stock

currentStock int Not Null Available Stock

UOM varchar 20 Unit of

measurement

UPC nvarchar 20 Universal

product code

SKU nvarchar 20 Shop Keeping

Unit

status bit status

 13

Table Name: TblSales

Primary Key: salesId

Field Name Data Type Size Constraints Description

salesId Int Primary Key Id

voucherNo Bigint Unique Transaction

Voucher No

invoiceNo Bigint Unique Sales Invoice

No

invoiceDate Date NotNull Date

customerId Int FK Customer Id in

Master

paymentType varchar 10 NotNull Payment Mode

totalAmount Decimal 18,2 NotNull Total Amount

Discount Decimal 18,2 NotNull Deiscount

Amount

PaidAmount Decimal 18,2 NotNull Customer paid

amount

TaxPercentage Varchar 10 NotNull Tax Percentage

TaxAmount Decimal 18,2 NotNull Total Tax

Amount

returnFlag Bit NotNull To check the

sales is
returned

isCheckout Bit NotNull Check Invoice

is Completed

Userid Int NotNull Logined user id

 14

Remark Nvarchar Max Remark about

sales

Status Bit Sales Status

Table Name: TblSalesSplit

Primary Key: Id
Field Name Data Type Size Constraints Description

Id Int Primary Key Id

salesId Int FK Sales Id

productId Int FK Item ID

Price Decimal 18,2 NotNull Item unit price

Qty Int NotNull Quantity saled

Amount Decimal 18,2 NotNull Total item

Amount

Discount Decimal 18,2 NotNull Item discount

TaxPercentage Nvarchar 10 NotNull Tax %

Taxamount Decimal 18,2 NotNull Tax amount

returnFlag Bit NotNull Is item

Returned?

returnQty Int Returned qty

tranVoucher Bigint Transaction

Voucher

Status Bit Status

 15

Table Name: TblPurchase

Primary Key: purchaseId

Field Name Data Type Size Constraints Description

purchaseId Int Primary Key

InvoiceNo Nvarhcar Max Not Null Inv No

InvoiceDate Date Not Null Invoice Date

PaymentType Nvarchar 10 Not Null Cash/Card/Credit

SupplierId Int FK Supplier Id

TotalAMount Decimal 18,2 Not Null Total bill Amount

PaidAmount Decimal 18,2 Not Null Total

PaidAMount

PaymentDue Decimal 18,2 Not Null Credit Amount to

Pay

TotalDiscount Decimal 18,2 Not Null Discount

Remark Nvarchar Max Remark

Status Bit

Return flag Bit Is Purchase

returned

Voucher Bigint Not Null Transaction

voucher

Taxpercentage Nvarchar 10 Not Null Tax percentage

taxAmount Decimal 18,2 Not Null Tax amount

netAmount Decimal 18,2 Not Null NetAmount

Userid Int Not Null Login user id

 16

Table Name: TblPurchaseSplit

Primary Key: Id

Field Name Data Type Size Constraints Description

Id Int Primary key Id

purchaseId Int FK Purchase id

productId Int FK Item Id

unitPrice Decimal 18,2 Not null Unit price

unitType Varchar Not Null UOM

TotalAMount Decimal 18,2 Not Null Total Amount

Discount Decimal 18,2 Not Null

returnFlag Bit Not Null Is Item

returned

taxPercentage Nvarchar 10 Not Null Tax percentage

taxAmount Decimal 18,2 Not Null Tax amount

Returnqty Int Return

quantity

voucherNo Bigint Transaction

voucher no

Status Int

Table Name: TblLogin

Primary Key: userId

Field Name Data Type Size Constraints Description

userId Int PK Id

username Nvarchar 100 Not Null Username

Password Nvarchar 100 Not Null Password

Status Int Not Null status

 17

Table Name: TblCustomer

Primary Key: customerId

Field Name Data Type Size Constraints Description

customerId Int PK Id

Name Nvarchar 100 Customer

Name

Mobile Nvarchar 12 Not Null Cust mobile

Address Nvarchar Max Cust address

Email Nvarchar 50 Email

outstandingBalance Decimal 18,2 Not Null Customer

Outstanding

openingBalance Decimal 18,2 Not Null Opening

Balance

Status Int

Table Name: TblSupplierMaster

Primary Key: supplierId

Field Name Data Type Size Constraints Description

supplierId Int PK Id

supplierName Varchar 100 Not Null Supplier

Name

Address Varchar Max Address

Mobile Varchar 10 Not Null Mobile

Email Varchar 50 Email

Remark Nvarchar Max Remark

outstandingBalance Decimal 18,2 Not Null O/s Balance

 18

openingBalance Decimal 18,2 Not Null Opening

Balance

openingDate Date 18,2 Not Null Entry Date

Status Bit Not Null