Defining a Requirements Process Improvement Model

被引:0
作者
Sarah Beecham
Tracy Hall
Austen Rainer
机构
[1] University of Hertfordshire,Department of Computer Science
来源
Software Quality Journal | 2005年 / 13卷
关键词
requirements engineering (RE); requirements engineering process; software process improvement; RE process improvement; Software Capability Maturity Model (SW CMM); goal-question-metric;
D O I
暂无
中图分类号
学科分类号
摘要
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.
引用
收藏
页码:247 / 279
页数:32
相关论文
共 29 条
  • [1] Basili V.R.(1988)The tame project: Towards improvement-oriented software environments IEEE Transactions on Software Engineering 14 758-773
  • [2] Rombach H.D.(2003c)Software process improvement problems in 12 software companies: An empirical analysis Empirical Software Engineering 8 7-42
  • [3] Beecham S.(1999)Simulation in support of CMM-based process improvement Journal of Systems and Software 46 107-112
  • [4] Hall T.(2000)Models implementation: A state of the art European Journal of operational Research 134 459-480
  • [5] Rainer A.(2001)Maturity and its impact on new product development project performance Research in Engineering Design 13 23-29
  • [6] Christie A.M.(1996)User participation in the requirements engineering process: An empirical study Requirements Engineering Journal 1 4-26
  • [7] David A.(1997)Software development process: A necessary evil Communications of the ACM 40 101-103
  • [8] Dooley K.(1996)Level 6: Why we can’t get there from here IEEE Software 13 97-98
  • [9] Subra A.(2002)Three process perspectives: organizations, teams, and people Annuls of Software Engineering 14 39-72
  • [10] Anderson J.(2001)Preventing requirement defects: An experiment in process improvement Requirements Engineering Journal 6 37-50