Prescriptive Process Model  

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


Prescriptive Process Model

Also as

Defined process


Reference /Scacchi, 2001/ Process Models in Software Engineering
A prescriptive model prescribes how a new software system should be developed. Prescriptive models are used as guidelines or frameworks to organize and structure how software development activities should be performed, and in what order. Typically, it is easier and more common to articulate a prescriptive lifecycle model for how system should be developed. This is possible since most such models are intuitive or well reasoned. This means that many idiosyncratic details that describes how a software system is built in practice can be ignored, generalized, or deferred for later consideration. This, of course, should raise concern for the relative validity and robustness of such life cycles models when developing different kinds of applications systems, in different kinds of development settings, using different programming languages, with differentially skilled staff, etc. However, prescriptive models are also used to package the development tasks and techniques for using a given set of software engineering tools or environment during a development project.
Reference /Wang Y., 2000/ Software Engineering Processes: Principles and Applications
A prescriptive process model is a model that describes "how to do" according to a certain software process system.
Reference /Lonchamp, 1993/ A Structured Conceptual and Terminological Framework for Software Process Engineering
Within prescriptive software process models, any explicit element which constraints the process performance.

People dealing with software processes may adopt a prescriptive attitude of mind. They define desired processes to answer the question "how software should be developed?

They may aim at:

  • guiding Software process performers (developers, managers, ...) receive indirect support through information which help them to perform their work, such as the current status of the process, the appropriate next steps to be excecuted, the decision points and their meanings, etc. Guidance is provided through manual or mechanical interpretation of software process descriptions simultaneously and synchronously with the actual software process performance.
  • enforcing Software process performers (developers, managers, ...) receive direct support .through enactable software process descriptions which are mechanically interpreted by process engines within a process-centered software engineering environment, to orchestrate the performance of the actual development and to automatize it as far as possible. What cannot be programmed for machine interpretation is left for humans to perform; for instance, the support system can await representable results of the intermediate human process.

Related terms in the glossary

Defined process
Descriptive Process Model
Preceptive Process Model
Proscriptive Process Model
Process Model

Publications on this area


This page online  •  GDPA Online  •  Last Updated 12.June.2002 by C. Freericks