Tag Archives: software development life cycle (SDLC)

Requirements Engineering in an Agile Software Development Environment

To print a PDF version of this article, click here.

Author: W. Allen Huckabee

The Business Capability Lifecycle (BCL) methodology, which was implemented to develop defense business systems, requires a change in requirements engineering processes. Previous software development work by Systems, Applications, and Products on the Global Combat Support System-Army (GCSS-Army) followed the waterfall Software Development Life Cycle (SDLC), which is not acceptable in the BCL methodology. The typical functional requirement statement is not easily changed and introduces problems into an Agile SDLC. In this article, the author posits that Agile-based requirements (user story and acceptance criteria) best fit the BCL approach. By implementing best business practices and lessons learned from the GCSS-Army project, a typical BCL-led program can achieve significant benefits, such as (a) increased effectiveness in requirements meeting the users’ needs; (b) increased performance of customers and software developers; and (c) reduced requirements volatility.

Continue reading

Increase Return on Investment of Software Development Life Cycle by Managing the Risk—A Case Study

To print a PDF copy of this article, click here.

Authors: William F. Kramer, Mehmet Sahinoglu, and David Ang

This research article aims to identify and introduce cost-saving measures for increasing the return on investment during the Software Development Life Cycle (SDLC) through selected quantitative analyses employing both the Monte Carlo Simulation and Discrete Event Simulation approaches. Through the use of modeling and simulation, the authors develop quantitative analysis for discovering financial cost and impact when meeting future demands of an organization’s SDLC management process associated with error rates. Though this sounds like an easy and open practice, it is uncommon for most competitors to provide empirical data outlining their error rates associated with each of the SDLC phases nor do they normally disclose the impact of such error rates on the overall development effort. The approach presented in this article is more plausible and scientific than the conventional wait-and-see, whatever-fate-may-bring approach with its accompanying unpleasant surprises, often resulting in wasted resources and time.

Continue reading