Example Process Modelling Tools

UML is a standardized general-purpose modeling language which includes a set of graphic notation techniques to create visual models of object-oriented software-intensive systems. UML is used to specify, visualize, modify, construct and document the artifacts of an object-oriented software-intensive system under development. UML offers a standard way to visualize a system's architectural blueprints, including elements such as:

 Activities.

 Actors.

 Business processes.

 Database schemes.

 (Logical) components.

 Programming language statements.

 Reusable software components. (See Appendix IV )

3.4.2.2 IDEF

An abbreviation of Integration Definition refers to a family of modeling languages in the field of systems and software engineering. They cover a wide range of uses, from functional modeling to data, simulation, object-oriented analysis/design and knowledge acquisition. The IDEF Functional Modeling method is designed to model the decisions, actions, and activities of an organisation or system. It was derived from the established graphic modeling language Structured Analysis and Design Technique (SADT) developed by Douglas T. Ross and SofTech, Inc. In its original form, IDEF0 includes both a definition of a graphical modeling language (syntax and semantics) and a description of a comprehensive methodology for developing models (See Appendix V).

3.4.2.3 Business Process Model and Notation

Business Process Model and Notation (BPMN) is a standard for business process modeling that provides a graphical notation for specifying business processes in a Business Process Diagram (BPD), based on a flowcharting technique very similar to activity diagrams from Unified Modeling Language (UML). The objective of BPMN is to support business process management, for both technical users and business users, by providing a notation that is intuitive to business representation discussed above. Park and Cutkosky developed this technique to provide a comprehensive method for the project management (PM). The most basic elements of DR are the task and feature, and the tasks and feature are unique in the DR process map. The task is the primary unit of the process, and it represents the elements which are participant in the process. The feature is the input and output of the tasks. Thus every task needs a feature to be the input, and it also needs another feature to represent the output of this task. The arrows are used to represent the process flow and link the tasks and features together. DR

also has the complex dependencies. In these dependences, the feedback dependency is most often to be used (See Appendix VII)

3.4.2.5 Flow Chart

A flowchart is a type of diagram that is used in this research. It is to represents an algorithm or process, showing the steps as boxes of various kinds, and their order by connecting them with arrows. This diagrammatic representation can give a step-by-step solution to a given problem. Process operations are represented in these boxes, and arrows connecting them represent flow of control. Data flows are not typically represented in a flowchart, in contrast with data flow diagrams;

rather, they are implied by the sequencing of operations. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields.

Flowcharts are used in designing and documenting complex processes or programs. Like other types of diagrams, they help visualize what is going on and thereby help the viewer to understand a process, and perhaps also find flaws, bottlenecks, and other less-obvious features within it that is the main reason behind selecting this type of process modelling in this research. There are many different types of flowcharts, and each type has its own repertoire of boxes and notational conventions. The two most common types of boxes in a flowchart are:

 A processing step, usually called activity, and denoted as a rectangular box.

 A decision usually denoted as a diamond.

A flowchart is described as "cross-functional" when the page is divided into different swim lanes describing the control of different organizational units. A symbol appearing in a particular "lane" is within the control of that organizational unit. This technique allows to locate the responsibility for performing an action or making a decision correctly, showing the responsibility of each organizational unit for different parts of a single process.

Flowcharts depict certain aspects of processes and they are usually complemented by other types of diagram. For instance, Ventre and Fowler (2002) defined the flowchart as one of the seven basic tools of quality control, next to the histogram,

Pareto chart, check sheet, control chart, cause-and-effect diagram, and the scatter diagram. Similarly, in UML, a standard concept-modeling notation used in software development, the activity diagram, which is a type of flowchart, is just one of many different diagram types. Common alternate names include:

flowchart, process flowchart, functional flowchart, process map, process chart, functional process chart, business process model, process model, process flow diagram, work flow diagram, business flow diagram. The terms "flowchart" and

"flow chart" are used interchangeably.

Types of flowchart

Flowcharts can be modeled from the perspective of different user groups (such as managers, system analysts and clerks) and that there are four general types.

 Document flowcharts, showing controls over a document-flow through a system

 Data flowcharts, showing controls over a data-flow in a system

 System flowcharts showing controls at a physical or resource level

 Program flowchart, showing the controls in a program within a system

Notice that every type of flowchart focuses on some kind of control, rather than on the particular flow itself. However there are several of these classifications.

For example Ventre (1978) named three basic types of flowcharts: the system flowchart, the general flowchart, and the detailed flowchart. That same year Marilyn (1978) stated "in practice, two kinds of flowcharts are used in solution planning: system flowcharts and program flowcharts.” More recently Ventre and Fowler (2002) stated that there are more differences: "Decision flowcharts, logic flowcharts, systems flowcharts, product flowcharts, and process flowcharts are just a few of the different types of flowcharts that are used in business and government". In this research, Document flowchart type has been used as it covers business process aspect also.