Defining a Requirements Process Improvement Model

  • Authors:

  • Sarah Beecham;Tracy Hall;Austen Rainer

  • Affiliations:

  • Department of Computer Science, University of Hertfordshire, Hatfield, UK A10 9AB;Department of Computer Science, University of Hertfordshire, Hatfield, UK A10 9AB;Department of Computer Science, University of Hertfordshire, Hatfield, UK A10 9AB

  • Venue:
  • Software Quality Control
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

Both software organisations and the academic community are aware that the requirements phase of software development is in need of further support. We address this problem by creating a specialised Requirements Capability Maturity Model (R-CMM1). The model focuses on the requirements engineering process as defined within the established Software Engineering Institute's (SEI's) software process improvement framework. Our empirical work with software practitioners is a primary motivation for creating this requirements engineering process improvement model. Although all organisations in our study were involved in software process improvement (SPI), they all showed a lack of control over many requirement engineering activities.This paper describes how the requirements engineering (RE) process is decomposed and prioritised in accordance with maturity goals set by the SEI's Software Capability Maturity Model (SW CMM). Our R-CMM builds on the SEI's framework by identifying and defining recommended RE sub-processes that meet maturity goals. This new focus will help practitioners to define their RE process with a view to setting realistic goals for improvement.