Degree of Rigor

For a project of a particular kind the degree of rigor with which the software procedure is applied may vary significantly. The degree of rigor is function of several project characteristics. For an example non-business, small, critical projects can commonly be addressed with somewhat less rigor which is large complex baseline critical applications. It should be noted however, in which all projects must be conducted in a manner which results in timely high quality deliverables. 4 various degrees of rigor can be defined that are:

Casual: In general umbrella tasks will be documentation and minimized needs will be reduced all basic principles of software engineering are yet applicable. All procedural frame work activities are applied but only a minimum task group is needed.

Structured: Framework related tasks and activities appropriate to the project type will be applied and umbrella activities necessary to ensure high quality will be applied. The process framework will be applied for this project. SQA, SCM measurement and documentation tasks will be conducted in a streamlined manner.

Strict: - The full process will apply for this project with a degree of discipline which will ensure high quality. Robust documentation will be produced and all umbrella activities will be applied.

Quick Reaction:  Framework of process will be applied for this project but because of an emergency condition only those tasks essential to maintaining good quality will be applied Back-filling example for developing a complete set of documentation conducting additional reviews will be accomplished after the application or product is delivered to the customer.

The project manager must have to develop a systematic approach for selecting the degree of rigor which is appropriate for a special project. To accomplish this project adaptation criteria are describe and a task set selector value is computed.