Entry-Task-Validation-Exit (ETVX)

Entry-Task-Validation-Exit (ETVX)  ETVX method comes with ETVX diagrams to describe the Entry conditions, Tasks to be performed, Validation of the tasks and the Exit conditions. ETVX method is primarily for the description of activities, which are a set of tasks to be performed. This is not a method to depict the higher level or organizational level processes. ETVX uses a simple technique of identifying the four important phases of any activity at a sub process level. These four phases of any activity are Entry Criteria, Tasks to be performed, Exit Criteria and Validation, Verification Conditions for each task. The purpose of using a process definition method such as ETVX is to develop an operational definition of the activity under a process architecture. These operational definitions can then be adapted or tailored for use on all projects which uses the defined process architecture.

To be operational, the documented process must put communicable meaning into the concepts and express the activity of the process or process itself in operational terms to: identify and define entry criteria to begin activity, probably a "from" activity for traceability, state or condition of inputs, eg., work products or data used identify and define the individual atomic tasks, task descriptions of what is to be accomplished like enumerated procedures or steps, organizational roles, responsibilities, units or automation of performing the tasks, identify and define validation and verification procedures to verify quality of work items or work products produced by tasks, identify and define an exit criteria to complete the activity, in most cases with a state or condition of outputs, e.g., work products or information produced, probably a "to" activity for traceability.

Process Model: ETVX The Entry-Task-Validation-Exit (ETVX) model views processes within the context of: Inputs or triggers Tasks (also called procedures) Controls Constraints Output

Entry Criteria or Trigger Tasks Validation Exit Criteria Entry Criteria CONTROL CONSTRAINTS Process Output Entry Criteria or Trigger Ensure that all exit criteria have been satisfied Correct any non- conformning or missing exit criteria Factors and/or activities to control the process (policy, standards, SLAs, etc.) Tasks required to create process output Limitations (technical, procedural, etc.)

Process components Entry Criteria: Inputs and Triggers Tasks Processes are initiated by either an input or a trigger. An input is usually an output from a preceding process; a trigger is an event that invokes the process. In either case, input or trigger, an associated list of entry criteria must be satisfied in order for the process to commence. Tasks Tasks (also called procedures) are the action components of a process. In the ETVX model tasks follow a sequence that has a validation step. This step ensures that the process does not pass its output to another process or terminate until all exit criteria have been satisfactorily met. Validation This is a process checkpoint that occurs after the task(s) associated with the process have been completed. This checkpoint is also known as a quality gate - its purpose is to ensure that the task(s) have produced an output that meets specifications and/or requirements of the process. A failure at the validation checkpoint generally requires re-performing the process tasks.

Process components Exit Criteria Controls Constraints All conditions that must be present and/or satisfied before a process can successfully terminate. Closely coupled to exit criteria is the output of the process itself; i.e., what the process was designed to produce. All processes produce an output. Controls Process controls are limits that have been purposely placed on the process to prevent undesirable outcomes. Examples include: Policies. Checkpoints. Audits and integrity checking (i.e., cyclic redundancy checks, etc.) Error detection and correction processes. Constraints Limitations imposed on a process are called constraints. Examples include technical capabilities, available time frames, resources, transmission speeds, etc. The key difference between a control and a constraint is that a control is designed into the process to produce or effect a desirable outcome, while a constraint is a limitation to the process (or environment) that may impact on the effectiveness and/or efficiency of the process.

ETVX Specification ETVX approach to specify a step Entry criteria: what conditions must be satisfied for initiating this phase Task: what is to be done in this phase Verification: the checks done on the outputs of this phase eXit criteria: when can this phase be considered done successfully A phase also produces information for management

ETVX approach

Sample ETVX Diagram

ETVX Example: Change management

Refrences http://www.oocities.org/goutamvs/PDM-ETVX.html http://www.tarrani.net/mike/ETVXSummary.pdf https://web.cs.dal.ca/~arc/teaching/CS3130/Lectures/2-ProcessModels.ppt http://www.philadelphia.edu.jo/academics/enaffar/uploads/2-SoftwareProcess.ppt Radice, R.A.; Roth, N.K.; O'Hara, A.C., Jr; Ciarfella, W.A. " A Programming Process Architecture" IBM Systems Journal Vol.24, No 2 (1985), pp.79-90.

conclusion One approach for organizing data is “ETVX”, Entry includes all inputs you require,internal and external to your project etc Exit specifies all of your expected outputs Task and validation provides information on the work you will need for estimation,execution and control.