Software Process Models

The software process model maybe defined as a simplified description of a software process, presented from a particular perspective. In essence, each stage of the software process is identified and a model is then employed to represent the inherent activities associated within that stage. Consequently, a collection of  ‘local’ models may be utilised in generating the global picture representative of the software process. Examples of models include the workflow model, the data-flow model, and the role model

·        The workflow model shows the sequence of activities in the process along with their inputs, outputs and dependencies. The activities in the model represent human actions.

·        The dataflow model represents the process as a set of activities each of which carries out some data transformation. It shows how the input to the process such as specification is transformed to an output such as design. The activities here maybe lower than in a workflow model. They may represent transformations carries out by people or computers.

·        The role model represents the roles of people involved in the software process and the activities for which they are responsible.

 In this section of the course focuses on the traditional generic software process models to highlight they effectively demonstrate the different approaches to software development. Such models include the:

  1. Build And Fix

  2. Waterfall Model

  3. Formal Systems Development Model

  4.  Prototyping Model  [Additional information on Prototyping]

  5. Rapid Application Development (RAD) Model

Evolutionary Process Models

  1. Incremental Model

  2. Spiral Model

  3. WIN WIN Spiral Model

Note that these are not definitive descriptions of any particular software process but give an overview of different approaches to software development.


Copyright © Adrian Als, Charles Greenidge & P. Walcott, 2004
This page was last modified: Monday, September 27, 2004