Requirements Engineering: Solutions and Trends

This last chapter of the book describes solutions and trends in the discipline of RE. Starting from a wrap-up of what was presented throughout this book, it suggests a framework of requirements engineering and indicates what current solutions are available in this framework. Beyond providing a short overview of the state of the practice, this chapter also summarizes current trends in RE. Four trends are evaluated, namely the growing usage of commercial off-the-shelf components and systems and how RE activities need to be adjusted; the evolving focus on product lifecycle management and the need to collaborate amongst very heterogeneous communities; the wish to learn and to share experiences on effective ways to implement RE in an organization and the growing interest in requirements engineers’ skill sets. We finally provide an outlook into where requirements engineering is heading for.

[1]  Jeffrey M. Voas,et al.  COTS Software: The Economical Choice? , 1998, IEEE Softw..

[2]  Søren Lauesen.  COTS tenders and integration requirements , 2005, Requirements Engineering.

[3]  M. J. Earl,et al.  E-Commerce Is Changing the Face of IT , 2001 .

[4]  David Lorge Parnas,et al.  Review of David L. Parnas' "Designing Software for Ease of Extension and Contraction" , 2004 .

[5]  Klaus Schmid.  A comprehensive product line scoping approach and its validation , 2002, ICSE '02.

[6]  Barry W. Boehm,et al.  Eight Lessons Learned during COTS-Based Systems Maintenance , 2003, IEEE Softw..

[7]  Christof Ebert,et al.  Using open source software in product development: a primer , 2004, IEEE Software.

[8]  Gordon B. Davis,et al.  Strategies for Information Requirements Determination , 1982, IBM Syst. J..

[9]  Barry W. Boehm,et al.  COTS Integration: Plug and Pray? , 1999, Computer.

[10]  Ralph Young,et al.  The requirements engineering handbook , 2003 .

[11]  Roel Wieringa,et al.  RE'03: practical requirements engineering solutions : Guest editors' introduction , 2004 .

[12]  Timo Saarinen,et al.  Managing the risks of information systems implementation , 1993 .

[13]  Marco Torchiano,et al.  Overlooked aspects of COTS-based development , 2004, IEEE Software.

[14]  Matthias Jarke,et al.  Cooperative Information Systems: A Manifesto * , 1997 .

[15]  Christof Ebert,et al.  Best Practices in Software Measurement , 2004 .

[16]  Walker Royce.  Software Project Management , 1998 .

[17]  Roel Wieringa,et al.  Guest Editors' Introduction: RE'03-Practical Requirements Engineering Solutions , 2004, IEEE Softw..

[18]  Lisa Brownsword,et al.  Developing New Processes for COTS-Based Systems , 2000, IEEE Softw..

[19]  M. R. Strens,et al.  Change analysis: a step towards meeting the challenge of changing requirements , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[20]  Allen B. Tucker.  On the balance between theory and practice [software engineering curriculum] , 2002 .

[21]  Christof Ebert,et al.  The Top Risks of Requirements Engineering , 2001, IEEE Softw..

[22]  Anthony Finkelstein,et al.  Requirements stability assessment using scenarios , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[23]  Acm Sigsoft.  Proceedings : 11th IEEE International Requirements Engineering Conference, 8-12 September 2003, Monterey Bay, California, USA , 2003 .

[24]  Holger Doernemann.  Tool-based risk management made practical , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[25]  Alan M. Davis,et al.  Elicitation technique selection: how do experts do it? , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[26]  Pradeep Kumar Ray,et al.  RE’03: PRACTICAL REQUIREMENTS ENGINEERING SOLUTIONS Ongoing Requirements Discovery in High-Integrity Systems , 2004 .

[27]  Neil A. M. Maiden,et al.  Lessons learned during requirements acquisition for COTS systems , 1997, CACM.

[28]  Christof Ebert,et al.  Dealing with nonfunctional requirements in large software systems , 1997, Ann. Softw. Eng..

[29]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[30]  Patrick Donohoe,et al.  Feature-Oriented Project Line Engineering , 2002, IEEE Softw..

[31]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[32]  Søren Lauesen,et al.  Task Descriptions as Functional Requirements , 2003, IEEE Softw..

[33]  Barry W. Boehm,et al.  COTS-Based Systems Top 10 List , 2001, Computer.

[34]  Capers Jones,et al.  Software Assessments, Benchmarks, and Best Practices , 2000 .

[35]  Soren Lauesen,et al.  Software Requirements: Styles & Techniques , 2002 .