Textile Management System Simplifies Operations

TEXTILE MANAGEMENT SYSTEM
Submitted By
PRASHANT BHARATI
&
ABHISHEK MEDEKAR
Under the Guidance of
MR. VINAY DUBEY
MRS. SNEHALATA AGARWAL
Submitted in partial fulfilment of the requirement for qualifying
Semester 6 Examination
ELPHINSTONE COLLEGE
156, MAHATMA GANDHI ROAD,
FORT, MUMBAI 400 032
B.Sc (IT) ELPHINSTONE COLLEGE Page 1

acknowledgement
Many People have contributed to this project, and I would like to

thank all of them. I should start with my group partner with whom I shared
my project work. I am thankful to him for being committed to this project
and lending a helping hand.
Special thanks to our coordinator for assisting us to complete our

project, and our faculty whose expertise and talent in software language
and logical regression helped us effectively and to maintaining the lab
effectively.
We should also like to thank our Principal for providing us a library,

which helped us constantly in increasing our technological knowledge, and
write this project report.
I extend a special thank you to my parents, my family members and

my friends for their constant inspiration and encouragement, without which
this work would not have become successful.
COURSE COORDINATOR :
MRS.DR.JAYSHREE DESAI
FACULTY :
MRS. S. AGARWAL
MR. VINAY DUBEY

INDEX
TITLE NO TITLE NAME
PAGE NO
1. Introduction
2. Synopsis
3. Objective and Scope of project
4. Definition of project
5. Software/Technologies used
6. Explanation of the technologies
7. System Life Cycle
8. Spiral Model
9. System Requirements
10. System planning
11. Gantt Chart
12. Entity Relationship Diagram
13. Structure Chart
14. Pert Chart
15. Testing
16. Report List
17. Table List
18. Snapshots
19. Future Enhancements
20. Bibliography
21. Conclusion

INTRODUCTION
Textile Management System is software for textile industries,

which aimed to reducing the workload in the textile industry.
The Textile Management System is designed to allow the industry

to keep track of all employee details, textile details, product details,
banquet details and agent details. It keeps tracks of active employees
as well as employees who have left the textile industry.
The Textile management System includes Front Office Module,

Back Office Module, Human Resource Management Module, and
Accounts Module. This will help authorized user to insert, delete,
update or view the various records related to employees, products and
many more details. This makes the software flexible to use.

SYNOPSIS

SYNOPSIS
The proposed system is developed to create a simple, user
friendly and to use software that avoids the tedious task done by the
existing system. The proposed system is accessible only to
authenticated user of the system wherein all users of the system
contain their valid user id and password.
The proposed system handles the various requirements of the

textile. The administrator of the system has been assigned to make
their settings of the system. He also has the right to see the login
details.
The main requirement of this project is to make the task of

inserting the employee related details, product related details and
maintain them very simple and time saving. After inserting the
details it must be retrieved whenever necessary by search criteria
which will give the actual information needed by the valid user.
There are several reports that are generated based on the

employees and room which will show employee information, salary
records and attendance. It will also show room check in details and
check out details.

PROJECT DEFINITION:
Management of activities in a Textile Industry.
To replace their existing system
Connecting all the departments through a single system
WHY THIS TOPIC IS CHOSEN?

It is a software project which would be designed to simplify the
process of textile processing company. In textile processing
company there are lots of calculations like purchasing raw material,
sales, profit, loss, workers salary etc. These calculations are not
only complicated but also brain eating. Our project also consists of
tables to store the calculations done, individual detail of raw
material item, customers details, suppliers details, order details,
delivery completion details.
So the owner can have all these details in his personal

computers rather than having hundreds of registers.
We are designing our project with the help of C#.NET as front

end and Microsoft SQL server 2000 as back end.
The Textile Management System is end user application

software. The textile system we are designing that helps the textile
company to handle those task that had been handled manually.
The tasks like:

o Keeping record of raw material purchased.
o Gives and stores details of suppliers.
o Keeping record of stock available.
o Maintaining record of customers.
o Stores record of order placed by the customers.
o Gives details of orders to be processed.
o Gives information about orders that are completed.
o Gives information about uncompleted orders.
o Displays payment status of customers order like total

amount to be paid advanced paid by the customer,
balance amount.
o Generates billing information.
o Stores employee information.
o Generates report of suppliers.
o Generates report of customers.
o Generates report of orders.
o Generates stock report.

o Generates employee reports.
SCOPE OF THE PROJECT:

We plan to develop an application that reduces the manual work
of staff workers.
Make an application that can be used from any machine in the
LAN.
Make an application that give access to different department
according to their departments to their rights.
Application saves the data in the database in universal XML
format.
Reduce errors caused by manual processing of data.
Reduces the chance of stealing the information.
PURPOSE
The purpose of the project is to develop a Textile

management system, which will be used by the company
through which all purchase details of textile can be
managed by the company.
The system deals with very popular interface tool and
retrieval of the records is much faster than the present
system. Hence it cause to saving time for the further work.
The user can have fast interaction with the system by
inserting, update Customer etc. Because not only the front
end provides the faster interaction with the records but
with back end also provides the proper interaction with the
records and gives or prompts the information to the end
user if he is making error during work.

Searching features is quite faster than current system,
because it searches directly from system that is from the
front end.

METHODOLOGY (SUMMARY OF
THE PROJECT):
First it creates the database with all the tables if it is used first
time or uses the databases as soon as the application is started.
Provides access rights to different departments and then to
different users such as manager, staff, etc.
Front Offices department handles front desk operations such as
inquiries, booking and cancellation of textile products.
Top level department manages the product to be provided to the
customers assigning prescheduled reports to different staff, etc.
HR department manage the activities such as addition, updating
and deletion of product records.
Payroll Departments is concerned with employee salaries, etc.
CONTRIBUTION THIS SOFTWARE

WILL MAKE:
This software will bring user satisfaction. This software will
reduce the chances of information stealing and manipulating the
contents of vital information and documents. It will help in
managing activities in the Textile efficiently and effectively.
CONCEPTS & TECHNOLOGIES USED:

Visual Studio 2008 as front end
SQL 2005 as back end

HARDWARE AND SOFTWARE TO BE USED:
HARDWARE:
Server Computer:
PIV processor or higher
160 GB of hard disk space
1 GB or above RAM
Client Computer:
PIV processor or higher
512 MB OR above RAM
10 GB of hard disk space
SOFTWARE:
Server Computer:
SQL 2005
.NET Framework 2.0
Microsoft Windows XP with SP2/Vista
Client Computer:
.NET Framework 2.0
Microsoft Windows XP with SP2/Vista

DATA DICTIONARY
Table Name: login_details
Description: This table stores the details about the users of the
system.
Fields Data Type Description

Username varchar(50) It stores the name of the
user
Password varchar(50) Password of the user
Table Name: customer_details
Description: This table stores the details of all the Customers.


customer_id Int It stores the ID of the
customer
customer_nam varchar(100) It stores the name of the
e customer
contact_no varchar(50) It stores the contact no of
customer
email varchar(50) It stores the email of user
customer
address varchar(MAX) It stores the address of
customer
lock Int It stores the value either
0 or 1
Table Name: customer_order
Description: This table stores the order details placed by the

customers.


order_id Int It stores order ID
customer_id Int It stores customer ID
date smalldatetime It stores the date of order
customer_nam varchar(100) It stores the name of the
e customer
material_name varchar(50) It stores the name of the
material
rate varchar(50) It stores the rate
quantity varchar(50) It stores the quantity
total_expense varchar(50) It stores the total bill
amount
Advance varchar(50) It stores the advance paid
by the customer
Balance varchar(50) It stores the balance
remained by the
customer
0 or 1
Table Name: customer_bill
Description: This table stores the details about the customer

bill.

bill_no Int It stores the unique bill
no.
order_id Int It stores the order ID
customer_id Int It stores the customer ID.

customer_name varchar(100) It stores the name of the

customer
amount
by the customer
Balance varchar(50) It stores the balance
remained by the
customer
balance_to_be_ varchar(50) It stores the remaining
paid balance paid by the
customer
bill_date smalldatetime It stores the bill date
remain_balance varchar(50) It stores the value either
0 or 1
Table Name: Stock
Description: This table stores the raw material details.

material_id Int It stores the material ID
supp_id Int It stores the Supplier ID

material_name varchar(50) It stores the name of the

material
rate varchar(50) It stores the rate per
material
stock_availabili varchar(50) It stores the available
ty quantity of material
0 or 1
Table Name:supplier_details
Description: This table stores supplier details.


supplier_id Int It stores the supplier ID
supplier_name varchar(100) It stores the supplier
name
contact_no varchar(50) It stores the contact no
Email varchar(50) It stores the email id of
the supplier
Address varchar(MAX) It stores the address of
the supplier
Lock Int It stores the value either
0 or 1
Table Name: supplier_material
Description: This table stores material details supplied by the

supplier.


sr_no Int It stores the order id
supplier_id Int It stores the supplier id
supplier_name smalldatetime It stores the name of the
supplier
material_name varchar(100) It stores the material
name
rate varchar(50) It stores the rate per
material
stock varchar(50) It stores the quantity of
material
lock varchar(50) It stores the value either
0 or 1
Table Name: supplier_order
Description: This table stores supplier bill details.


order_id Int It stores the order id
supplier_name varchar(50) It stores the name of the
supplier
material_name varchar(50) It stores the material
name
Rate varchar(50) It stores the rate per
material
quantity varchar(50) It stores the quantity of
the material
amount
advance varchar(50) It stores the advance paid
by the user
Balance varchar(50) It stores the balance paid
by the user
Date smalldatetime It stores the bill date.
0 or 1
Table Name: supplier_bill
Description: This table stores supplier bill details.


bill_no Int It stores unique bill no
order_id Int It stores the order id
supplier_name varchar(50) It stores the name of the
supplier
amount
by the user
Balance varchar(50) It stores the balance paid
by the user
balance_paid varchar(50) It stores the remaining
balance
bill_date smalldatetime It stores the bill date.
Table Name: lock
Description: It stores other tables as fields of this table.


customer_detai Int It stores the value either
ls 0 or 1
customer_order Int It stores the value either
0 or 1
Stock Int It stores the value either
0 or 1
supplier_details Int It stores the value either
0 or 1
supplier_materi Int It stores the value either
al 0 or 1
supplier_order Int It stores the value either
0 or 1

OBJECTIVE AND
SCOPE OF THE
PROJECT

OBJECTIVE AND SCOPE OF THE

Projects
The existing system of the current textile industries needs to be
computerised which would result in fast, easy and smooth working. A
new systems need to be introduces for such industries where all
departments are interlinked. Each department should be automated as
separate interdependent module into application.
While application room reservation data, all necessary validation

should be performed. For example the system should check whether the
rooms of a specific type are available for booking for the duration
specified by the customer.
In order to develop the software for textile management,

we need to analyze the existing system and create a
design for envision system.
1. Implementing the functionality on the login page to validate

department credentials and provide the user with
appropriate features and functionality.
2. Implementing the functionality on the Front Office page to
view available product number the basis of cloth Type, Cloth
quality, and Size of cloth.
3. Implementing the functionality on the Front Office page to
enable user to book cloth they need, calculate customer
payment details and also help in cancellation of orders and
to store details about the Transport Agent who brings and
supplies the material.
4. Implementing the functionality on the Back Office page to
view the cloth Service report containing cloth maintenance,
raw material, etc.
update the cleaning status of the raw material.


mark attendance of the employees in current shift.
7. Implementing the functionality on the Human Resources
page to allot shifts to employee.
8. Implementing the functionality on the Account Page for
adding, updating and deleting Transport Agents details.
9. Implementing the functionality on the Human Resource page
to perform various activities such as adding, updating, and
deletion of employee record. Implementing the functionality
on the Accounts page to calculate Agent Commission and
Employees Payment details.

The system will accomplish the following

Objectives:
1. The authorized department of the company will be able to
log into the application using different logins, which will give
them access permission.
2. The Back Office department head will able to view and
manage the loading status of the material.
3. The HR department head will be able to manage employee
details, such as adding, updating and deleting employee
detail.
4. In case of cancellation, it is done in two ways pre-
cancellation and post-cancellation and necessary changes
in payment details are updated.
5. The accounts department will generate the reports for
material booked, quantity booked, Employee details,
customer details etc.
THEORETICAL BACKGROUND

Existing System
This system analysis yielded the simple basic system that the
TEXTILE was currently under the influence of. It was a manual system
that the textile companies are using currently. There was no system of
anything of the device to keep records of transaction.
The present system of the textile company today is totally based

on the manual data management. The details about the cloth recorded
in various registers. The users at have to manually enter the details.
The entries in various registers are made manually. When the data is to
be retrieved, the user has to go through the different registers as the
exact location of the data is not known. This is very time consuming
and tedious process.
The system has lots of calculations like the salary of the

employees and agent commissions. Since the user does all these
calculations manually there are chances or possibility of incorrect
calculations. It even becomes a tedious job of searching for the
different values in the various registers and then performing the
calculations.
The user has to manually go through the registers to create the

different reports that the staffs have to generate. This also is very time
consuming and tedious process. Thus keeping the entire problem in
mind schools definitely want to have software which will save their time
in entering, retrieving and calculations.

DRAWBACKS OF EXISTING SYSTEM
Following are the drawbacks of the existing system:
LIMITATIONS OF THE EXISTING SYSTEM
No Security has been provided to the data.

As the work is manual it consumes lot of time and energy.
Records of the customers and supplier are not maintained.
Finding a specific record required searching of more then half
of record.
Since the system is manual report creation takes lots of
timeprocess.
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.

DEFINITION OF PROJECT

DEFINITION OF PROBLEM
1) Maintaining detail:-
There are many more departments in the textile industry where all
the data maintaining in hand written register is too difficult at time
of adding data or retrieving data.
2) Absence of validation:-
As the storage and exchange of date is achieved only by user of

registers, which lack validation problem.
3) Inquire of available product :-
Checking status of the product was performed manually looking in

register which is time consuming.
4) No security facility:-
There is no security to handle the departmental data. Anyone can
manipulate the data.
5) Update problem:-
There is problem with updating or deleting of particular record.
For example they are not able to recollect the details of the
previous customers, employees, etc .

SOFTWARE /
TECHNOLOGIES USED

SOFTWARE / TECHNOLOGIES
USED
Software used in this project is:
1. FRONT END : Microsoft Visual Studio 2005(C#)

2. BACK END : Microsoft SQL Server 2005
3. HELP: Agora Help Generator
The explanations about these software / technologies are discussed in

details in next section.

EXPLANATION OF THE TECHNOLOGY
FRONT END:
MICROSOFT VISUAL STUDIO 2008:
Microsoft Visual Studio is an integrated development

environment (IDE) from Microsoft. It can be used to
develop console and graphical user interface applications along
with Windows Forms applications, web sites, web applications, and web
services in both native code together with managed code for all
platforms supported by Microsoft Windows, Windows Mobile , Windows
CE , .NET Framework , .NET Compact Framework and Microsoft Silver
light .
Visual Studio includes a code editor supporting IntelliSense as well

as code refactoring . The integrated debugger works both as a source-
level debugger and a machine-level debugger. Other built-in tools
include a forms designer for building GUI applications, web
designer, class designer, and database schema designer. It accepts
plug-ins that enhance the functionality at almost every levelincluding
adding support for source-control systems (like Subversion and Visual
SourceSafe ) and adding new toolsets like editors and visual designers
for domain-specific languages or toolsets for other aspects of
the software development lifecycle (like the Team Foundation
Server client: Team Explorer).
Visual Studio supports different programming languages by means of

language services, which allow the code editor and debugger to support
(to varying degrees) nearly any programming language , provided a
language-specific service exists. Built-in languages include C /C+
+ (via Visual C++ ), VB.NET (via Visual Basic .NET ), C# (via Visual C# ),

and F# (as of Visual Studio 2010 [ 2 ] ). Support for other languages such
as M , Python , and Ruby among others is available via language
services installed separately. It also
supports XML /XSLT , HTML /XHTML , JavaScript and CSS . Individual
language-specific versions of Visual Studio also exist which provide
more limited language services to the user: Microsoft Visual Basic,
Visual J#, Visual C#, and Visual C++.
Microsoft provides "Express" editions of its Visual Studio 2010

components Visual Basic, Visual C#, Visual C++, and Visual Web
Developer at no cost. Visual Studio 2010, 2008 and 2005 Professional
Editions, along with language-specific versions (Visual Basic, C++, C#,
J#) of Visual Studio 2005 are available for free to students as
downloads via Microsoft's Dream Spark program.
C# [LANGUAGE] AND .NET [TECHNOLOGY]

Microsoft C# .NET is a modern, object oriented, type
safe language. It enables programmers to quickly build a wide range of
applications for the Microsoft .NET Platform. C# pronounced as C
sharp, is designed to bring rapid development to the C++ programmer
without scarifying the power and control that have been a hallmark of
C++. C# support many features such as:
Automatic garbage collection

Rich intrinsic model for error handling
Decimal data type for financial application
Modern approach to debugging and robust security model .Net
technology is the platform for C# language for better work in
faster manner. C# .Net is the boost for the application work.
BACK END:

MICROSOFT SQL SERVER 2005:
Microsoft SQL 2005 is a relational database management

system from Microsoft. Its primary components are SQL OS
implementing basic services required for server, including thread
scheduling. I/O and Memory Management, Relational Engine
implementing relational database components having support for
databases, tables, query and stored procedures and finally Protocol
layer which exposes all these functionalities. Being Transact-SQL as its
primary query language a high performance data access is provided.
This SQL Server version is Microsofts next generation data

management and analysis software delivering increased scalability,
availability and security for enterprise data.
The next major enhancement in SQL Server 2005 which the

SQL Server 2005 lacks is the integration of a .NET compliant language
such as C#, ASP.NET or VB.NET to build objects (stored procedures,
triggers, functions, etc.), which enables the application to execute .NRT
code in the DBMS to take the advantage of the .NET functionality.
SQL Server 2005 has native capabilities to support

encryption of the data stored in user defined databases which SQL
Server 2000 lacks. Real Estate Web application utilizes these features
of Microsoft SQL Server 2005 to store the entire details of the property
listings along with its images.
Databases structure:-
Before storing the information, you need design a database
structure. Each database has following elements.
Field : - Contains one portion of the data, also

known as column.
Record : - Contains related information also known as
row. One or more field makeup a single record.

Database table:-
Made up by one or more records. Database file is physically
file stored on a disk and contains tables, query, forms and
report.
Database is collection of information about an entity such the
entire student enrolled at a school or all customers of a
company. Others example includes the phones book or address
book. Each access databases is comprised of 5 objects.
HELP:
AGORA HELP GENERATOR:

The Help Generator scans the application and automatically
generates HTML files, screenshots and other necessarily ingredients of
the help file. It links the help topics to the appropriate application forms
automatically thus making the help topics to the appropriate application
forms automatically thus making the help context sensitive. Then the
work starts: entering text in the prefabricated sections with the included
Help Editor. Compile the help project to a CHM file, browser based help
and printed documentation in one go, then after this help is ready.
The Help Generator is presented as a wizard. In this wizard you

can place settings as where to store files, CSS, adding hotspots yes or
no etc. The effect of our choices is immediately visible on the right side
of the window. That way we can control exactly what the generated help
will look like.
On the Contents tab we will find the contents tree. With right
clicking on the tree we change the order of topics or exclude topics to
be generated.
The following items are prepared: HTML Help files and screenshots for
each processed form are set, all project files (including table of
contents and index) are created, links from the help file to our
application.

This makes the Generator a time saving help authorizing tool

both for technical writers and programmers. The Generator scans the
application, each forms in our application is analyzed in detail in terms
of controls, menu, and tab order etcetera and presented as pages with
well formed HTML.

SYSTEM LIFE CYCLE
SYSTEM LIFE CYCLE

System life cycle is used by the system analysis to develop

information System including various phases as requirement,
validation, training meets maintenance. System Life Cycle should result
in a high quality system that meets or exceeds customer expectation
with in time and cost estimate works effectively and efficiently in the
current and plant maintenance and cost effective enhancing.
The success of the project is depends upon successful completion

of all the stages the various phases encountered during the lifecycle of
developing this web application.
System development lifecycle is concerned with the detail

management of all the components that go into development of a new
system.
System development lifecycle involves following steps:

a) Software Concept : It identifies and defines a need for
new system.
b) Requirement analysis : It analyses the information needs
of the end user.
c) Architectural design : It creates a blue print for the
design with the necessary for the hardware, software, people &
data resources.
Designers will produce one or more models of what they see a

system eventually looking like with the ideas from analysis section
either used or discarded. A document will be produce with the
description of the system but nothing is specific i.e. that might be
referred as touch screen or GUI operating system but no functionality
added to it.
a) Coding and debugging : Adding functionality to your design

using computer programming and finding out all possible error.

b) System testing : It evaluates the system actual

functionality.

SPIRAL MODEL

SPIRAL MODEL
As we know Textile Industry are very forward in their

applications work because the requirements which will fulfil for this
industry are regularly get upgraded.
To fulfil this need the Spiral Model is fits in the frame of

Textile industry. So we decided to use the Spiral model in our project
which is very useful in completion of the project.
Spiral model is a software development process containing

elements of both design and prototyping in stages, in an effort to
combine advantage of top down and bottom up concept known as
Spiral life cycle module. It is a system development method used in
information technology. This model of development method combines
the feature of the prototyping model and waterfall model. The spiral
model is intended for large experience and complicated project.
This process model combines iterative nature of incremental

model with systematic approach of waterfall model. This process
model has 5 phases: -
a) Communication
b) Planning
c) Modelling
d) Construction
e) Deployment.
In the communication phase we had discussion with client and

get requirement. After the completion of this phase then only we move
to the next phase i.e. planning in which we plan the project to reach the
clients expectations. Next phase is modelling we model clients
requirement and in construction phase we actually construct the project
work. The last is deployment in which we keep the maintenance which
is helpful after the completion of the project.
Each phase starts with a design phase goal and ends with
the limits running progress. Analysis and engineering efforts are

applied at each phase of project with an age towards the end of the
goal project. The steps in the spiral model can be realized as follows.
1. The new system requirements are defined as much details as

possible. This usually includes interviewing a number of users
and all the internal or existing system other aspects of the design
is created.
2. A preliminary design is created for the new system.
3. A first prototype of the new system is concentrated from the

preliminary design. This is usually a scaled down system and
represents an appropriate of the characteristics of the final
product.
4. A second prototype is evaluated by the four filed procedures.

i. Evaluating the first prototype in terms of its strength,
weakness and risks.
ii. Defining the requirements of the second prototype.
iii. Planning & designing the second prototype.
iv. Constructing & testing the second prototype.
5. Finishing prototype is evaluating ion the same manner as was the

previous prototype is developed from it according to the four
fooled procedure outlined above.
6. The preceding steps are integrated and the entire customer is

satisfied that the refined prototype represents the final
procedures designed.
7. The final system is constructed base on the refined prototype.
8. The final system is thoroughly evaluated & tested.

Spiral Approach
Advantages of the Spiral model
i. An estimate that is budget, scheduling etc, get more realized as

work progress because important issues are discovered earlier.
ii. It is more able to cope with the changes that software
development generally entails.
iii. Software engineers can get their hands in & start working on a
project earlier.

System requirements

SYSTEM REQUIREMENTS
HARDWARE REQUIREMENT:
Computer are never fast enough and rarely have

enough space or Memory, so as the faster and more
powerful your computer is better as suggest that an
ideal system for a professional
Intel Pentium P4
256 MB of memory
15 screen
1.00 GB of disk space
Realistically though, software be run with more modest

configuration and still provide reasonably performance.
The minimum that you need so that the performance
adequate is
Intel 80486x4 or better

16 MB or more of memory
15 screen
1 GB of disk space for a full flow work
And the components that are not variable are :
Keyboard (84 keys or more)
Mouse (any standard)
Printer (to print reports)
System Software Requirements:-
Operating System : Windows Operating

System
Front End: : C#.NET
Back End: : MS SQL server
2000

System planning
System Planning:
The project team consists of following two members:
1) Abhishek Medekar
2) Prashant Bharati
TASKS DESCRIPTION RESPONSIBILITIES
Requirement Gathering Study of existing system, Abhishek Medekar

advantages and
disadvantages, working on it Prashant Bharati
like where automation is
needed.
Designing Front-end(user interface Abhishek Medekar

form, user modification form
etc.) and Back-end designing Prashant Bharati
Coding Coding using Abhishek Medekar
C#.NET (Visual Studio Prashant Bharati

2008).
Testing Testing eachand every Abhishek Medekar

module
Prashant Bharati
Documentation Generating timely reports Abhishek Medekar

regarding activities
Prashant Bharati

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 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 materials reports in the form
of crystal reports.
Easy to search and update Customer or
supplier records by their Id.

ENTITY
RELATIONSHIP
DIAGRAM

E-R Diagram :-

STRUCTURCHART

Context Level
Diagram:-


PERT CHART
Pert chart

PERT(Program (or Project) Evaluation and Review Technique) is a method to analyze the
involved tasks in completing a given project, especially the time needed to complete each
task, and to identify the minimum time needed to complete the total project.
PERT was developed primarily to simplify the planning and scheduling of large and complex
projects.
It was able to incorporate uncertainty by making it possible to schedule a project while not
knowing precisely the details and durations of all the activities. It is more of an event-
oriented technique rather than start- and completion-oriented, and is used more in projects
where time, rather than cost, is the major factor. It is applied to very large-scale, one-time,
complex, non-routine infrastructure and Research and Development projects.
ADVANTAGES
PERT facilitates identification of the critical path and makes this visible
PERT facilitates identification of early start, late start, and slack for each activity,
PERT provides for potentially reduced project duration due to better understanding of
dependencies leading to improved overlapping of activities and tasks where feasible.
The large amount of project data can be organized & presented in diagram for use in
decision making.

Pert chart
Design Code Testing

Database Database
Analysis
Finish
Design Code GUI

GUI
Install

TESTING

Testing
Software testing is processes used to measure the quality of
develop computer software. Usually quality is constraints to such topic
as correctness, completeness, security but it can also include more
technical re1quirement as described by ISO standard such as
capability, reliability, efficiency, portability, maintainability, compatibility
and usability.
Testing is the process of technical investigation performed on

behalf of end use r or client i.e. intended to reveal quality related
information about the product with respect to the context in which it is
intended to operate.
This includes the process of executing the program or application

with the intention of finding errors.
Testing can never completely establish the correctness of

computer software. An important point is that software testing should be
distinguishing from the separate discipline of software quality
assurance which includes all business process not just testing.
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design, coding.
Testing objectives
1. Testing is a process of executing a program with the intent of finding an
error.
2. A good test case is the one that has high portability of finding an as-yet
undiscovered error.
3. A successful test is one that uncovers an as-yet discovered error.

The main objective here will be to design test cases to uncover different
classes of errors and to do so with minimum amount of time and efforts. If
testing is conducted successfully it will uncover errors in the software.
Another advantage is that it demonstrates that software functions appear
to be working according to the specifications and performance
requirement have been met.
But Testing cannot show the absence of defects it can show only that
software errors are present.
Strategies used for software testing
The software engineering process is viewed as spiral as shown:
Unit testing begins at the vortex of the spiral and concentrates at
the each unit of the software as implemented in the source code. Unit
testing assures each module tested individually functions properly as a
unit.
Integration testing focuses on the design and construction of the
software architecture. It is a systematic technique for constructing a
program structure while conducting tests to uncover errors associated
with interfacing. The objective is to take unit-tested module and build a
program structure that has been specified as design.
Validation testing takes care of the requirements established as
part of the software requirements analysis are validated against the

software that has been constructed. It is said to be successful when the
software functions in a manner that can be reasonably expected by the
customer.
System testing tests software and other system elements as a
whole. These tests fall outside the scope of software engineering process
and are not conducted solely by the software developer.
VALIDATION TESTING:
Software validation is achieved through different tests that

demonstrate conformity with requirements. In general, validation
is the process of checking if something satisfied a certain criteria.
Validation implies one is able to document that a solution or
process is correct or suited for its intended use.
Validation can be too declared or make legally valid or to

prove valid or conform the validity of data, information or process.
Validation is important because it disallow data that cannot
possibly be either true or real to be entered into database or
computer system.
The methodology used for maintaining data integrity is as follows:

Numeric validation
Data validation
In our system we are going to use the Black box testing in the
following criteria:
i. Easy to compute data:

Ensure legitimate values which the system should
accept and save in the database or process the data

to display any of the required results. We ensured that

the system accepted and proposed all such data and
give required results.
ii. Extreme data testing:
This test case carried out data overflow and under

flow checks to make sure that the data lies within the
available set of data range for that particular data type
and the particular data field.
e.g. an integer input should lies between 32768 and
32767, company code is a four digit positive number
etc.
iii. Invalid inconsistent database input:
When primary key values were entered it was checked

whether they conflicted with existing values. When
foreign key values were entered they were validated
for referential integrity violations.
SECURITY TESTING
Login screen provides access too only authorized employee

using a user password combination. So we provide the
encryption of password before storing in the database.
During security testing, the tester plays the important role of
an individual who desires to penetrate the system.
The tester may attempt to acquire password through
external clerical means may attack the system with custom
software designed to break down any defence that have
been constructed
.
END USER TESTING:

In this software the performance has been in line with the

expectations of the client company. Testing is done to find
information critical decisions about the project or products
that are made on basis of the information. Testing is
process of executing program with the intent of finding
error. This phase in our software accomplishes:
Corrective faults.
Improved performance.
Adapt the product to a changed environment and
implementing changes.
Evaluation by the external guide.
WHITE BOX TESTING:
White box testing is sometimes called glass box testing is

test case design method that uses control structure of
procedure design to derived test case. Using White box
testing methods derived cases that:-
Guarantee that all individuals paths within module

have been exercise at least once.
Exercise all logical decision on their true and false
sides.
Exercise all loops at their bounders and within their
optional bound.
BLACK BOX TESTING:
Black box testing is also called behaviour testing focuses on

functional requirement of software. Black box testing enables the
software engineer to derive the set I\P condition that will fully
exercise all functional requirement of program. Black box testing
attempt to find in following categories:-
Incorrect or missing function.

Interface error.

Error in data structure or external database access.

Behaviour or performance error.
Initialization and termination error.
REPORT LIST

REPORT LIST
Many reports can be created in this. The main advantage of the

reports is that they are dynamic and are generated according to the
user need.
The report can be saved in XML format so that they can be easily
transferred or there is option to take the print of the report by employee
name, by employee id, by departments, by room numbers, by room type
etc.
REPORTS:
1. FRONT OFFICE
a. Check in report
b. Check out report
c. Hall detail report
2. HUMAN RESOURCE
a. Employee details
b. Shift detail
c. Attendance
3. ACCOUNTS
a. Agents
b. Employee Salary
4. EXAMINATION RESULT

Data Flow
Diagrams:-
1.1
Stock
Enter
custom Customer_det
er ails
details
1.2
Places
Admin custom
er order Customer_ord
er
1.3
Generat
Customer_bill
es
custom
er bill

2.1
Stock
Enter
supplier
details supplier_detai
ls
2.2
Enter
Admin supplier
material supplier_mate
s rial
2.3
Places
supplier_order
supplier
order
2.4
Generat supplier_bill
es
supplier
bill
3.1
supplier_detai
Enter ls
Admin stock
details Stock

DATA MODULES AND THEIR DESCRIPTION
Login:-
Enter User ID and password to login.

Reset clears the fields so that the user can enter the
username and password again.
If the entered username or password is wrong the
message box would be prompted displaying Invalid
Login.

MDI Form:-
This form acts as container for all other forms.

It contains main menu having submenus like
Customer Details, Supplier Details, etc.

Customer Details Form:-

This form allows user to view Customer
details.
New Button: It allows user to enter new
customer record.
Save Button: It allows user to save the
record to database.
Update Button: It allows user to update the
record from data grid view.
Exit Button: Exits the form.

Customer Order Form:-
This form allows user to enter Customer Order

details.
Save Button: It allows user to save the record to
database.
Clear Button: It allows user to clear all the fields
of the form.
Calculate Button: It allows user to calculate total
expenses based on quantity and rate entered by
the user.

Update Customer Order Form:-
This form allows user to update Customer Order

details. User can select existing order id from the
combobox and can update quantity or balance
field.
record and save to database.
Delete Button: It allows user to delete the record
from the database.
the user.


Customer Bill Form:-

This form allows user to enter Customer Bill
details.
record to database.
Clear Button: It allows user to clear all the
fields of the form.

Supplier Details Form:-
This form allows user to view Supplier details.

New Button: It allows user to enter new Supplier
record.
database.
record from datagridview.

Supplier Order Form:-
This form allows user to enter Supplier Order

details.
database.
Clear Button: It allows user to clear all the fields
of the form.
the user.


Update Supplier Order Form:-

This form allows user to update Supplier
Order details. User can select existing order
id from the combobox and can update
quantity or advance field.
record and save to database.
Delete Button: It allows user to delete the
record from the database.
Calculate Button: It allows user to calculate
total expenses based on quantity and rate
entered by the user.


Supplier Material Form:-

This form allows user to enter materials
supplied by the supplier. The user has to
select supplier Id from the combo box.
record to database.
Supplier Bill Form:-

This form allows user to enter Supplier Bill

details.
record to database.
fields of the form.

Raw Material Form:-

This form allows user to add new material
supplied by the supplier.
record to database.
fields of the form.

Update Raw Material Form:-

This form allows user to update material
supplied by the supplier.
record to database.
Delete Button for the datagridview: It
allows user to delete particular material
record from the datagridview.
Delete Button:

Update Raw Material Form:-

Deleting particular record from the data
grid view.

Stock Form:-
This form allows user to view the stock
details. The user has to select material name
from the combo box.
View All Button: It allows user to view all
available stock details in the data grid view.

Multiuser Validation:-

Reports:-
Customer Report:-


Supplier Report:-

Raw Material Report:-

Sales Report:-


CURRENT SYSTEM
In Current System all the works has been done manually.

The Since all the works are done manually it does not provide
any proper information about
the particular customer records or their bills.
Some issues may remain unresolved for a very long time.
The requested textile is checked for availability.
If available then the textile is selected.
All related tables have to be manually updated.
Cost is manually calculated by grade and textile rate.
LIMITATIONS OF THE EXISTING SYSTEM
No Security has been provided to the data.

As the work is manual it consumes lot of time and energy.
Records of the customers and supplier are not maintained.
Finding a specific record required searching of more then half
of record.
Since the system is manual report creation takes lots of time.

Textile Management System Simplifies Operations

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Textile Management System Simplifies Operations

Uploaded by

Copyright:

Available Formats

TEXTILE MANAGEMENT SYSTEM

TEXTILE MANAGEMENT SYSTEM

Under the Guidance of

MR. VINAY DUBEY

MRS. SNEHALATA AGARWAL

Submitted in partial fulfilment of the requirement for qualifying

156, MAHATMA GANDHI ROAD,

FORT, MUMBAI 400 032

B.Sc (IT) ELPHINSTONE COLLEGE Page 1

Many People have contributed to this project, and I would like to

Special thanks to our coordinator for assisting us to complete our

We should also like to thank our Principal for providing us a library,

I extend a special thank you to my parents, my family members and

B.Sc (IT) ELPHINSTONE COLLEGE Page 2

3. Objective and Scope of project

6. Explanation of the technologies

7. System Life Cycle

10. System planning

11. Gantt Chart

12. Entity Relationship Diagram

13. Structure Chart

14. Pert Chart

16. Report List

17. Table List

19. Future Enhancements

B.Sc (IT) ELPHINSTONE COLLEGE Page 3

Textile Management System is software for textile industries,

The Textile Management System is designed to allow the industry

The Textile management System includes Front Office Module,

B.Sc (IT) ELPHINSTONE COLLEGE Page 4

B.Sc (IT) ELPHINSTONE COLLEGE Page 5

The proposed system handles the various requirements of the

The main requirement of this project is to make the task of

There are several reports that are generated based on the

B.Sc (IT) ELPHINSTONE COLLEGE Page 6

WHY THIS TOPIC IS CHOSEN?

So the owner can have all these details in his personal

We are designing our project with the help of C#.NET as front

The Textile Management System is end user application

The tasks like:

B.Sc (IT) ELPHINSTONE COLLEGE Page 7

o Keeping record of raw material purchased.

o Gives and stores details of suppliers.

o Keeping record of stock available.

o Maintaining record of customers.

o Stores record of order placed by the customers.

o Gives details of orders to be processed.

o Gives information about orders that are completed.

o Gives information about uncompleted orders.

o Displays payment status of customers order like total

o Generates billing information.

o Stores employee information.

o Generates report of suppliers.

o Generates report of customers.

o Generates report of orders.

o Generates stock report.

B.Sc (IT) ELPHINSTONE COLLEGE Page 8

o Generates employee reports.

SCOPE OF THE PROJECT:

The purpose of the project is to develop a Textile

B.Sc (IT) ELPHINSTONE COLLEGE Page 9

CONTRIBUTION THIS SOFTWARE

CONCEPTS & TECHNOLOGIES USED: