Extreme Requirements Engineering

by Larry Wagner

Requirements engineering is the most critical activity for a software project to ensure delivery of a product that meets the needs of the customer. Poorly done requirements can lead to myriad problems in the development cycle, such as software that is over budget, delivered late, or of poor quality. Incomplete requirements and changing requirements are often major contributors to these problems [3]. Debates rage on today over agile software development versus rigorous software development. Some would accuse the agile side of a "full speed ahead, no matter the consequences" attitude -- expediency at whatever the cost. Others would say of the rigorous side, "You will complete this 700-pound requirements specification, no matter if the client no longer needs the software by the time it is ready" -- process at whatever the price.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.
Extreme Requirements Engineering December 2001