Towards a Strategic Requirements Elicitation - A Proposal of the PRINCE Model

Requirements changes are sometimes pointed out as being one of the causes for project failure. Our solution to cope with this problem is to plan and manage requirements changes strategically. This paper introduces the PRINCE model that consists of 3+1 types of requirements elicitation processes based on the time of the maturation of the requirements elicitation activity. To explain the model, we show a real case with quantitative observations of a requirements elicitation process. When we are able to elaborate a strategy of requirements elicitation with the PRINCE model, we can elicit requirements by need of the physical development, rather than the theoretical development process model.

[1]  Frank Houdek,et al.  Analyzing requirements engineering processes: a case study , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.

[2]  Meir M. Lehman.  Feedback in the software evolution process , 1996, Inf. Softw. Technol..

[3]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[4]  Steve Riddle,et al.  Tailoring Traceability Information to Business Needs , 2006 .

[5]  Tony Gorschek,et al.  Handshaking Between Software Projects and Stakeholders Using Implementation Proposals , 2007, REFSQ.

[6]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[7]  Taichi Nakamura.  Analysis of project management reports of 49 system integration projects , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[8]  Agile Manifesto,et al.  Manifesto for Agile Software Development , 2001 .

[9]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[10]  Ian Sommerville,et al.  Integrated requirements engineering: a tutorial , 2005, IEEE Software.

[11]  Sankar R. Kousik,et al.  Total Requirements Control at Every Stage of Product Development , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[12]  Takako Nakatani,et al.  A Case Study: Requirements Elicitation Processes throughout a Project , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[13]  Shigeru Yamada,et al.  Extraction of viewpoints for eliciting customer's requirements based on analysis of specification change records , 2007, 14th Asia-Pacific Software Engineering Conference (APSEC'07).

[14]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..