Sie sind auf Seite 1von 27



SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR 2 months industrial training At LCET, Katani-Kalan (From Jun 2011 to July 2011)


Roll No. : 4408

Univ. Roll no. : 90490306227




SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENT FOR 2 months industrial training At LCET, Katani-Kalan (From Jun 2011 to July 2011) SUBMITTED BY Varun Jain

Roll No. : 4408

Univ. Roll no. : 90490306227




I hereby certify that Varun Jain Roll No 90490306227 of Ludhiana College of Engineering & Technology Katani-Kalan, has undergone two months Industrial Training from Jun 2011 to July 2011 to fulfill the requirements for the award of degree of B.Tech. CSE. He/ She works on Workflow Management project under the supervision of Mr.Yashpal Singla & Mr.Akhilesk Aggarwal. During his tenure with us we found him sincere and hard working. Wishing him a great success in the future.

Varun Jain Signature of the Student

Signature of the SUPERVISORS


The authors are highly grateful to the Dr. J.S.Sohal, Director, Ludhiana College of engineering & Technology Katani-kalan, for providing this opportunity to carry out the Major project at this college.

The constant guidance and encouragement received from Dr. Pawan Kumar, Principal, has been of great help in carrying out the project work and is acknowledged with reverential thanks.

The authors would like to express a deep sense of gratitude and thanks profusely to Er. Ramandeep Singh, Head CSE, without the wise counsel and able guidance, it would have been impossible to complete the report in this manner.

The help rendered by Mr. Yashpal Singla & Mr. Akhilesh Aggarwal, for experimentation is greatly acknowledged.

The author expresses gratitude to other faculty members of Computer science and Engineering Department of LCET Katani-kalan for their intellectual support throughout the course of this work.

Finally, the authors are indebted to all whosoever have contributed in this report work and friendly stay at IOTA SOL, Ludhiana.

Varun Jain

Table of Contents
1. Introduction6 1.1 Various Phases Of Project.8 1.2 Disadvantages Of old System11 1.3 Advantages of New Computerized System..12 2. Hardware and Software Requirements.13 3. Project Review.14 3.1 Software Analysis Data Flow Diagrams......15 3.2 Database Structure...16 4. Planning Of Work19 4.1 Snapshots of the Project...20 5. Results and Discussions25 6. Conclusion and Future Scope..26 7. Bibliography..27

Workflow: The automation of a business process, in whole or part, during which documents, information or tasks are passed from one participant* to another for action, according to a set of procedural rules. *participant = resource (human or machine workflow management consortium The system is used to coordinate the work of multiple people in a project that has a fixed process.

Why workflow management?

Better, Cheaper faster businesses Improved efficiency - mostly through automation of business processes. Improved customer service through consistency in the processes. Improved process control - helps management and improves overall quality of the outcomes. Flexibility software control over processes enables their re-design in line with changing business needs Business process improvement - through focus on business processes.

Since, todays dynamic global business environment is driving a new extended enterprise, competitive companies are focusing their management on processes as the key to their success. To this end workflow management technologies have been developed, involving process modeling, process reengineering and workflow implementation and automation. On the 6

other hand effective project management is one of the most important success factors for organizations. Since information flow between the participants in a project becomes more and more important in project's implementation, the possible use of workflow management tools in modeling and reengineering of project This project entitled as WORKFLOW MANAGEMENT is used basically for manage the data of a hosiery including employee detail , type of employees number of employees ,about their salary and also records the lots and work done or in process . Now a day we can easily see that our life is so much busy. In the modern life in a hosiery, factory or in a management there is no time for entering data manually because of the changing life style and fast approach to each work. In UK and other developed country mostly all the people do work online and uses computer for time savage to fill entries and to maintain records. Because its time saving and you can easily find the records in a short span of time. Thats the reason the mostly all the famous companies has their online web sites and there you can fill the whole status or can have a record to anything which you want. In the workflow management, the same case is handled to save time in mills or big firms where the records of employee, lot, its various fields and phases where the task is done in various states and their salary and compensation is to be maintained. So the workflow management helps to manage these records and saves it in a database and saves time without doing it manually as avoiding the old techniques to maintain records using various bills and blitzes and all that is to be kept safe from the unauthorized user.


1. Login 2. Home 3. Manage Master Data 4. Manage Workflow 5. Salary 6. Manage Employee 7. About Us 8. Logout

1. Login module In the admin module the website administrator has all rights to manage the website. He can see who are the members and their orders and add main category of products and add new products. Add sub category and many more this module is authenticated by login authentication. Only admin can access it.

2. Home After the user login the page which opens is the home page which welcomes the description about Workflow Management.

3. Manage Master Data In this phase fills the all basis table information about the workflow status. This phase consists of following parts Manage employee type: in this page we can enter any number of employee types like sewing, cutter, washing, etc. And can also update the existing types. Manage raw material: this page enters the information about raw material or fabric type and we can insert any type, delete or update existing type of raw material. Manage color: this page is related to lot or the fabric color. We can add any number of colors and update or delete existing color record.

Manage product: this page brings all the type of fabric made from the raw material like an example is a t-shirt, shirt or sweater, etc. Also we can apply the changes on product type and can insert new types.

Manage rate unit: in this page we decide all the rate units and can insert new units & update or delete the existing ones. Manage product compensation rate: in this page we select employee type, product and rate unit and corresponding to these fields we can define the price for that type. Also we can update or delete the existing record.

4. Manage Workflow and Lot In this phase manages the lot and the whole workflow corresponding to that lot and maintains the task to be done for the lot. This phase consists of following three parts Manage lot : this page makes the new lot when its is to be cut by cutter and entry is done in the data base for maintain the lot with its color ,raw material type , product made and piece cut followed by employee name and its employee type. Manage workflow: this page done all the work operations like embroidery, washing, pressing, sewing, etc and assign the pieces to employees of the corresponding types when a lot is selected .we can also made changes like update or delete to the corresponding workflow. View lot status: this page brings whole of the lot record its all workflow which is managed on when and completion date. This prints all the work done for the corresponding lot selected.


Manage salary

In this phase is the one of the important of all phases. This page brings the salary status of employees for their task done when selected against their employee type. This page also consists of three parts. Generate salary :on this page when we select a employee from its corresponding employee type shows its all previous balance and new salary record against its new task done till up to its last paid date. And at last we can pay salary to

employee from the data shown on the page and after that the balance outstanding is set.

View salary: this page results all the salary information like compensation amount, balance outstanding and previous balance from the date one to last that employee has taken for his all task done.

View salary against task: this page shows all the work and salary records of an employee against the tasks that he done till from the first date to last.

6. Manage Employee In this section, user can add any number of employees and can either update or delete employees data. This page contains all the basic information about the employee like his name, age, contact number, address, its type, date of joining and username.

7. About Us In this section, user can see the information about this project like company name, developer name, and all info about us. This page also contains a reset button for database clearance. All the fields of database were clear if u reset it.

8. Logout In this section after the work done or complete for security logout session cleared and also clears browser history to disable back button on use again u have u login again with correct user name and password.



As we know the manual processing is quite tedious, time Consuming, less accurate in comparison to computerized processing. Obviously the Present system is not good & is exception consultant encountering all the above problems. Time consuming. It is very tedious. All information is not placed separately. Lot of paper work. Slow data processing. Not user-friendly environment. It is difficult to find records due file Management system.



In new computerized system i tried to give these facilities. Manually system changes into computerized System. Friendly user interface. Time saving. Save paper work. Connecting to database so we use different type of queries, data report. Give facility of different type of inquiry. Formatted data. Datas are easily approachable.



Hardware requirement: Processor: - Pentium 4 1 GHz or above Ram: - 256mb. Hard disk: -80 GB or above. Monitor: - 14 VGA Mouse, keyboard

Software requirement: Operating system : windows NT/2003, Windows Xp, Window Vista ,Windows 7 Ide Frontend Back end Server Development kit Browsers : Eclipse for java and Mysql query browser : jsp/html : My-sql : apache tomcat 6.0.32 : jdk-6

: Internet Explorer, Mozilla Firefox, Google Chrome


3. Project Review
Objectives To increase reliability for the company. To provide the good experience for managing. And learn how the products will work in live. And increase our programming skills. To enhance easy task handling in a company. To do work manually and adding entries manually On computer and avoiding written work.

Project Category: -

Web Application

This website will show customer the better experience of adding entries and will generates bill and payments are go through PayPal and many more. It will target the fast market and provide you the best quality goods and with new style.

Employee Bills & Salary Employee type Lot Status Management Modules Payment and Receipt



Login Username and password

Welcome to workflow management

Manage Master Data

Manage Employeetype

Manage Color

Manage Rawmaterial

Manage Rate

Manage Product

ManageProduct ratecompensation

Manage Workflow & Lot

Manage Lot Create and update Lot

Manage Workflow
Edit & do workflow Operations on diff. employee type

View Lot Status Shows all the Lot information

Manage Salary

Generate Salary
Show the total salary against work done and previous balance

View Salary
Shows the balance all compensation and balance Outstanding

View SalaryAgainst Task

Shows Salary

against each task

Manage Workflow & Lot


Manage Employee
Add new employee, Update and delete existing employee record 15


1. tb_emploeetype Field id employeetype Key Primary key Type Int Varchar(45)

2. tb_rateunit Field id title Key Primary key Type Int Varchar(45)

3. tb_rawmaterial Field id rawMaterial Key Primary key Type Int Varchar(45)

4. tb_color Field id color Key Primary key Type Int Varchar(45)

5. tb_user Field id userId password Key Primary key Type Int Varchar(45) Varchar(45)

6. tb_product Field id product Key Primary key 16 Type Int Varchar(45)

7. tb_employee Field Id Name employeetypeId dateOfJoining username Age contactNo Key Primary key Foreignkey Type Int Varchar(45) Int Varchar(45) Varchar(45) Int Varchar(45)

8. tb_productcompensation Field Id Rate productId rateunitId employeetypeId Key Primary key Foreignkey Foreignkey Foreignkey Type Int Int Int Int Int

9. tb_workflow Field Id employeeId employeetypeId lotId createdOn Key Primary key Foreignkey Foreignkey Foreignkey Type Int Int Int Int Date

10. tb_lot Field Id employeeId rawmaterialId productId Color quantityAssigned Piececut lotName Key Primary key Foreignkey Foreignkey Foreignkey Type Int Int Int Int Int Int Int Varchar(45)


11. tb_workflowemployee Field id employeeId workflowId salaryId taskAssignedOn taskCompletedOn pieceAssigned compensation compensationDate Key Primary key Foreignkey Foreignkey Foreignkey Type Int Int Int Int Date Date Int Int Date

12. tb_salary Field id employeeId compensationDate previousBalance compensationAmount balanceOutstanding Key Primary key Foreignkey Type Int Int Date Int Int Int


Planning-how an idea come to mind Analysis Design-Implementation Maintenance Development Testing

Planning The idea came to mind as there is a need to handle all the written work like billing or lot of handling is done manually. So to enter these entries manually, there is a need of any Workflow Management that do this work easy. Analysis For this some task has to be done like # Market Research # Software Analysis # Software Design # Coding Design Implementation The task of module is Design Workshop and Implementation Phase is not only in bugs but in software implementation. In Design Workshop, developers have to start from the bottom to impress the users. In the latter phase, we will only have to work in software updates to ensure wider user acceptance. Maintenance When the software is implemented, it does not mean that the software is good as it is. All SDLC models include maintenance since there are absolutely no way that software will be working perfectly. Someone has to stay in the present software to take a look and ensure the program works perfectly. Testing The first type of testing is the actual testing by users. This is usually done in models wherein implementation does not go with pre-testing with users. On the other hand, there are also testing that uses professionals in the field. This testing is aimed in cleaning the software of all the bugs altogether. For software that are set for public release, the software is first tested by other developers who were not in charge in creating the software.




The correct username and password login the account.


After successful login the Home page will be shown as above



This page adds new employee type, update and delete the existing employee type. 4. COLOR

This page adds new color, update and delete the existing color. 21


This page adds new raw material, update and delete the existing raw material.


This page adds new rate, update and delete the existing rate record. 22


This page creates new Lot, update and delete the existing Lot.


This page manages all the workflow levels.



This page entitles salary against each employee and we can also pay salary here.



This page entitles salary against each task that the employee has done.



The analysis so far has shown that the two approaches usually applied in workflow modeling, i.e. the activity and the communication-based, can provide adequate vehicles for process modeling when applied to project management - when the aim is an effort to reengineer and/or streamline these processes aiming to operational improvement. None of the two approaches falls behind the other concerning the scope and wealth of information provided. Specifically, they both provide: ample information concerning the tasks to be modeled (either separating them into phases, Or tasks and activities), hence they both support the allocation of a project's phases into work packages, tasks and activities; rich information for the time duration of processes and the cost incurred for the execution of the processes. constructs for modeling issues such as parallelism and if-then-else mechanisms.



However, the two approaches present a number of differences concerning the "philosophy" of modeling which would be taken explicitly into account when applied to project management. Such differences are strongly related to the limitations that, in general, the workflow systems have. We list below the basic ones, observed throughout the modeling procedure: the simplicity/complexity in applying the approaches to project management processes, especially with regard to the flow of communication and the interdependence of tasks. Both methods are highly dependent on the type of the project. The key issue, though, is that the activity-based approach enables us to observe possible interdependencies of tasks but does not provide much information about the flow of communication among processing entities [ ]. On the contrary, that is being brought to an end successfully by the communication-based approach, which, in turn, due to its structure, can not represent big number of interdependent tasks. the ease of applying the approaches to the administrative issues of project management processes. The tasks modeled should be repetitive concerning operations involved in the project. It is very hard, for different reasons in each approach, to model exceptional tasks or processes. the ability and ease of each approach for handling client-orientation. The activity-based approach is more convenient for internal tasks of the project management team, while the communication-based is strongly focusing on the relationship with the customer, reminding at each single step who is the client and what is he expecting from the task! the managerial implications concerning the expertise required by the modeling team by each approach. In Jet Form the modeling procedure seems to be less structured requiring professional expertise by the project management team in process modeling. On the other hand Action Workflow is more structured guiding the model designer throughout the whole procedure. However, the latter can be also a disadvantage, because it restricts the degrees of freedom that the design team has.



Sierra Kathy ,OReally Headfirst Java A Learners Guide Ebook (headfirst java) by Kathy sierra & Bert bates,2nd edition