|Reference||/Garg, 1994/ The SMART Approach for Software Process Engineering|
This involves the evaluation of the static and dynamic properties of a process model, including its consistency, completeness, internal correctness, and traceability. Examples of useful static analysis are to find out: the maximum number of activities that can be carried out in parallel within a process, the number of activities that use the output of a particular activity, and other descriptive analysis.
At this stage, one might want to carry out a simulation that involves symbolically executing process models in order to determine the path and flow of intermediate state transitions in ways that can be made persistent, replayed, queried, dynamically analysed, and reconfigured into multiple alternative scenarios. For example, hypothetical agents and resources can be assigned to the process and the process engine started. During the execution, one can discover dependencies between activities and agents, e.g. Agent 1 cannot start any work unless Agent 2 has finished the requirements activity.
Multiple graphic views or visualizations of the software process at this stage help in understanding process flow relationships. For example, sometimes it is useful to view the process from an activity viewpoint, while other times it might be useful to view it from a data-flow or role-specific viewpoint.
The use of process traces, process definitions, and process plans to assess process behavior.
|This page online GDPA Online Last Updated 10.June.2002 by C. Freericks|