Software Development Process Models: A Technique for Evaluation and Decision-Making

Abstract

Process models are the bedrock on which all software development projects are based. Since the first process model was defined in the late 1950s, more contemporary processes have evolved to deal with even more complex projects in even more dynamic problem domains. Although there are many such process models now available for software engineers to follow, they can be classified according to one of five basic types. They differ in the level to which the process might be applied and also in the additional guidelines and philosophies they define. In this paper we define those five fundamental process types. The paper goes on to present a definitive technique for comparing such process models—the Functionality‐Time graph. By combining this technique with a Functionality‐Cost/Benefit graph, it helps to identify the key decision points in the software development process with respect to a software system's functionality. Such a hybrid technique helps project managers to recognise the point at which to draw closure on an existing system by showing potential losses if the project continues. By attempting to identify where they lie on the graphs defined in this paper, project managers can determine the consequences of decisions at different stages of the software life cycle. The hybrid graphs also provide an invaluable educational tool that help software engineers understand the development processes they adopt and clarifies the differences between them. Copyright © 2013 John Wiley & Sons, Ltd.

Developing a Memory and Communication App for Persons Living With Dementia: An 8-Step Process

“…The underlying principle for developing My PATI in steps 1 through 4 in Figure 2 is based on 3 software process models. These models included the incremental, throwaway prototype, and agile (a combination of incremental and prototyping, see Textbox 2 for definitions) models [ 38 , 39 ]. My PATI is a research app, thus making the requirements, by definition, inherently vague.…”

Blinded by Simplicity

“…The complexity of the software development processes (SDP) depends on many structural and managerial factors. From a managerial perspective the overall development process can be divided into five central components that consume the project: time, resources, money, scope, and quality [15], see figure 1. Figure 1.…”

“…The first software process model known, the stage-wise approach (later called the Waterfall model), was defined in 1956 by Herbet D Bennington. Since the 50's, process models have evolved to handle the growing complexity of projects dealing with more dynamic problem domains [15]. [15] identify four main categories of process models that capture the quintessence of all existing models.…”

“…Since the 50's, process models have evolved to handle the growing complexity of projects dealing with more dynamic problem domains [15]. [15] identify four main categories of process models that capture the quintessence of all existing models. In table 1. they are organized in a matrix divided into high and low uncertainty of requirement respective complexity of system: incremental models are suited for processes with low uncertainty and high complexity (e.g.…”

Domain-specific reasoning for method engineering based on Toulmin's argumentation theory

“…Unfortunately these approaches concentrate primarily on the management and change of requirements; the need to translate from natural language to the modelling language remains. Additionally there are approaches, like the waterfall model and its derivatives [15,16], which can be used to guide the process of modelling. However, with the strict focus on the actual process, the generality of these approaches restrains them to be used with general purpose languages, such as programming languages.…”