![]() |
|
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
2001 | |
---|---|
Reference | /Scacchi, 2001/ Process Models in Software Engineering |
Definition/ Use |
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. |
2000 | |
Reference | /Wang Y., 2000/ Software Engineering Processes: Principles and Applications |
Definition/ Use |
A prescriptive process model is a model that describes "how to do" according to a certain software process system. |
1993 | |
Reference | /Lonchamp, 1993/ A Structured Conceptual and Terminological Framework for Software Process Engineering |
Definition/ Use |
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:
|
This page online GDPA Online Last Updated 12.June.2002 by C. Freericks