GDPA  
Process Cycle  

A-B-C- D-E-F- G-H-I- J-K-L- M-N-O- P-Q-R- S-T-U- V-W-X- Y-Z

Identification

Process Cycle

Definitions/Uses

1991
Reference /Madhavji, 1991/ The process cycle
Definition/
Use
The process cycle is a concise and integrated view of engineering, management, performance and improvement of software processes. The process cycle, bounded by the sectors A, B and C, defines de scope of the total set of process steps necessary for the development and evolution of software processes.
In addition, the cycle defines the key roles played by human beings, categories of tools used, goals and policies governing the processes, and inter-relationships and feedback among the different roles. The feed-front and feedback links across the three sectors complete a cycle of process engineering, management, performance and improvement: hence, the name process cycle.

Figure Process Cycle
Figure E3: Process Cycle

Sector A: engineering process models
In sector A, process engineers design, construct and improve generic process models according to project-free goals and policies. The goals and policies concern the process of developing process models (i.e. how the process modellers do their job) and the contents of the process models (i.e. what job the process modellers do).

Sector B: managing software processes
The descriptions developed in sector A are then adopted and customised by process managers for use in specific software process.

Sector C: performing software processes
In sector C, process performers (i.e. software developers) carry out software process, in order to build and improve the application software. This act is shown in the process cycle by a thin, downward, broken arrow from the enacted software process to the process performing tools.

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster