Evolving beyond requirements creep: a risk-based evolutionary prototyping model

Evolutionary prototyping focuses on gathering a correct and consistent set of requirements. The process lends particular strength to building quality software by means of the ongoing clarification of existing requirements and the discovery of previously missing or unknown requirements. Traditionally, the iterative reexamination of a systems requirements has not been the panacea that practitioners sought, due to the predisposition for requirements creep and the difficulty in managing it. The paper proposes the combination of evolutionary prototyping and an aggressive risk mitigation strategy. Together, these techniques support successful requirements discovery and clarification, and they guard against the negative effects of requirements creep. We embody these techniques in a comprehensive software development model, which we call the EPRAM (Evolutionary Prototyping with Risk Analysis and Mitigation) model. The model was intentionally designed to comply with the Level 2 Key Process Area of the Software Engineering Institute's Capability Maturity Model. Validation is currently underway on several software development efforts that employ the model to support the rapid development of electronic commerce applications.

[1]  Jawed I. A. Siddiqi,et al.  Validating and evolving software requirements in a systematic framework , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[2]  Horst Lichter,et al.  Prototyping in industrial software projects—bridging the gap between theory and practice , 1994, ICSE '93.

[3]  Pankaj Jalote,et al.  CMM in Practice: Processes for Executing Software Projects at Infosys , 1999 .

[4]  John B. Shoven,et al.  I , Edinburgh Medical and Surgical Journal.

[5]  Alan M. Davis,et al.  Operational prototyping: a new development approach , 1992, IEEE Software.

[6]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[7]  Jakob Nielsen,et al.  Usability engineering , 1997, The Computer Science and Engineering Handbook.

[8]  C. Mahoney,et al.  Managing risk , 2011 .

[9]  Jan Stage,et al.  Controlling Prototype Development Through Risk Analysis , 1996, MIS Q..

[10]  Nuno Jardim Nunes,et al.  Case Study: SITINA - A Software Engineering Project Using Evolutionary Prototyping , 1998 .

[11]  Mark C. Paulk,et al.  Capability Maturity Model for Software , 2001 .

[12]  Judith G. Brodman,et al.  Applying CMM Project Planning Practices to Diverse Environments , 2000, IEEE Softw..

[13]  Walker Royce,et al.  Software Project Management: A Unified Framework , 1998 .

[14]  Walker Royce.  Pragmatic quality metrics for evolutionary software development models , 1990, TRI-Ada '90.

[15]  M. Paulk.  Using the Software CMM in Small Organizations , 1998 .

[16]  R.D. Acosta,et al.  A case study of applying rapid prototyping techniques in the Requirements Engineering Environment , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[17]  A. Sutcliffe,et al.  A technique combination approach to requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[18]  Mark C. Paulk,et al.  The Capability Maturity Model: Guidelines for Improving the Software Process , 1994 .

[19]  D. A. Fern,et al.  Tri-Cycle: a prototype methodology for advanced software development , 1989, [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume II: Software Track.

[20]  Julia B. Earp,et al.  A Multidisciplinary Electronic Commerce Project Studio for Secure Systems , 2000 .

[21]  Gerard O’Regan,et al.  The Capability Maturity Model , 2002 .

[22]  K. Arihiro,et al.  Outcomes of endoscopic submucosal dissection in patients who develop metachronous superficial esophageal squamous cell carcinoma close to a post-endoscopic submucosal dissection scar , 2022, Esophagus.

[23]  Barry W. Boehm,et al.  Identifying Quality-Requirement Conflicts , 1996, IEEE Softw..

[24]  Annie I. Antón,et al.  The role of policy and stakeholder privacy values in requirements engineering , 2001, Proceedings Fifth IEEE International Symposium on Requirements Engineering.

[25]  Ismaïl Khriss,et al.  Generating user interface prototypes from scenarios , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[26]  John Hampton Dempster.  Inconsistency Identification and Resolution in Goal-Driven Requirements Analysis. , 2000 .

[27]  Karlheinz Kautz,et al.  Applying and adjusting a software process improvement model in practice: the use of the IDEAL model in a small software enterprise , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[28]  I. Graham.  Structured prototyping for requirements specification of expert systems , 1989 .

[29]  Ian Graham.  Structured prototyping for requirements specification in expert systems and conventional IT projects , 1991 .

[30]  Narciso Cerpa,et al.  An experience: a small software company attempting to improve its process , 1999, STEP '99. Proceedings Ninth International Workshop Software Technology and Engineering Practice.

[31]  K. Roberts,et al.  Thesis , 2002 .

[32]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[33]  Annie I. Antón,et al.  Strategies for Developing Policies and Requirements for Secure and Private Electronic Commerce , 2001, E-Commerce Security and Privacy.

[34]  Alistair G. Sutcliffe,et al.  Experience with SCRAM, a SCenario Requirements Analysis Method , 1998, Proceedings of IEEE International Symposium on Requirements Engineering: RE '98.

[35]  Mark P. Ginsberg,et al.  Process Tailoring and the the Software Capability Maturity Model , 1995 .

[36]  H. Zullighoven,et al.  Prototyping in industrial software projects-bridging the gap between theory and practice , 1993, Proceedings of 1993 15th International Conference on Software Engineering.

[37]  Luqi,et al.  Process knowledge based rapid prototyping for requirements engineering , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[38]  A. Antón,et al.  Strategies for Developing Policies and Requirements for Secure Electronic Commerce Systems , 2000 .

[39]  Mark C. Paulk,et al.  Using the Software CMM with Good Judgment , 1999 .

[40]  C. Jones,et al.  Strategies for managing requirements creep , 1996 .

[41]  D. Jackson.  Burns , 1828, The London medical and physical journal.