Project Doocuments (Repaired)

TEXTILE MANAGEMENT SYSTEM
A Project Report
Submitted in partial fulfilment of the
Requirement for the award of the degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY),

-By
JYOTI GHANSHYAM GUPTA

Seat No
Under the esteemed guidance of

Mrs. Anjali Gangal
Designation
DEPARTMENT OF INFORMATION TECHNOLOGY
K.B GIRLS WOMAN COMMARECE AND ART COLLEGE

(Affiliated to University of Mumbai)
THANE, 600400
MAHARASHTRA
2018 – 2019
1
KB GIRLS WOMAN COMMERCE AND ARTS COLLEGE
(Affiliated to University of Mumbai)
THANE – MAHARASHTRA - 400600
DEPARTEMENT OF INFORMATION TECHNOLOGY
CERTIFICATE
This is to certify that the project entitled,” TEXTILE MANAGEMENT SYSTEM “, is

benefited work of JYOTI GHANSHYAM GUPTA bearing seat No:(number) submitted in
partial fulfilment of the requirement for the award of degree of BACHLOR OF SCIENCE in
INFORMATION TECHNOLOGY from University of Mumbai
Internal guide Coordinator
External Examiner
Date: College Seal
2
ABSTRACT
Content
Note: Entire document should be with

Line spacing and all paragraphs should start with 1 tab space.
3
ACKNOWLEDGEMENT
The acknowledgement should be in times new roman,
4
DECALARATION
Content
I hereby declare that the project entitled, “TEXTILE MANAGEMNET

SYSTEM”
Done at THANE, has not been in any case duplicated to submit to any other university for
the award of any degree. To the best of my knowledge other than me, no one has submitted to
any other university.
The project is done in partial fulfilment of the requirement for the award of degree of
BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY) to be submitted as final
semester project as part of our curriculum.
5
TABLE OF CONTENTS
SR NO. Contents Page no.
1 Introduction 1-4
1.1 Background
1.2 Objective
1.3 Purpose and scope
1.2.1 purpose
2 Survey Of Technology 5-8
3 System Analysis 9-18
3.1 Existing System
3.2 Proposed System
3.3 Requirement Analysis
3.4 Hardware Requirement
3.5 Software Requirement
3.6 Justification of Selection Of Technology
4 System Design 19-32
4.1 Module Division
4.2 Data Dictionary
4.3 ER Diagram
4.4 DFD Diagram
5 Implantation And Testing
6
7
6
CHAPTER-1
INTRODUCTION
1.1 BACKGROUND
It is a software project which is 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, worker`s salary etc. This project also consists of
details, delivery completions details and generates reports.
So, the owner can have all these details in his personal computers rather than having
Hundreds of registers.
The Textile Management System is end user application software. This project helps The
textile company to handle those tasks that had been handled manually. The tasks like:
 Keeping record of raw material purchased.

 Gives and store details of suppliers.
 Keeping record of stock available.
 Maintain record of customers.
 Stores record of order placed by the customers.
 Gives details of orders to be processed.
 Gives information about orders that are completed.
 Gives information about uncompleted orders.
 Displays payment status of customers order like total amount to be paid
 Advanced paid by the customer, balance amount.
 Generate billing information.
 Generate report of Suppliers.
 Generate report of Customers.
 Generate report of Raw Materials.
 Generate Sales report.
 Generate Purchase reports.
7
1.2 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 per 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 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 causes 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
1.3 OBJECTIVES
The existing system of the current textile industries needs to be computerised
which would result in fast, easy and smooth working. A new system 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 the duration specified by the customer.
8
1. Implementing the functionality on the login page to validate department

credentials and provide the user with appropriate features are
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 help in
cancellation of orders and to store details about the transport agent who
bring and supplier the materials.
4. Implementing the functionality on the back-office page to view the cloth
services report containing cloth maintenance, raw material, etc.
5. Implementing the functionality on back office page to update the cleaning status of raw
material.
1.4 ACHIEVEMENTS
1. How to study project needs and requirements.
2. Documentation of software system.
3. Familiar with technologies like Asp.net, C#, Ajax, SQL, Html, JavaScript.
4. Completed life cycle of project development from requirement to testing phase.
9
CHAPTER-2
SURVEY OF TECHNOLIES
2.1 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 than half of record.
 Since the system is manual report creation tasks lots of time.
 No multiuser environment is provided.
 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 manual work and
manpower.
 Hence processing becomes faster.
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 provided by means of Login Form. Only authorized users can
have access to the system.
 The system allows user 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, Suppliers reports, sales
and purchase reports as well as raw material`s reports in the form of crystals reports.
 Easy to search and update Customer or supplier records by their Id.
10
2.3 HARDWARE REQUIREMENTS

Computer are never fast enough and rarely having 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.0 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 preformation adequate is
 Intel 80486*4 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)
2.4 SOFTWARE REQUIREMENTS

Operating System: Windows Operating System
Front End : C#.NET
Back End : MS SQL server 2012
The experiences about these software / technologies are discussed in details in next section.
11
EXPLANATION OF THE TECHNOLOGY
FRONT END:
MICROSOFT VISUAL STUDIO 2017:
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 platform
supported by Microsoft Windows, Window mobile, Window CE, .Net framework,
.Net compact framework and Microsoft silver light.
BACK END:
MICROSOFT SQL SERVER 2012
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
2.5 JUSTIFY OF PLATFORM

The .NET Framework programming model that enable developers to build web-based
application which expose their functionality programmatically over a network using standard
protocols such as SOAP and HTTP. Developer tools such as Microsoft visual studio .NET,
which provide a repaid application integrated development environment for programming
with the .NET Framework.
 A set of server including Microsoft Windows 2000, Microsoft SQL, server and
Microsoft BizTalk Server that integrates, runs, operates and manages XML web
services and applications.
 Client software such as windows XP, windows CE and Microsoft office XP that helps
developers deliver a deep and compelling user experiences across a family of devices
and existing products.
12
Chapter -3
REQUIREMENT AND ANALYSIS

3.1 PROBLEM DEFINATION
 Maintaining detail-
There are many more departments in the textile industry in the textile industry
where all the data maintaining in hand written register is too difficult at time of
adding data or retrieving data.
 Absence of validation-
As the storage and exchange of data is achieved only by user of register, which
lack validation problem.
 Inquire of available product-

Checking status of the product was performed manually looking in register
which is time consuming.
 No security facility-
There is no security to handle the department data. Anyone can manipulate the
data.
 Update problem-
There is problem with updating of particular record for ex. They are not able to
recollect the details of the previous customers, Employees, etc.
13
 3.2 Planning and scheduling
TASKS DESCRIPTION RESPONSIBILITY

Requirement gathering Study of existing system
advantage and disadvantage
working on it like where
automation is needed
Designing Front-end (user interface
form, user modification form
etc.) and Back-end designing
Coding Coding, using
C#.NET (visual studio 2008.)
Testing Testing each and every
module
Documentation Generating timely report
regarding activities
14
 GRANT CHART
ANALYSIS DESIGN
July August September

Week Week Week Week Week Week Week Week Week Week Week Week
1 2 3 4 1 2 3 4 1 2 3 4
System
Analysis
Study of
current
System
Documentat
ion Of
Proposed
System
Study Data
Of System
& draw
class
Diagram
Study Of
Scenario &
documentati
on
Draw event
table
Draw use
case
Diagram
Draw
Sequence
diagram
Draw
Collaboratio
n diagram
Draw State
Chart
diagram
Present
System
requirement
Planning Execution Break
15
Design phase
October November December

1 2 3 4 1 2 3 4 1 2 3 4
System
design
Database
design
Final design
pattern to
be
implement
List and
description
categories of
Design user
interface
and method
calls
Draw I/P
Screen
Draw use
case
Diagram
Planning Execution Break
January February March

1 2 3 4 1 2 3 4 1 2 3 4
Coding
Testing
Planning Execution
16
 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 completed each
task, and to identify the minimum time needed to completed the total project.
--PERT was developed primary to simplify the planning and
Design Code Testing

Database Database
Analysis
Finish
Design Code
GUI GUI
Install
17
 ADVANTAGES
 PERT facilities identification of the critical path and makes this visible.
 PERT facilities identification of early start, late start, and slack for each
activity.
 PERT provided 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.
18
3.3 model Conceptual
 Data flow diagram
Places Stock
customer
details Customer details
Admin Places
customer Customer_ order
order
Generates
Customer_ bill
customer
bill
Supplier details
Enter
Admin
Stock
s Stock
Details
19
Enter stock
supplier
Supplier details
details
Enter
admin supplier Supplier materi
materials
Places
supplier Supplier_order
order
Generates
supplier Suppier_bill
bill
20
E-R DIAGRAM
total
name
advance
material
Customer_n bill id
a Bill_no
date
quantity
Order
balance
Order_id advance
Bill_no Customer_bill Bill_dat

e
Customer_id Customer_order balance
idid
Supplier_nam
eme
Genera
Suppli tes
Supplier_order er
Sales Report
Supplier_id
Order_id
Login _details mainta Textile generat

in management es
password
User_id
Purchase Report
User_name
Contact_no
Customer_detai
mainta
Supplier_details ls
ins email
email
address
Customer_na
Supplier_id
me Customer_id
address
Contact_no Supplier_name
mme
21
OBJECT ORIENTED DIAGRAM
Customer details
+customerorderdetails
Customer order
+Newcustomerorder
+updatecustomerorder +addcustomerorder
+updatecustomer
+viewcustomerorder
Stock
ADMIN +addstock +updatestock
+addadmin +deletestock +viewstock
+deleteadmin +viewadmin
+updateadmin
Supplier_order
+addsupplierorder
+updatesupplierorder
+deletesupplierorder
Materials +viewsupplierorder
+Addmaterial
+deletematerial
+updatematerial Supplier
+viewmaterial
+addsupplier
+updatesupplier
+deletesupplier
+viewsupplier
22
CHAPTER -4
SYSTEM DESIGN
 4.1 BASIC MODULE

 LOGIN:
 Enter user ID and password to login.
 Reset clears the fields so that the user can enter the username and password
login.
 If the entered username or password is wrong the message box would be
prompted displaying “invalid login”.
 Enter the new 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.
 Add Button: it allow user to save the record to database.
 Update Button: it allows user to update the record from data grid view.
 Delete Button: delete the form.
 Customer order form:

 This form allows user to clear all the fields of the form.
 Add Button: it allows user to save the record to database.
 New Button: it allows user to clear all the fields of the form.
23
 Calculate Button: it allows user to calculate total expenses based on quantity

and rate entered by the user.
 Update Button: it allows user to update the record from data grid view.
 Update Customer Order Form:

 The form allows user to update customer order details. User can select
existing order id form the combo box and can update quantity or balance
field.
 Update Button: it allows user to update the record and save to database.
 Deleted 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.
 Customer Bill form:

 This form allows user to enter customer bill details.
 Add Button: It allows user to save the record to database.
 Create Button: It allows user to clear all the fields of the form.
 Print button: print the bill.
 Supplier Details Form:

 This form allows user to view Supplier details.
 New Button: It allows user to enter new Supplier record.
 Update Button: It allows user to update the record from data gridview.
 Supplier Order Form:

 This form allows user to enter Supplier Order details.
24
 New Button: It allows user to clear all the fields of the form.
 Calculate Button: It allows user to calculate total expenses based on
 Update Button: it allows user to update the record and save to database.
 Update Supplier Order Form:

 This form allows user to update Supplier Order details. User can select
existing order id from the combo box and can update. Quantity or advance
filed.
 Update Button: It allows user to update the 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
 Supplier Material Form:

 This form allows user to enter materials supplied by the supplier. The enter
materials select supplier id from the combo box.
 Save Button: It allows user to save the record to database.
 delete Button: delete the form.
 Update Button: It allows user to update the record and save to database.
 Supplier Bill Form:

 This form allows user to enter Supplier Bill details.
 Create Button: It allows user to clear all the fields of the form.
 Print button: print the bill
25
 4.2 DATA DESIGN
Data base design is the organisation of data according to a database model. The
designer determines what data must be stored and how the data element interfaces.
With this information, they can begin to fit the data to the database model.
Data design involves classification data and identifying interrelationship. This
theoretical representation of the data is called ontology. The ontology is the theory
behind the database design.
 4.2.1 SCHEMA DESIGN

Data base schema……the term schema refers to the organization of data as a
blueprint of how the database is constructed (divided into databases). The formal
definition of a database schema is a set of formal (sentences) called integrity
constrains imposed on a database.
26
 4.2.2 DATA INTERGRITY AND CONSTRAINTS
Table Name: login details
Description: This table stores the details about the users of the system.
Fields Data Type Description

Username varchar(MAX) IT stores the name of the
user
Password varchar(MAX) Password of the user
Table Name: customer details

Description: This table stores the details of all the customer.
Customer_id Bigint It stores the ID of the
customer
Customer_name Varchar(MAX) It stores the name of the
customer
Customer_add Varcahr(MAX) It stores the address of
customer
Customer_Email Varchar(50) It stores the email of user
customer
Customer_mob Bigint It stores the contact no of
customer
27
Table Name: customer_order

Description: This table stores the order details placed by the customer.
Order_id Bigint It stores the order ID
Material_name Varchar(MAX) It stores the material name
Material_rate Bigint It stores the rate per
material
Material_quantity Bigint It stores the material of
the quantity
Material_total Bigint It stores the total of the
material
Material_advance Bigint It stores the advance of
the material
Material_balance Bigint It stores
Customer_id Bigint It stores
Customer_name Varchar(MAX) It stores
Order_date Varchar(MAX) It stores
payment Bigint It stores
Bill_no Bigint It stores
Bill_date Varchar(MAX) It stores
Table Name: supplier_details

Description: This table stores supplier details.
Supplier_id Bigint It stores the order id
Supplier_name Varchar(MAX) It stores the supplier name
Supplier_add Varchar(MAX) It stores the address of the
supplier
Supplier_Email Varchar(MAX) It stores the email id of the
28
supplier
Supplier_mob bigint It stores the mob no
Supplier_mob2 Bigint It stores the mob no 2
GST Bigint It stores the GST no
Table Name: supplier_order

Description: This table stores supplier order details.
Order_id Bigint It stores the order id
Material_id Bigint It stores the supplier id
Material_name Varchar(MAX) It stores the name of the
supplier
Material_rate Bigint It stores the material name
Material_quantity Bigint It stores the rate per
material
Material_total Bigint It stores the quantity of
the material
Material_advance bigint It stores the total bill
amount
Material_balance bigint It stores the advance paid
by the user
Supplier_id bigint It stores the balance paid
by the user
Supplier_name Varchar(MAX) It stores the bill date.
Order_date Varchar(MAX) It stores the material id
Supplier_GST Bigint It stores the supplier GST
no
Payment Bigint
Bill_no Bigint
Bill_date Varchar(MAX)
29
Table Name: material details.

Description: This table stores material details.

Material_id Bigint It stores the material id
Material_name Varchar(MAX) It stores the material name
Quantity Bigint It stores the quantity of the
material
Prize Bigint It stores the prize of the
material
Sale quantity Bigint It stores the
Sale prize Bigint It stores the
Stock Bigint It stores the
30
 4.3 LOGIC DIAGRAM
Context level diagram:-
Admin Customer
Textile
management
system
Supplier Stock
31
 USE CASE DIAGRAM
Customer details
Supplier details
Admin
Material details
Stock details
Sales order details
Purchase order
32
Component diagram
Supplier_details
+supp_id integer
+supp_name:string
Customer _details Matrialcomponent
+cust_id integer +material_id integer
+cust_name: string +material_name:

string
Supplierordercompo
nent
+supplier_bill_no:da
Stockcomponent tetime
+material_id: integer
+avail_qty: integer
Customerordercomp
onent
_customer_bill_no:
integer
33
ACTIVITY DIAGRAM
LOGIN
ENTER
CUSTOMER
SEARCH MATERIAL
MATERIAL PURCHAS
BILL GENERATE
RECEIVE PAYMENT
34
 4.3.2 DATA STRUTURES
Before storing the information, you need design a database structure. Each
database has following elements.
 Filed :- contains one portion of the data, also known as column.
 Record :- contains related information also knows as row. One or more

filed makeup a single record.
 DATABASE TABLE
 Made up by 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. Other
example includes the phone book or address book. Each access
database is comprised of 5 objects.
 4.3.3 ALGORITHMS DESIGN
Processing of cotton involves

 Preparatory processes
 Sparring
 Weaving
 Finishing
Preparatory process
 Preparatory
 Process involves
 Ginning, blending
 Carding, combing
 Drawing
35
4.4 USER INTERFACE DESIGN
User interface design(UI) or user interface engineering is the design of user

interfaces for machines and software, such as computers, home appliances, mobile devices,
and other electronic devices, and other electronic devices, and other electronic devices, with
the focus on maximizing usability and the user experience. The goal of user interface as
simple and efficient as possible, in terms of accomplishing user goals (user centred design)
4.5 SECURITY ISSUES
 INFORMATION SECURITY POLICY

Information security policies are a set of statements
consisting of management directions, decisions and high-level
security principles that the organization must comply with in order to
achieve the required level of security. The information security. The
information security policy templates in this package are developed
in alignment with the ISO/IEC 27002 standards.
 SECURITY ARCHITECURES
Security architecture is the organization of security
controls in order to achieve its enablement and control objectives that
address security risks to information, information systems, and
information processing facilities. This templates provides a life-cycle
oriented, risk-driven, defence-in-depth, and traceability assured
methodology to information security architecture.
36
Chapter -5
Implementation and testing
5.1 Code (Place Core segment)
HOME PAGE
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Drawing;
using System.Linq;
using System.Text;
using System.Windows.Forms;
namespace WindowsFormsApplication1
{
public partial class Home : Form
{
public Home()
{
InitializeComponent();
}
private void Home_Load(object sender, EventArgs e)

{
private void homeToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
Home l1 = new Home();
l1.ShowDialog();
}
private void stockToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
Stock_available si = new Stock_available();
si.ShowDialog();
}
37
private void exitToolStripMenuItem1_Click(object sender, EventArgs e)

{
private void updateDeleteSupplierToolStripMenuItem_Click(object sender, EventArgs

e)
{
this.Hide();
SupplierInfo si = new SupplierInfo();
si.ShowDialog();
}

{ System.Windows.Forms.Application.Exit();
private void addSupplierToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
SupplierOrder si = new SupplierOrder();
si.ShowDialog();
}
private void addCustomerToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
CustomerInfo si = new CustomerInfo();
si.ShowDialog();
}
private void supplierReportToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
SupplierReport si = new SupplierReport();
si.ShowDialog();
}
private void button1_Click(object sender, EventArgs e)

{
this.Hide();
Material si = new Material();
si.ShowDialog();
}

{
this.Hide();
38

si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}
private void customerOrderReportToolStripMenuItem_Click(object sender, EventArgs

e)
{
this.Hide();
CustomerReport si = new CustomerReport();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
CustomerBill si = new CustomerBill();
si.ShowDialog();
}
private void updateDeleteCustomerToolStripMenuItem_Click(object sender, EventArgs

e)
{
this.Hide();
CustomerOrder si = new CustomerOrder();
si.ShowDialog();
}
private void exitToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
si.ShowDialog();
}
private void customerBillsToolStripMenuItem_Click(object sender, EventArgs e)

{
39
this.Hide();
si.ShowDialog();
}
private void supplierBillsToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
SupplierBill si = new SupplierBill();
si.ShowDialog();
}
private void stockReportToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
StockReport si = new StockReport();
si.ShowDialog();
}
private void saleReportToolStripMenuItem_Click(object sender, EventArgs e)

{
this.Hide();
PurchaseSaleReport si = new PurchaseSaleReport();
si.ShowDialog();
}
}
}
40
Login code
using System;
using System.Data;
using System.Linq;
using System.Text;
using System.Data.Sql;
using System.Data.OleDb;
using System.Data.SqlClient;
{
public partial class Login : Form
{
SqlConnection con = new SqlConnection(@"Data Source=DESKTOP-

2O8FVUK\SQLEXPRESS;" + "Initial catalog=TextileManage;" + "Integrated
Security=True");
public Login()
{

{
con.Open();
string userid = textBox1.Text;
string password = textBox2.Text;
SqlCommand cmd = new SqlCommand("select userid,password from login where
userid='" + textBox1.Text + "'and password='" + textBox2.Text + "'", con);
SqlDataAdapter da = new SqlDataAdapter(cmd);
DataTable dt = new DataTable();
da.Fill(dt);
if (dt.Rows.Count > 0)
{
MessageBox.Show("Login sucess Welcome to Homepage");
this.Hide();
Home h1 = new Home();
h1.ShowDialog();
}
else
{
MessageBox.Show("Invalid Login please check username and password");
41
}
con.Close();
}
private void Login_Load(object sender, EventArgs e)

{

{
this.Hide();
ResetPassword h1 = new ResetPassword();
h1.ShowDialog();
}
private void textBox1_TextChanged(object sender, EventArgs e)

{
}
}
}
42
Reset password
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class ResetPassword : Form
{
Security=True");
public ResetPassword()
{
}
private void label3_Click(object sender, EventArgs e)

{

{
if (!textBox3.Text.Equals(textBox5.Text))
{
label10.Text="Password Not Match";
}
else
{
label10.Text="";
}
}

{
this.Hide();
Login h1 = new Login();
h1.ShowDialog();
}

{
43
if (textBox1.Text.Equals("") || textBox2.Text.Equals("") || textBox3.Text.Equals("") ||

textBox4.Text.Equals("") || textBox5.Text.Equals(""))
{
MessageBox.Show("Please Fill All fields!!!");
}else{
String comp = "",us="",ps="";
String use = textBox1.Text;
String pass = textBox2.Text;
con.Open();
SqlCommand cmd1 = con.CreateCommand();
cmd1.CommandType = CommandType.Text;
cmd1.CommandText = "select userid AS TOT,password AS TOT1 from login";
SqlDataReader rd = cmd1.ExecuteReader();
while (rd.Read())
{
us = rd["TOT"].ToString();
ps = rd["TOT1"].ToString();
if (us.Equals(use) && ps.Equals(pass))

{
comp = "YES";
}
}
con.Close();
if (comp.Equals("YES"))
{
String newuid = textBox4.Text;
String newpass = textBox5.Text;
SqlDataAdapter ddd = new SqlDataAdapter();
ddd.UpdateCommand = new SqlCommand("UPDATE login SET userid='" +
textBox4.Text + "',password='" + textBox5.Text+"'", con);
con.Open();
ddd.UpdateCommand.ExecuteNonQuery();
con.Close();
MessageBox.Show(" UserID and Password is Updated!!! ");
}
else
{
MessageBox.Show("Invalid Login please check username and password");
}
}
}
}
44
Supplier code
using System;
using System.Data;
using System.Linq;
using System.Text;
using System.Text.RegularExpressions;
{
public partial class SupplierInfo : Form

{
Security=True");
public SupplierInfo()
{
bind();
}
public void bind()
{
String connectionString = "Data Source=DESKTOP-
2O8FVUK\\SQLEXPRESS;Initial Catalog=TextileManage;Integrated Security=True;";
using (SqlConnection sqlCon = new SqlConnection(connectionString))

{
45
sqlCon.Open();
SqlDataAdapter sqlDa = new SqlDataAdapter("SELECT Sup_Id AS
SupplierID,SName AS SupplierName,SAddress Address,SEmail AS EmailID,SMob AS
MobileNumber1,SMob2 AS MobileNumber2,GST AS GSTNO FROM supplier_data",
sqlCon);
DataTable dtbl = new DataTable();
sqlDa.Fill(dtbl);
dataGridView1.DataSource = dtbl;
}
}
private void groupBox1_Enter(object sender, EventArgs e)

{
private void SupplierInfo_Load(object sender, EventArgs e)

{

{
textBox4.Text.Equals("") || textBox5.Text.Equals("") || textBox6.Text.Equals(""))
{
MessageBox.Show("Please enter all fields correctly", "Warning");
}
46
else
{
con.Open();
SqlCommand cmd = con.CreateCommand();
cmd.CommandType = CommandType.Text;
cmd.CommandText = "insert into supplier_data values ('" + textBox1.Text + "','" +
textBox2.Text + "','" + textBox3.Text + "'," + Convert.ToInt64(textBox4.Text) + "," +
Convert.ToInt64(textBox5.Text) + "," + Convert.ToInt64(textBox6.Text) + ")";
cmd.ExecuteNonQuery();
con.Close();
this.Hide();
si.ShowDialog();
}
}
private void dataGridView1_CellClick(object sender, DataGridViewCellEventArgs e)

{
int ind = e.RowIndex;
DataGridViewRow selectedRows = dataGridView1.Rows[ind];
label5.Text = selectedRows.Cells[0].Value.ToString();
textBox1.Text = selectedRows.Cells[1].Value.ToString();
textBox2.Text= selectedRows.Cells[2].Value.ToString();
}

{
47

{
}
else
{
String sid = label5.Text;

long ssi = Convert.ToInt64(sid);
ddd.UpdateCommand = new SqlCommand("UPDATE supplier_data SET
SName='" + textBox1.Text + "',SAddress='" + textBox2.Text + "',SEmail='" + textBox3.Text
+ "',SMob=" +Convert.ToInt64( textBox4.Text) + ",SMob2=" +
Convert.ToInt64(textBox5.Text) + ",GST=" + Convert.ToInt64(textBox6.Text) + " where
Sup_Id=" + ssi, con);
con.Open();
con.Close();
this.Hide();
si.ShowDialog();
}
}

{

{
48

}
else
{
String sid = label5.Text;

long ssi = Convert.ToInt64(sid);
ddd.DeleteCommand = new SqlCommand("DELETE FROM supplier_data where
Sup_Id=" + ssi, con);
con.Open();
ddd.DeleteCommand.ExecuteNonQuery();
con.Close();
this.Hide();
si.ShowDialog();
}
}

{
si.ShowDialog();
this.Hide();
}

{
string patt = @"^[a-zA-Z\s]+$";
bool isEmailValid = Regex.IsMatch(textBox1.Text, patt);
49
if (!isEmailValid)
{
label10.Text = "Alphabets";
}
else
{
label10.Text = "";
}
}

{

{
string patt = @"^\w+@[a-zA-Z_]+?\.[a-zA-Z]{2,3}$";
if (!isEmailValid)
{
label12.Text = "email";
}
else
{
label12.Text = "";
}
}
50
{
string patt = @"^[0-9]{10}$";
if (!isEmailValid)
{
label13.Text = "10 digit mobile number";
}
else
{
label13.Text = "";
}
}

{
string patt = @"^[0-9]{10}$";

if (!isEmailValid)
{
}
else
{
label14.Text = "";
}
}

{
51
string patt = @"^[0-9]{12}$";

if (!isEmailValid)
{
label15.Text = "12 digit GST number";
}
else
{
label15.Text = "";
}
}
e)
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
Home si = new Home();
si.ShowDialog();
}
{
this.Hide();
si.ShowDialog();
52

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
System.Windows.Forms.Application.Exit();
}

e)
{
this.Hide();
si.ShowDialog();
}

{
53
this.Hide();
si.ShowDialog();
}
private void billsToolStripMenuItem_Click(object sender, EventArgs e)

{

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}
54

e)
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}
}
}
55
Material code
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class Material : Form

{
Security=True");
public Material()
{
bind();
}
public void bind()
{
comboBox1.Items.Clear();
con.Open();
cmd1.CommandText = "select DISTINCT(MName) AS TOT from material_data";
while (rd.Read())
{
comboBox1.Items.Add(rd["TOT"].ToString());
}
con.Close();
}
{
private void comboBox2_SelectedIndexChanged(object sender, EventArgs e)

{
String sid = comboBox2.Text;
long ssid = Convert.ToInt64(sid);
56
con.Open();
cmd1.CommandText = "select Prize AS TOT,SalePrize AS TOT1 from material_data
where MId=" + ssid;
while (rd.Read())
{
label4.Text = rd["TOT"].ToString()+"/-";
label7.Text = rd["TOT1"].ToString()+"/-";
}
con.Close();
}

{

{

{
string patt = @"^0*[1-9]\d*$";
if (!isEmailValid)
{
label10.Text = "number format(not zero)";
}
else
{
label10.Text = "";
}
}

{
private void comboBox1_SelectedIndexChanged(object sender, EventArgs e)

{
comboBox2.Items.Clear();
String sid = comboBox1.Text;
con.Open();
57
cmd1.CommandText = "select Mid AS TOT from material_data where MName='"

+comboBox1.Text+"'";
while (rd.Read())
{
comboBox2.Items.Add(rd["TOT"].ToString());
}
con.Close();
}

{
if (comboBox1.Text.Equals("") || comboBox2.Text.Equals("") || label4.Text.Equals("-
") || textBox1.Text.Equals("0") || textBox1.Text.Equals(""))
{
}
else
{
String cid =comboBox2.Text;
long cci = Convert.ToInt64(cid);

ddd.UpdateCommand = new SqlCommand("UPDATE material_data SET
SalePrize=" +Convert.ToInt64( textBox1.Text) + " where MId=" + cci+" AND
MName='"+comboBox1.Text+"'", con);
con.Open();
con.Close();
this.Hide();
si.ShowDialog();
}
}

{

{
this.Hide();
si.ShowDialog();
}
58

e)
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();

{
this.Hide();
si.ShowDialog();
}

e)
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
59

{
this.Hide();
si.ShowDialog();
}

{

{
this.Hide();
si.ShowDialog();
}

e)
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}
}
}
60
Customer Code
using System;
using System.Data;
using System.Linq;
using System.Text;
{
public partial class CustomerInfo : Form
{
Security=True");
public CustomerInfo()
{
bind();
}
public void bind()
{
String connectionString = "Data Source=DESKTOP-
2O8FVUK\\SQLEXPRESS;Initial Catalog=TextileManage;Integrated Security=True;";
using (SqlConnection sqlCon = new SqlConnection(connectionString))
{
sqlCon.Open();
SqlDataAdapter sqlDa = new SqlDataAdapter("SELECT CId AS
CustomerID,CName AS CustomerName,CAddress AS Address,CEmail AS EmailID,CMob
AS MobileNumber FROM customer_data", sqlCon);
DataTable dtbl = new DataTable();
sqlDa.Fill(dtbl);
dataGridView1.DataSource = dtbl;
}
}

e)
{
this.Hide();
si.ShowDialog();
}
61

{
this.Hide();
si.ShowDialog();
}

{
textBox4.Text.Equals(""))
{
}
else
{
con.Open();
SqlCommand cmd = con.CreateCommand();
cmd.CommandType = CommandType.Text;
cmd.CommandText = "insert into customer_data values ('" + textBox1.Text + "','"
+ textBox2.Text + "','" + textBox3.Text + "'," + Convert.ToInt64(textBox4.Text) + ")";
cmd.ExecuteNonQuery();
con.Close();
this.Hide();
si.ShowDialog();
}
}

{
{
}
else
{
String cid = label5.Text;

ddd.UpdateCommand = new SqlCommand("UPDATE customer_data SET
CName='" + textBox1.Text + "',CAddress='" + textBox2.Text + "',CEmail='" +
textBox3.Text + "',CMob=" + textBox4.Text + " where CId=" + cci, con);
62
con.Open();
con.Close();
this.Hide();
si.ShowDialog();
}
}

{
{
}
else
{
String cid = label5.Text;

ddd.DeleteCommand = new SqlCommand("DELETE FROM customer_data where
CId=" + cci, con);
con.Open();
ddd.DeleteCommand.ExecuteNonQuery();
con.Close();
this.Hide();
si.ShowDialog();
}
}

{
this.Hide();
si.ShowDialog();
private void textBox1_TextChanged_1(object sender, EventArgs e)
63
{
string patt = @"^[a-zA-Z\s]+$";
if (!isEmailValid)
{
label10.Text = "Alphabets";
}
else
{
label10.Text = "";
}
}
private void textBox2_TextChanged_1(object sender, EventArgs e)

{

{
string patt = @"^\w+@[a-zA-Z_]+?\.[a-zA-Z]{2,3}$";
if (!isEmailValid)
{
label12.Text = "email";
}
else
{
label12.Text = "";
}
}

{
string patt = @"^[0-9]{10}$";
if (!isEmailValid)
{
}
else
{
label13.Text = "";
}
}
private void dataGridView1_CellClick(object sender, DataGridViewCellEventArgs e)

{
int ind = e.RowIndex;
DataGridViewRow selectedRows = dataGridView1.Rows[ind];
64
label5.Text = selectedRows.Cells[0].Value.ToString();
private void homeToolStripMenuItem_Click_1(object sender, EventArgs e)

{
this.Hide();
si.ShowDialog();
}
private void updateDeleteSupplierToolStripMenuItem_Click_1(object sender,

EventArgs e)
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
}
65

e)
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}
private void billsToolStripMenuItem_Click(object sender, EventArgs e)

{

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}

e)
{
this.Hide();
si.ShowDialog();
}
66
{
this.Hide();
si.ShowDialog();
}

{
this.Hide();
si.ShowDialog();
}
}
}
67
5.2 TESTING APPROACH:

Software testing is a critical element of software quality
assurance and represents the ultimate review of specification, design, coding.
Testing objective:
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 function appears to be
working according to the specification and performance requirement have
been met.
But Testing cannot show the absence of defects it can show only that software
errors are present.
5.2.1 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 function properly as a unit.
5.2.2 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.
68
Chapter -6
Results and Discussions
Home Form
69
Login Form
 Enter user ID and password to login.
70
Reset Password Form
 Reset clears the fields so that the user can enter the username and password
login.
 If the entered username or password is wrong the message box would be
prompted displaying “invalid login”.
 Enter the new login.
71
Suppliers Form
 This form allows user to view Supplier details.

 New Button: It allows user to enter new supplier record.
 Add Button: It allows user to add the record to database.
 Update Button: It allows user to update the record from data grid view.
 Delete Button: Delete the form.
72
Material Form
 This form allows user to update material supplied by the supplier.
 Update Button: It allows user to update the record to database.
73
Customer Form
 This form allows user to view customer details.
 New Button: It allows user to enter new customer record.
 Add Button: It allows user to add the record to database.
 Delete Button: Delete the form.
74
Supplier order Form
 This form allows user to enter Supplier Order details.

 New 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.
75
Customer order Form
 This form allows user to clear all the fields of the form.
 Add Button: it allows user to save the record to database.
 New 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.
 Delete Button: exits the form.
76
Customer Bill Form
 This form allows user to enter customer bill details.

 Create Bill: it allows the customer and supplier order details
 .print Bill: print the form.
77
Supplier Bill Form
 This form allows user to enter Supplier Bill details.

 Create Bill: it allows the supplier order details
 .print Bill: print the form.
 delete Button: delete the bill.
78
Stock availability Form
 This form allows user to view the stock details. The user has to select material name
from the combo box.
79
Supplier report Form
 Print button: print the form.
80
Customer report Form
81
Stock Report Form
82
Purchase Report Form
Chapter-7
83
Conclusion And Future Work
Bangladesh is a developing country. Many developing countries are

now using information countries are now using information communication for different
sector. if we want to change our position in the world we must have to develop our
information technology. Through the developed project anyone can visualize the
effectiveness and efficiency in the field. It is very helpful for computerization or doing
automation of these types of management system. This automated system gives very helpful
services for textile factories in our country. In this project, I have developed an automated
textile work order management system. Using this system, Admin can go through the entire
system and also generating various types of report. On the other hand, admin can modify, add
and delete the work order & shipment schedule to and from the system the system. Also can
see the deliverables are on order or not. These systems will be one of the steps forward to
improve the textile sector of Bangladesh.
Future work:
The future plan of this project is to improved design, implementation and
documentation in such a way that beside work order, any other work process monitoring
services can easily customize and use this project.
I will develop the site more dynamically. In future I will add some modules for better
improvement of the project. Such as; the system wills automatically giving the
recommendation for an event based on some logical criteria for a particular project. Also it
will give some recommendation for merging or efficient resource planning. And finally a
more secured and user friendly version, for the front end users. I will implement this system
in textile industry.
Chapter -8
84
REFERENCE
Content
[1] Reference Book:
Visual C# programming basics.
[2] Website:
www.scribd.com
For SQL
www.scribd.com
[3] FOR .NET INSTALLATION
85

Project Doocuments (Repaired)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Project Doocuments (Repaired)

Hochgeladen von

Copyright:

Verfügbare Formate

TEXTILE MANAGEMENT SYSTEM

TEXTILE MANAGEMENT SYSTEM

BACHELOR OF SCIENCE (INFORMATION TECHNOLOGY),

JYOTI GHANSHYAM GUPTA

Under the esteemed guidance of

DEPARTMENT OF INFORMATION TECHNOLOGY

K.B GIRLS WOMAN COMMARECE AND ART COLLEGE

KB GIRLS WOMAN COMMERCE AND ARTS COLLEGE

(Affiliated to University of Mumbai)

THANE – MAHARASHTRA - 400600

DEPARTEMENT OF INFORMATION TECHNOLOGY

This is to certify that the project entitled,” TEXTILE MANAGEMENT SYSTEM “, is

Internal guide Coordinator

Date: College Seal

Note: Entire document should be with

I hereby declare that the project entitled, “TEXTILE MANAGEMNET

 Keeping record of raw material purchased.

1.2 SCOPE OF THE PROJECT:

 The purpose of the project is of the project is to develop a ‘Textile management

1. Implementing the functionality on the login page to validate department

2. Documentation of software system.

4. Completed life cycle of project development from requirement to testing phase.

 No Security has been provided to the data.

2.2 PROPOSED SYSTEM

2.3 HARDWARE REQUIREMENTS

system for a professional

15” screen 1.0 GB of disk space

 Intel 80486*4 or better

And the components that are not variable are:

 Keyboard (84 keys or more)

2.4 SOFTWARE REQUIREMENTS

Front End : C#.NET

Back End : MS SQL server 2012

EXPLANATION OF THE TECHNOLOGY

MICROSOFT VISUAL STUDIO 2017:

Microsoft visual studio is an integrated development environment

2.5 JUSTIFY OF PLATFORM

REQUIREMENT AND ANALYSIS

 Inquire of available product-

 3.2 Planning and scheduling

TASKS DESCRIPTION RESPONSIBILITY

July August September

Planning Execution Break

October November December

Planning Execution Break

January February March

Design Code Testing

3.3 model Conceptual

 Data flow diagram

Bill_no Customer_bill Bill_dat

Login _details mainta Textile generat

OBJECT ORIENTED DIAGRAM

 4.1 BASIC MODULE

 Customer Details Form:

 Customer order form:

 Calculate Button: it allows user to calculate total expenses based on quantity

 Update Customer Order Form:

 Customer Bill form:

 Supplier Details Form:

 Supplier Order Form:

 Update Supplier Order Form:

 Supplier Material Form:

 Supplier Bill Form: