College Automation Project

WORKFLOW AUTOMATION SYSTEM 17CP308
WORKFLOW AUTOMATION SYSTEM
A PROJECT REPORT
Submitted by
HINGU DHAVAL KISHANBHAI

ID No. 17CP308
In
Partial fulfilment for the award of the degree of
B. TECH. (COMPUTER ENGINEERING)
Under the course of
CP446: FULL SEMESTER EXTERNAL PROJECT)
BIRLA VISHVAKARMA MAHAVIDYALAYA

(ENGINEERING COLLEGE)
(An Autonomous Institution)
VALLABH VIDYANAGAR
GUJARAT TECHNOLOGICAL UNIVERSITY,

AHMEDABAD
Academic Year: 2019 – 2020
B. V. M. ENGINEERING COLLEGE,
VALLABH VIDYANAGAR-388120
i
APPROVAL SHEET
The project work entitled “WORKFLOW AUTOMATION SYSTEM"

carried out by “HINGU DHAVAL KISHANBHAI with ID No
(17CP308)” (which was carried out at Kothari InfoTech Pvt. Ltd.) is
approved for the submission in the course CP446, Full Semester
External Project for the partial fulfillment for the award of the degree
of B. Tech. (Computer Engineering).
(Name & Designation)
Date:
Place:
ii
CERTIFICATE
This is to certify that Project Work embodied in this project report titled
“WORKFLOW AUTOMATION SYSTEM" was carried out by “HINGU
DHAVAL KISHANBHAI with ID No (17CP308)” (which was carried out
at Kothari InfoTech Pvt. Ltd.) under the course CP446, Full Semester
External Project for the partial fulfillment for the award of the degree of B.
Tech. (Computer Engineering). Followings are the supervisors at the
institute.
Date:
Place:
Prof. Bhavesh Tanawala
Professor of Computer Engineering
Prof. Mahasweta Joshi
Professor of Computer Engineering
(Dr. Darshak G Thakore)

Prof. & Head
Computer Engineering Department, BVM
iii
DECLARATION OF ORIGINALITY
I hereby certify that we are the sole authors of this report under the course CP446 Full
Semester External Project and that neither any part of this report nor the whole of the report
has been submitted for a degree to any other University or Institution.
I certify that, to the best of our knowledge, the current report does not infringe upon
anyone’s copyright nor violate any proprietary rights and that any ideas, techniques,
quotations or any other material from the work of other people included in our report,
published or otherwise, are fully acknowledged in accordance with the standard referencing
practices. Furthermore, to the extent that we have included copyrighted material that
surpasses the boundary of fair dealing within the meaning of the Indian Copyright
(Amendment) Act 2012, we certify that we have obtained a written permission from the
copyright owner(s) to include such material(s) in the current report and have included
copies of such copyright clearances to our appendix.
I declare that this is a true copy of report, including any final revisions, as approved by
report review committee.
I have checked write up of the present report using anti-plagiarism database and it is in
allowable limit. Even though later on in case of any complaint pertaining of plagiarism, we
are sole responsible for the same and we understand that as per UGC norms, University can
even revoke the degree conferred to the student submitting this report.
Date:
Institute code: 007
Hingu Dhaval Kishanbhai (17CP308)
iv
v
Contents
AB STRACT ......................................................................................................viii
ACKNO WLED GEM ENT ................................................................................ix
List of Figures ........................................................................................................x
List of Tables ........................................................................................................xi
ABBREVIATIONS................................................................................................1
CHAPTER 1 INRODUCTION ............................................................................2
1.1 Project Overview………………………………………………………………………………………….2
1.2 Objective…………………………………………………………………………………………………..2
1.3 Scope……………………………………………………………………………………………………….3
1.4 Tools and Technology Used………………………………………………………………………….3
CHAPTER 2 PROJECT MANAGEMENT………………………………………5
2.1 Project Planning…………………………………………………………………………………………...5
2.1.1 Project Development Approach and Justification………………………………………………5
2.2 Project Work Scheduling………………………………………………………………………………6
2.2.1 Gantt Chart Representation………………………………………………………………………..6
CHAPTER 3 SYSTEM REQUIREMENTS STUDY & ANALYSIS...................8
3.1 User characteristics……………………………………………………………………………………..8
3.1.1 Use Case Diagram…………………………………………………………………..8
3.2 Hardware and Software Requirements…………………………………………………………….9
3.3 Assumption and Constraints…………………………………………………………..10
3.4 Study of Existing System…………………………………………………………………………….10
3.5 Limitation of Existing System………………………………………………………………………..10
3.6 Requirements of Proposed System…………………………………………………………………..11
3.6.1 Functional Requirements…………………………………………………………...11
3.6.2 Non-Functional Requirements……………………………………………………...13
3.7 System Workflow……………………………………………………………………………………….14
3.8 Class Diagram…………………………………………………………………………………………….15
3.9 Activity Diagram………………………………………………………………………………………….16
3.10 Sequence Diagram……………………………………………………………………………………..17
vi
3.11 State Chart Diagram........................................................................................... 18

CHAPTER 4 SYSTEM DESIGN………………………………………......................19
4.1 Database Schema Design ..................................................................................... 19
4.2 Screen Layouts (FORMS AND REPORT) ............................................................... 19
4.3 Method Pseudo Code .......................................................................................... 26
4.3.1 Xml Generator Pseudo Code ............................................................................ 26
4.4 Coding Standards ................................................................................................ 27
4.5 Testing Method .................................................................................................. 28
4.6 Test Cases ......................................................................................................... 29
CHAPTER 5 FUTURE ENHANCEMENT & CONCLUSION……………............31
5.1 Future Enhancement ............................................................................................. 31
5.2 Conclusion .......................................................................................................... 32
5.2.1 Self-analysis of Project Viabilities..................................................................... 32
5.2.2 Problem Encountered and problems solution ........................................................ 32
5.2.3 Summary of Project Work ............................................................................... 33
References……………………………………………………………………………….35
vii
ABSTRACT
Workflow Automation System – Patterns for Automated Manufacturing is a

software developed to automate the production workflow for business of all sizes.
It automates and simplifies the overall process from order to shipment. This
system is flexible enough to adapt to all kind of structured environments and is
implemented and deployed in-house without considering external factors.
Purchase orders from data sources, movement of the job in the system, availabil it y
of necessary details at right stage at right time, is all automated.
Continuous evaluation of the workflow also help to recognize patterns and derive
knowledge with which quality decisions can be made.
viii
ACKNOW LEDGEMENT
Here we gladly present this project report on “ Workfow Auotmation System ” as part of the
8th semester B.Tech in Computer Science and Engineering. At this time of submitting this
report we use this opportunity to mention those people who with us along the work. We take
this occasion to thank God, almighty for blessing us with his grace and taking our endeavor to
a successful culmination. We extend our sincere and heartfelt thanks to our esteemed guide,
Prof. Bhavesh Tanawala & Prof. Mahasweta Joshi for providing us with the right guidanc e
and advice at the crucial junctures and for showing us the right way. We extend our sincere
thanks to our respected Head of the Department Dr. Darshak Thakore for allowing us to use
the facilities available. I also express my sincere gratitude to Mr. Alpesh Kaswala from
Kothari Infotech Pvt Ltd, Surat for constantly guiding and supporting me during the duration
of the project.
We would like to thank the other faculty members also, at this occasion. Last but not
the least; we would like to thank friends for the support and encouragement they have given
us during the course of our work.
Hingu Dhaval Kishanbhai

(17CP308)
ix
List of Figures
Fig 2.1 Iterative Process Model…………………………………………………..5
Fig 2.2 Gantt Chart…………………………………………………………….....6
Fig 3.1 Use Case Diagram………………………………………………………..8
Fig 3.2 System Workflow……………………………………………………….14
Fig 3.3 Class Diagram…………………………………………………………...15
Fig 3.4 Activity Diagram………………………………………………………...16
Fig 3.5 Sequence Diagram……………………………………………………….17
Fig 3.6 State Chart Diagram……………………………………………………...18
Fig 4.1 Script Builder……………………………………………………………..19
Fig 4.2 Print Automation Setting………………………………………………….20
Fig 4.3 General Database Connector……………………………………………....21
Fig 4.4 Field Mapping……………………………………………………………...22
Fig 4.5 Job Sheet…………………………………………………………………....23
Fig 4.6 Tracking Stages……………………………………………………………..24
Fig 4.7 Queued Ticket……………………………………………………………….25
Fig 4.8 Tracking Panel……………………………………………………………….26
x
List of Tables
Table 4.1 Coding Standards……………………………………………………….27
Table 4.2 Xml Ticket Generator Test Suite 1……………………………………...29
Table 4.3 Xml Ticket Generator Test Suite 2……………………………………...30
Table 4.4 Xml Ticket Generator Test Suite 3………………………………………30
xi
ABBREVIATIONS
WAS – Workflow Automation System
PA – Postal Agent
1
CHAPTER 1 INRODUCTION
1.1 Project Overview
The advent of digital technologies opened up possibilities of interacting with the customers
even before the production has started. Customers through these interactions are making
customization choices for the products before they are produced for them. Therefore, there
is a need of a workflow apparatus that is not only dynamic in nature but also adaptable to
changing needs of the customer centric manufacturing, which can also meet the
requirement of the changing landscape of manufacturing.
To achieve all the above needs, Workflow Automation System is developed. It relates to
an apparatus and method for automating the workflow processes related to manufacturing
or management using a data file containing the workflow data and information,
configurable end points of Process stages and network of digital Postal agents. It also
provides method and apparatus for the user to define his/her own workflow process and the
means to interface with the existing data sources like ERP etc, at both the terminal ends.
At the starting point to source the data for the workflow from the data sources and at the
terminating point to store the outcome back into the data sources. Thus, WAS not only
simplifies the operations, but also reduce the skill required to operate.
1.2 Objective
The basic objective of Workflow Automation System is to simply and automate the
production workflows for businesses of all sizes. To achieve this following objectives needs
to be met.
 To define an apparatus to achieve the following objectives.

 To define a method / apparatus that is able to allow the user to dynamically define
the multiple workflows.
 To allow the user to gather, generate and use data to complete the workflow.
2
 To automate the entire workflow process as defined by the user.

 To provide the end results or data to the existing IT systems for verification and
storage, consolidation and further action.
1.3 Scope
WAS is developed to improve the productivity and quality by enforcing best practices in
workflow processes involved in manufacturing as well as management. It allows to define
the workflow process from the data fetched from the data sources and the network location
of the various stages at which the execution of that particular stage is performed and job
ticket is generated accordingly. The system is able to move the job ticket automatically
without any intervention of any external factor. Also the user is able to have a visual display
of status of any job ticket at any point of time. The system is also adaptable to changes at a
particular stage.
1.4 Tools and Technology Used
Editor :
- Visual Studio 2012 : It provides the facilities to develop, compile, debug, and run
any MFC application as well as C++ programs.
Technologies :
i. Programming Purpose :
- MFC (Microsoft Foundation Classes): It provides a C++ object-oriented wrapper
over Win32 for rapid development of native desktop applications.
- C++ : It provides the basic object oriented concepts which are essential for building
an efficient and flexible application
ii. Interaction Purpose :
- JavaScript: It is used to allow the interaction with web.
3
iii. Database Purpose :
- XML (Extensible Markup Language): It is used to store the order data and also is
able to extend itself when necessary.
XSD (XML Schema): It specifies how to formally describe the elements in XML
document.
4
CHAPTER 2 PROJECT MANAGEMENT
2.1 Project Planning
2.1.1 Project Development Approach and Justification
For developing the Workflow System, we followed Iterative Process Model. This model
focuses on an initial, simplified implementation, which then progressively gains more
complexity and a broader feature set until the final system is complete. After an initial
planning phase, a small handful of stages are repeated over and over, with each completion
of the cycle incrementally improving and iterating on the software.
The reason behind choosing Iterative Process Model for developing Workflow Automation
System is because all the requirements were not cleared at the starting phase. The first
prototype is build according to the initial requirements and as and when new requirements
were identified, changes were made accordingly in the system and new prototype is
developed and the cycle repeats.
FIG 2.1 ITERATIVE PROCESS MODEL
5
CHAPTER 2 PROJECT MANAGEMENT

2.2 Project Work Scheduling
This section includes assorted project management and scheduling diagram to

elucidate the work process of the project.
2.2.1 Gantt Chart Representation
A Gantt chart is a type of bar chart that illustrates a project schedule.
Task Name Dec-Jan Feb-March. April-May
Requirements
Gathering
Analysis
Design
Coding
Testing
Correction
FIG 2.2 GHANTT CHART
6
Mind Mapping is helpful for understand any Individual Component.
7
CHAPTER 3 SYSTEM REQUIREMENTS STUDY & ANALYSIS
3.1 User characteristics
The users of this system can be any manufacturing industry or management organization
who has a step by step process execution and also there is a need for the workflow apparatus
that is dynamic in nature and also adaptable to changing needs.
The system is more useful for industries moving towards customer centric manufacturing
and automated manufacturing.
3.1.1 Use Case Diagram
A use case diagram is a graphic depiction of the interactions among the elements of a
system. A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements
FIG 3.1 USE CASE DIAGRAM
8
In the above figure, there are 5 actors in the system which interacts with each other and
completes the execution of the system.
3.2 Hardware and Software Requirements
System Recommendations for end user:
Processor: Requires a PC based on Intel i5 or i7 quad core (3.3 GHz) or higher

processor.
Operating System: Microsoft® Windows® 7 64-bit or later. RAM: 6GB DDR3 or

more.
Hard Disk: Hard Drive with SATA interface and 1 TB free disk space. Solid state drives
are recommended for better performance.
Monitor: SVGA or better with resolution of 1280 x 1024 or better. 32 bits or more color
support recommended.
Printer: Subjected to software specification.
Redistributable components: Visual C++ 2012 Redistributable.
Software: Internet Explorer, Access ODBC driver.
System Recommendations for Software Developer:
Processor: Requires a PC based on Intel i7 quad core (3.3 GHz) or higher processor.
Operating System: Microsoft® Windows® 7 64-bit or later. RAM: 8GB DDR3 or

more.
Hard Disk: Solid state Hard Drive with SATA interface and 1 TB free disk space.
Monitor: SVGA or better with resolution of 1280 x 1024 or better. 32 bits or more color
support recommended.
9
Software: Visual studio 2012, GIMP, Internet Explorer, Access ODBC driver.
3.3 Assumption and Constraints
User process should be divided into set of particular task (step by step process execution)
The systems in the organization or industry should be part of network.
3.4 Study of Existing System
Conventional Systems :
Most manufacturing industry and management organization used a conventional method

for the workflow processes.
ERP and MIS Systems :
ERP and MIS systems are also used to track business and make weighted operational and
management decision.
Other Workflow Systems :
There are some software for Automation such as Kissflow that is a cloud-based forms
automation solution that automates business processes and track performance.
3.5 Limitation of Existing System
Conventional Systems :
 Conventional process of any workflow system can be laborious and slow

 Every stage in the production or service chain has its own execution speed and hence
has the potential to become a bottleneck and define the entire workflow's overall speed.
 Efficiency of the labors cannot be fully utilized and there are many chances of error.
10
ERP and MIS Systems :
 ERP and MIS systems typically serviced the requirements of workflows that were
defined largely with static boundaries and implemented as organization wide practices.
This would also mean that there was a little scope for experimentation outside of the
box.
Other Workflow System :
 Other Workflow Systems are general purpose systems for managing the workflow, but
WAS is a system designed specifically for a Customer i.e any Printing Industry
3.6 Requirements of Proposed System
System has been designed to manage the production workflows and simplify them.
3.6.1 Functional Requirements
R.1 Fetch Data
Description: Fetch the data from the data sources and convert into a particular format.
Input: User entered data
Output: Fetch the data into desired format
R.2 Xml Ticket Generator
Description: From the data fetched from data sources, Xml Ticket Generator will
map it with fields of the schema of Workflow, define a process and stages and the
location associated with that stages and generate the job ticket
Input: Data fetch from the data sources
11
Output: XML Job Ticket
R.3 Digital Postal Agent
Description: It will move the job ticket from one location to another by reading the
tracking information available in the job ticket.
Input: Tracking information of job ticket
Output: Updated job ticket (After the completion of task the job ticket is updated
which defines that a particular task is completed and its needed to be move to its next
destination)
R.4 Client Terminal
Description: A machine or a service present to process, request data, make calls to

end–points; all with respect to the Job/s in progress at the terminal.
Input : Information corresponding to that stage from the job ticket
Output : Updated Job Ticket
R.5 Generic Server
Description: It is a repository of Job tickets arriving at a stage. Its Job is to make a

Job Ticket available, when a Processing Client will request for it. Once, the Job is
completed, the Job Ticket is returned to it by the Processing Client along with the
status of the Job. The Job Ticket Server then hands over the updated Job Ticket to its
Postal Agent, who will then forward it to the next destination.
Input : Job ticket
Output : Updated Job Ticket
12
R.6 Configurable End Points
Description: It is the terminal end of the processing client that is connected to a

machine or a service or a combination responsible for processing the incoming Job.
The type of machine or the service connected is completely unknown to the
Workflow Automation apparatus, since the Process itself and the data associated with
it is user defined to start with. Therefore, the end point provides a mechanism for
configuration by the user.
Input: Program script defined by the user, a simple port connection to transfer the
Job data, a call to another process to handle the processing, WebSockets, HTTP
transfer, Internet of Things (IOT) protocol etc
Output: Connection with the specified End Point
R.7 Tracking Panel
Description: Display status of the Jobs in the system at any given time. Jobs can not
only be monitored for its progress but also can be canceled, paused or rescheduled in
case of error.
Input: Tracking information of the job ticket

Output: Visual representation of the status of the job ticket.
3.6.2 Non-Functional Requirements

 Usability- WAS is developed taking into consideration the target audience and
study of various manufacturing industries
 Modifiability: The system or the modules can be modified according to the

customer’s requirement.
13
 Extensibility- New features can be added to it in the future without many changes
 Maintainability- Lower Maintenance is required and if necessary the facilities will

be provided from our side.
 Security- The deployment is on the local network, therefore data privacy and
security is maintained
3.7 System Workflow
The diagram below shows the how the each component in the system is connected and how
the system works
FIG 3.2 SYSTEM WORKFLOW
14
3.8 Class Diagram
A Class diagram in the Unified Modeling Language(UML) is a type of static structured

diagram that describes the structure of the system by showing system’s classes, their
attributes, operations (or methods) and the relationship among objects.
In XML Ticket Generator, the module I had been Working on required 4 classes as
mentioned below in the figure.
FIG 3.3 CLASS DIAGRAM
15
3.9 Activity Diagram
Activity Diagram focuses on the execution and the flow of the behavior of the system.
FIG 3.4 ACTIVITY DIAGRAM
16
3.10 Sequence Diagram
Sequence Diagram shows object interactions arranged in time sequence.
FIG 3.5 SEQUENCE DIAGRAM
17
3.11 State Chart Diagram
State Chart Diagram is used to model the dynamic nature of the system.
FIG 3.6 STATE CHART DIAGRAM
18
CHAPTER 4 SYSTEM DESIGN
4.1 Database Schema Design
The data in the workflow automation system are the transient data which are transferred
from one stage to another through the xml file so there is no need to store that data in
database.
This system does not use any permanent data. The data is just moved from one location to
other as per defined by the user.
The data which are being transferred from one location to other is store in the xml format
and the validation of the fields of the xml file is by the xml schema.
4.2 Screen Layouts (FORMS AND REPORT)
The below figure defines the Script Builder which is used to write and run the Scripts.
FIG 4.1 SCRIPT BUILDER
19
Print Automation Setting is used to define the location where the job ticket will be stored
after the job is done or after an error occurred during the process.
FIG 4.2 PRINT AUTOMATION SETTING
20
General Database Connector provides the connection with different types of databases.
FIG 4.3 GENERAL DATABASE CONNECTOR
21
Field Mapping provides the functionalities to map the data fields from data sources with
the data fields define by the schema.
FIG 4.4 FIELD MAPPING
22
Job Sheet provides functionality to create the job sheet and store it in a location.
FIG 4.5(JOB SHEET)
23
Tracking Stages allows to create the process by defining the stages and their corresponding
locations.
FIG 4.6 TRACKING STAGES
24
FIG 4.7 QUEUED TICKET
Tracking Panel provides the visual display of the status of the job ticket in any particular
point of time
25
FIG 4.8 TRACKING PANEL
4.3 Method Pseudo Code
The module which I had worked on is XML Ticket Generator so following is the pseudo
code for the same.
4.3.1 Xml Generator Pseudo Code
 Fetch the data from data sources

 Store data in a particular format
 Create schema for each stage of the process
 Mapping of data fields of order data with the schema define for the stages
 Define stages
 Define location of the stages
 Define process
 Define process stages and corresponding location
 Generate job ticket
Other modules are as the following.
26
 Data Connector
 Automation Agent
 Generic Server
 Client Terminal
 End Point Configuration
4.4 Coding Standards
The system is developed using the object oriented technology so the name of the classes
and its data members should be appropriate.
The names of each variable should be meaningful and according to the context.
TABLE 4.1 CODING STANDARDS
Datatype Prefix Example
Integer I int iRadius
Character C char cFullName
Bool B bool bCheck
Double D double dRadius
Global variable G int giRadius
Class Object Cl ClassName clObjectName
Class data member _ int i_Radius
27
Function Fn int fnGetData ()
Arguments A Int fnSetData(int iaRadius)
 Write a proper justification and purpose in comments before adding new class or
function.
 Give the proper understanding of the function by explaining its arguments it will
receive and the return type of the function.
Other coding standards are same as per defined by Microsoft.
4.5 Testing Method
 Testing Paradigm
Before making changes in actual environment, the system is deployed in the local
server and functionality are tested and analyzed.
If all the functionalities are executed perfectly and changes or additions are made
as desired, then all the components are pushed towards actual environment. If any
disruption and outage is observed, then root cause and other factors are listed and
accordingly the programming has been corrected.
 Testing Methods
Testing methods for deployment are taken up depending on the environment

which is getting tested because for each environment, acceptance criteria are
different.
But the common functionalities which are checked are whether the software runs
properly in different systems and each component of the software individually
performs it task efficiently and also when all the components are run together.
28
4.6 Test Cases
TABLE 4.2 XML TICKET GENERATOR TEST SUITE 1
T est XT G001 T est Name: Job T icket

ID: Generation
Step Step Detail Expected Result Actual Pass/Fail

Result
1 After defining the Job Ticket should be As Pass
process job ticket should generated expected
be generated
2 Sequence of stages in Sequence should be As Pass
job ticket should be as maintained expected
per defined by the user
3 Location defined in the Only Valid Location are As Pass
job ticket should be valid allowed expected
4 The data in the job ticket The data in the job ticket is As Pass
should be as per the same as per the order data expected
order data
29
T est XT G002 T est Name: Process

ID: Creation

Result
1 Allow multiple location Multiple locations are allowed As Pass
for each stage for each stage expected
2 Location defined should Allow only if the location is As Pass
be connected in valid expected
network
3 Process Creation For each process the stages As Pass
sequence as defined should be expected
followed along with the
location
T est XGT 003 T est Name: Mapping of data

ID:

Result
1 Different Allow different database for the order As Pass
database data expected
2 Mapping of Each data fields should be mapped As Pass
data fields with the data fields of database expected
30
CHAPTER 5 FUTURE ENHANCEMENT & CONCLUSION
5.1 Future Enhancement
WAS is a system build for a specific client which is a printing industry but it can be used
by other industries or client by doing necessary changes.
1) Improvement in this system itself i.e after client uses

The changes will be made according to the feedback from the client I the same
system.
2) Making the system compatible with other industries or other client

The necessary changes structured changes will be made to the system to make it
useful for other industries or as per the other client requirement.
3) Deployed on cloud than TCP/IP
The system can be deployed on cloud if required.
4) Compatible with other OS

Make the system useful in other Operating system as Linux.
31
5.2 Conclusion
5.2.1 Self-analysis of Project Viabilities
The Functionalities of “Workflow Automation System” have been developed following all
customer requirements and has been delivered after thorough code review and testing. I
believe that all the functionalities will serve the purpose developed for and will be helpful
for the users to get better way for managing their workflow.
5.2.2 Problem Encountered and problems solution
 Understanding the project idea and the purpose of the building such system was the
main task and finding the answer of the questions was the main challenge.
 Also designing the interface and making the best use of object oriented concepts
was quite difficult
.
 Thinking of the best methods which can make the system more efficient, user
friendly and adaptable to changes when required.
 Choosing appropriate technology to build the system.
32
5.2.3 Summary of Project Work
WAS is directed to an apparatus for developing a process flow to allow an user to execute
a manufacturing process, the apparatus comprises:
 A Data Connector for allowing data connections between the apparatus and various
associated input resources sequentially disposed including mapping between the
data fetched and a Job Ticket derivable from the order data, the job ticket comprises
various data sections applicable to the process for manufacturing
 A Job Ticket Generator for allowing user interaction with the input resources to
carry out a plurality of task
 A Process Creator to define and create the process Stages for the Process execution
based on transformed data from the input resources.
 One Postal Agent for moving a job ticket to its next destination based on tracking
of information available inside the job ticket and updates the current status of the
job and transmits to a control panel in every step.
 One Job Ticket Server making available the applicable job ticket for execution of
task, to a particular stage in the process;
 One Processing Client present at a processing stage for initiating a call to an End
Point, along with the job related data.
 One end point configurable for multitasking, connectable to a machine or a service

or combination of both assigned for processing the incoming job.
33
 A control panel for displaying the status of the process flow development at any
given point of time.
34
References
 Programming Windows with MFC – Jeff Prosise, Published in 1996

 Speaking JavaScript - Axel Rauschmayer, Published in 2014
 Visual Studio 2012 help center
 XML and Web Sevices Unleashed –Ron Schmelzer, Published in 2002
35

College Automation Project

Uploaded by

Document Information

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

College Automation Project

Uploaded by

Copyright:

Available Formats

WORKFLOW AUTOMATION SYSTEM 17CP308

WORKFLOW AUTOMATION SYSTEM

HINGU DHAVAL KISHANBHAI

B. TECH. (COMPUTER ENGINEERING)

Under the course of

CP446: FULL SEMESTER EXTERNAL PROJECT)

BIRLA VISHVAKARMA MAHAVIDYALAYA

GUJARAT TECHNOLOGICAL UNIVERSITY,

The project work entitled “WORKFLOW AUTOMATION SYSTEM"

(Name & Designation)

Prof. Bhavesh Tanawala

Professor of Computer Engineering

Prof. Mahasweta Joshi

Professor of Computer Engineering

(Dr. Darshak G Thakore)

Institute code: 007

Hingu Dhaval Kishanbhai (17CP308)

3.11 State Chart Diagram........................................................................................... 18

Workflow Automation System – Patterns for Automated Manufacturing is a

Hingu Dhaval Kishanbhai

Fig 2.1 Iterative Process Model…………………………………………………..5

Fig 2.2 Gantt Chart…………………………………………………………….....6

Fig 3.1 Use Case Diagram………………………………………………………..8

Fig 3.2 System Workflow……………………………………………………….14

Fig 3.3 Class Diagram…………………………………………………………...15

Fig 3.4 Activity Diagram………………………………………………………...16

Fig 3.5 Sequence Diagram……………………………………………………….17

Fig 3.6 State Chart Diagram……………………………………………………...18

Fig 4.1 Script Builder……………………………………………………………..19

Fig 4.2 Print Automation Setting………………………………………………….20

Fig 4.3 General Database Connector……………………………………………....21

Fig 4.4 Field Mapping……………………………………………………………...22

Fig 4.5 Job Sheet…………………………………………………………………....23

Fig 4.6 Tracking Stages……………………………………………………………..24

Fig 4.7 Queued Ticket……………………………………………………………….25

Fig 4.8 Tracking Panel……………………………………………………………….26

Table 4.1 Coding Standards……………………………………………………….27

Table 4.2 Xml Ticket Generator Test Suite 1……………………………………...29

Table 4.3 Xml Ticket Generator Test Suite 2……………………………………...30

Table 4.4 Xml Ticket Generator Test Suite 3………………………………………30

WAS – Workflow Automation System

1.1 Project Overview

 To define an apparatus to achieve the following objectives.

 To automate the entire workflow process as defined by the user.

1.4 Tools and Technology Used

iii. Database Purpose :

CHAPTER 2 PROJECT MANAGEMENT

2.1 Project Planning

2.1.1 Project Development Approach and Justification

FIG 2.1 ITERATIVE PROCESS MODEL

CHAPTER 2 PROJECT MANAGEMENT

This section includes assorted project management and scheduling diagram to

2.2.1 Gantt Chart Representation

A Gantt chart is a type of bar chart that illustrates a project schedule.

Task Name Dec-Jan Feb-March. April-May

FIG 2.2 GHANTT CHART

Mind Mapping is helpful for understand any Individual Component.

CHAPTER 3 SYSTEM REQUIREMENTS STUDY & ANALYSIS

3.1 User characteristics

3.1.1 Use Case Diagram

FIG 3.1 USE CASE DIAGRAM

3.2 Hardware and Software Requirements

System Recommendations for end user:

Processor: Requires a PC based on Intel i5 or i7 quad core (3.3 GHz) or higher