Kovair’s configurable IT Process Automation System provides a framework to define and follow software processes whether it is a Software Product Development, an eService Project or even Software Maintenance or IT Projects. Its Omniprocess Automation system has all the special features needed for the ALM workflow or the workflows required for software life-cycle management.

The IT Process Automation Technology is divided in to two different architectures:

• State-based Process
• Task-based Process

State-based Process

A State-based Process depends on two variables for each artifact - a 'State' and an 'Owner'. By changing the State from one value to another the artifact moves along in the Process. As it changes the State often, it is assigned to a different person, the "Owner", who will be responsible for that Item at that State. State based processes though simple, are difficult to model many real life situations, as they do not support parallel activities. Since an item can be in one state at any time, multiple parallel activities on the same item cannot be modelled in State- based processes. Kovair , therefore, employs a Task-based process engine.

Task-based Process

Kovair Global Lifecycle has developed a Task-based Process Engine to address the limitations of State-based Processes and especially to make a Process successful in a distributed environment. Unlike a State-based Process, there can be multiple assignees for an Artifact (Requirement or Issue) at any point of time and each assignee gets a Task with an Activity. For example, in a Requirement Process, a Use Case may be worked on simultaneously by the QA Engineer on a 'Test case design', by the Architect on a 'System design' as well as by the Technical Writer on 'Documentation'. All these activities can go on in parallel. Each of these assignees gets a Task in their Home page instructing them to do the particular activity. Once the Task is complete, the user just closes the Task. At this juncture, the Kovair Global Lifecycle Process will automatically generate the next Task(s) for the appropriate persons (based on the defined Process). It is not necessary for any of the participants to know what the next steps in the Process are nor whom to assign it to next. This is extremely useful in a larger team especially when they are distributed in multiple locations.

To gather more ideas about the product, please visit our collection of whitepapers under the Download section of the website.

Example of Kovair's Parallel Activities

Core Features and Advantages of the Task-based Kovair Omniprocess Capabilities

• Multiple Independent Processes at different levels: Projects, Modules, Releases, Requirements, Issues and any Entity synchronized with each other
• Visual drag and drop process designer on Browser
  The system allows representation of a Process in the form of a Visio-like diagram. User can design any process (Step, Activity, Join, Delay Wait, Links) by using the drag and drop capabilities of the Kovair Process Designer over the Web as well as embed business rules/policy for each process step.
• Parallel Activities
  In real life scenario there are activities, which originate from a common point and then they follow a parallel path. Thereafter, they merge/join based on certain conditions. Kovair allows defining of parallel activities in a process. For example: the diagram on this page shows that upon submission of a ‘Change Request’ the record system generates two parallel tasks- ‘Create Test Script’ and Implement Development Package’. Both these tasks run simultaneously without affecting each other and joining in ‘Wait’ for all inputs.
• Task Assignment to multiple users/roles based on policies: Queued, One task for All, Individual tasks.
• Conditional Branching
  Very few real-life Processes are simple, linear and sequential. Often, Processes follows alternative paths based on different criteria. Kovair Global Lifecycle allows you to add Conditional Branching both between Steps (and between Activities in a Step). The condition can be simple or complex by using AND, OR, NOT or multiple conditional statements.
• Merging/Joining with quorum-based forwarding policy
  In a Process, often multiple parallel branches merge together in order to go forward. The node at which the connectors merge is called a Join Node. It is also referred to as a ‘Merge Node’, ‘Synch Node’ or ‘Rendezvous Node’. In the Join Node it is possible to define a Forwarding Policy which  directs the Process when to move forward. Kovair Global Lifecycle allows two types of Forwarding Policies – Count based or Percentage based.
• Process variables
  The System allows you to add additional fields, called ‘Process Variables’, that are to be used within the scope of the Process. These variables are Process specific and get recycled when the Process gets completed.
• Process Modification without affecting running processes
  If a process is modified the existing records will follow the old process path. The modification will not affect the existing path and the records. The new records created will follow the new process.
• Restart Process at any time for multiple items
  If the user wants the existing record to follow the modified path, he/she can stop the process and re-start it. A new path will be generated for all the records.