Quantifying the impact of requirements definition and management process maturity on project outcome in large business application development

被引:15
作者
Ellis, Keith [1 ]
Berry, Daniel M. [2 ]
机构
[1] Univ Lancaster, Dept Comp, Lancaster LA1 4WA, England
[2] Univ Waterloo, David R Cheriton Sch Comp Sci, Waterloo, ON N2L 3G1, Canada
基金
加拿大自然科学与工程研究理事会;
关键词
Commercial application (CA) development; Empirical study; On-budget; On-function; On-time; Requirements discovery and management (RDM); RDM maturity; Successful CA development; Survey; SOFTWARE; BENEFITS;
D O I
10.1007/s00766-012-0146-3
中图分类号
TP [自动化技术、计算机技术];
学科分类号
0812 ;
摘要
Using data from two surveys of people knowledgeable about requirements for, and the success of the development of, large commercial applications (CAs) in hundreds of large organizations from around the world, this paper reports a high positive correlation between an organization's requirements definition and management (RDM) maturity and that organization's successful performance on CA development projects. Among the organizations that responded with a filled survey, an organization that is assessed at a high RDM maturity is significantly more successful in its CA development projects than is an organization that is assessed at a low RDM maturity, when success in CA development projects is measured as (1) delivering CAs on-time, on-budget, and on-function, (2) meeting the business objectives of these projects, and (3) the perceived success of these projects. This paper presents a comprehensive framework for RDM, describes a quality RDM process, and describes RDM maturity and how to measure it. It describes the two surveys, the first of which ended up being a pilot for the second, which was designed taking into account what was learned from the first survey. The paper concludes with advice to practitioners on the application of the RDM maturity framework in any organization that wishes to improve its RDM and its performance in the development of large CAs.
引用
收藏
页码:223 / 249
页数:27
相关论文
共 41 条
  • [1] ABBOTT B, 2001, INFOWORLD, V23, P45
  • [2] Alexander L. C., 1991, Proceedings of the Fifteenth Annual International Computer Software and Applications Conference (Cat. No.91CH3023-9), P521, DOI 10.1109/CMPSAC.1991.170231
  • [3] [Anonymous], P IEEE 1 INT S REQ E
  • [4] [Anonymous], 2009, CHAOS SUMM 2009
  • [5] To do or not to do: If the requirements engineering payoff is so good, why aren't more companies doing it?
    Berry, DM
    Damian, D
    Finkelstein, A
    Gause, D
    Hall, R
    Simmons, E
    Wassyng, A
    [J]. 13th IEEE International Conference on Requirements Engineering, Proceedings, 2005, : 447 - 447
  • [6] Boehm BW., 2009, SOFTWARE COST ESTIMA
  • [7] The guide to the software engineering body of knowledge
    Bourque, P
    Dupuis, R
    Abran, A
    Moore, JW
    Tripp, L
    [J]. IEEE SOFTWARE, 1999, 16 (06) : 35 - 44
  • [9] A FIELD-STUDY OF THE SOFTWARE-DESIGN PROCESS FOR LARGE SYSTEMS
    CURTIS, B
    KRASNER, H
    ISCOE, N
    [J]. COMMUNICATIONS OF THE ACM, 1988, 31 (11) : 1268 - 1287
  • [10] Requirements engineering and downstream software development: Findings from a case study
    Damian, D
    Chisan, J
    Vaidyanathasamy, L
    Pal, Y
    [J]. EMPIRICAL SOFTWARE ENGINEERING, 2005, 10 (03) : 255 - 283