Textile Management Systen
Textile Management Systen
Textile Management Systen
Submitted By
PRASHANT BHARATI
&
ABHISHEK MEDEKAR
Semester 6 Examination
ELPHINSTONE COLLEGE
acknowledgement
COURSE COORDINATOR :
MRS.DR.JAYSHREE DESAI
FACULTY :
MRS. S. AGARWAL
MR. VINAY DUBEY
INDEX
TITLE NO TITLE NAME
PAGE NO
1. Introduction
2. Synopsis
4. Definition of project
5. Software/Technologies used
8. Spiral Model
9. System Requirements
15. Testing
18. Snapshots
20. Bibliography
21. Conclusion
INTRODUCTION
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.
PROJECT DEFINITION:
Management of activities in a Textile Industry.
To replace their existing system
Connecting all the departments through a single system
PURPOSE
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.
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
Description: This table stores the details about the users of the
system.
Table Name:supplier_details
OBJECTIVE AND
SCOPE OF THE
PROJECT
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.
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:-
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
FRONT END:
MICROSOFT VISUAL STUDIO 2008:
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++.
BACK END:
Databases structure:-
Before storing the information, you need design a database
structure. Each database has following elements.
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:
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.
SPIRAL MODEL
SPIRAL MODEL
a) Communication
b) Planning
c) Modelling
d) Construction
e) Deployment.
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.
Spiral Approach
System requirements
SYSTEM REQUIREMENTS
HARDWARE REQUIREMENT:
Intel Pentium P4
256 MB of memory
15 screen
16 MB or more of memory
15 screen
System planning
System Planning:
The project team consists of following two members:
1) Abhishek Medekar
2) Prashant Bharati
PROPOSED SYSTEM
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
Analysis
Finish
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 objectives
error.
2. A good test case is the one that has high portability of finding an as-yet
undiscovered error.
The main objective here will be to design test cases to uncover different
But Testing cannot show the absence of defects it can show only that
the each unit of the software as implemented in the source code. Unit
unit.
customer.
whole. These tests fall outside the scope of software engineering process
VALIDATION TESTING:
In our system we are going to use the Black box testing in the
following criteria:
SECURITY TESTING
Corrective faults.
Improved performance.
Adapt the product to a changed environment and
implementing changes.
Evaluation by the external guide.
REPORT LIST
REPORT LIST
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
B.Sc (IT) ELPHINSTONE COLLEGE Page 66
es
supplier
bill
TEXTILE MANAGEMENT SYSTEM
3.1
supplier_detai
Enter ls
Admin stock
details Stock
Login:-
MDI Form:-
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.
Exit Button: Exits the form.
Multiuser Validation:-
Reports:-
Customer Report:-
Supplier Report:-
Sales Report:-
CURRENT SYSTEM