Requirements Evolution from Process to Product Oriented Management

Requirements Evolution represents one of the major problems in developing computer-based systems. Current practice in Requirement Engineering relies on process-oriented methodologies, which lack of product features. The resulting scenario then is a collection of general methodologies, which do not take into account product features that may enhance our ability in monitoring and controlling Requirements Evolution. This paper shows empirical investigations of two industrial case studies. The results point out evolutionary product features and identify an Empirical Framework to analysing Requirements Evolution. This work represents a shift from process to product-oriented management of Requirements Evolution.

[1]  Hoyt Lougee,et al.  SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION , 2001 .

[2]  M. R. Strens,et al.  Meeting the Challenge of Changing Requirements , 1996, SSS.

[3]  Stuart Anderson,et al.  Requirements Changes Risk/Cost Analyses: An Avionics Case Study , 2000 .

[4]  David M. Weiss,et al.  Software Product-Line Engineering: A Family-Based Software Development Process , 1999 .

[5]  Stuart Anderson,et al.  Controlling Requirements Evolution: An Avionics Case Study , 2000, SAFECOMP.

[6]  Jessica Keyes,et al.  IEEE Standard Dictionary of Measures to Produce Reliable Software , 2002 .

[7]  Lawrence D. Pohlmann,et al.  Customer‐Centered Products – Creating Successful Products through Smart Requirements Management , 2001 .

[8]  Peter J. Middleton,et al.  Software Inspection , 1994, J. Inf. Technol..

[9]  Kristin A. Farry,et al.  Customer Centered Products: Creating Successful Products Through Smart Requirements Management (Продукты для клиента: создание успешных продуктов с помощью грамотного управления требованиями) , 2000 .

[10]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[11]  George Stark An Examination of the Effects of Requirements Changes on Software Releases , 1998 .

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

[13]  Meir M. Lehman,et al.  Software's future: managing evolution , 1998, IEEE Software.

[14]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[15]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[16]  Peter Neumann,et al.  Safeware: System Safety and Computers , 1995, SOEN.

[17]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[18]  Neil R. Storey,et al.  Safety-critical computer systems , 1996 .

[19]  George E. Stark,et al.  An examination of the effects of requirements changes on software maintenance releases , 1999 .

[20]  Suzanne Garcia,et al.  Key Practices of the Capability Maturity Model, Version 1.1 , 1993 .

[21]  Linda H. Rosenberg,et al.  Doing Requirements Right the First Time , 1998 .