The selection of a software development life cycle (SDLC) model for a software project is highly dependent upon the characteristics of the software product to be developed. We classified software products according to characteristics that matter for SDLC selection. We surveyed literature to elicit recommendations for SDLC selection. We formalized our findings to present a rule based recommendation system that can be helpful to software developers in selecting the most appropriate SDLC model to be used for the development of a software product. We conducted an initial evaluation of our system. We believe our SDLC recommendation system provides useful hints for selecting an SDLC, and provides a base for validating and refining SDLC recommendation rules.

A rule-based recommendation system for selection of software development life cycle models

A central concern of systems engineering is selecting the most preferred alternatives for implementation from among competing options. The selection process is sometimes called tradeoff analysis, and is often built on the methods of decision analysis and utility theory. The process can be loosely divided into two parts, a first part in which one determines the relative priority of various requirements, and a second part, a design selection phase, in which alternatives are compared, and the preferred alternatives chosen.



This paper discusses the means of determining the priority order for implementing system changes. It also outlines the implications on the selection process of evolutionary systems development.

11.4.2 Managing Priorities: A Key to Systematic Decision‐Making

We know many of our IT projects fail and disappoint. The poor state of requirements methods and practice is frequently stated as a factor for IT project failure. In this paper, I discuss what I believe is the fundamental cause: we think like programmers, not engineers and managers. We do not concentrate on value delivery, but instead on functions, on use-cases and on code delivery. Further, management is not taking its responsibility to make things better. In this paper, ten practical key principles are proposed, which aim to improve the quality of requirements specification.

/pdf/what-s-wrong-with-requirements-specification-an-analysis-of-5avmvuc4m8.pdf

What's Wrong with Requirements Specification? An Analysis of the Fundamental Failings of Conventional Thinking about Software Requirements, and Some Suggestions for Getting it Right

Building owners, designers and constructors are seeing a rapid increase in the number of sustainably designed high performance buildings. These buildings provide numerous benefits to the o...

A framework for application of system engineering process models to sustainable design of high performance buildings

A central concern of systems engineering is selecting the most preferred alternatives for implementation from among competing options. The selection process is sometimes called tradeoff analysis, and is often built on the methods of decision analysis and utility theory. The process can be loosely divided into two parts, a first part in which one determines the relative priority of various requirements, and a second part, a design selection phase, in which alternatives are compared, and the preferred alternatives chosen. This paper discusses the means of determining the priority order for implementing system changes. It also outlines the implications on the selection process of evolutionary systems development. BACKGROUND

Managing Priorities: A Key to Systematic Decision-Making

Evolutionary development (Evo) focuses on early delivery of high value to stakeholders, and on obtaining and utilizing feedback from stakeholders. This paper describes from a project manager's viewpoint, the positive experiences that one organization rapidly achieved on switching from using the Waterfall method to Evo. Major benefit came from paying greater attention to the quality requirements as opposed to the previous practice of concentrating solely on the required functionality.

11.4.1 From Waterfall to Evolutionary Development (Evo): How we rapidly created faster, more user‐friendly, and more productive software products for a competitive multi‐national market

Trond Johansen

Papers

11.4.1 From Waterfall to Evolutionary Development (Evo): How we rapidly created faster, more user‐friendly, and more productive software products for a competitive multi‐national market