Abstract
Requirements engineering is an often underutilized discipline in software development. Yet the economic benefits – lowered development costs, faster development and better products that delight customers – have plainly been demonstrated in study after study. In this paper, the case is made for requirements engineering as an integral part of any product lifecycle. Metrics are provided to show the positive effect of requirements engineering and requirements management (RM), from individual developers to the business to the customer. A software product is examined as an example of how to bring effective requirements management into product development.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Bates J (2005) Business in real time – Realizing the vision. DM Review, 05/2003 (http://www.dmreview.com/)
Blackburn JD, Scudder GD, Van Wassenhove LN (1996) Improving speed and productivity of software development: A global survey of software developers. IEEE Trans Software Eng 22(12):875–885
Boehm BW, Papaccio PN (1998) Understanding and controlling software costs. IEEE Tran Software Eng 14(10):1462–1476
Davis AM (1993) Software requirements: Objects, functions, and states. Prentice Hall PTR, Upper Saddle River (NJ)
Ellis K (2006) The executive briefing on the issues surrounding getting business requirements right. http://www.digital-mosaic.com, May 2
Frankl A, King T (2005) How to detect requirements errors – A guide to slashing software costs and shortening development time. http://www. n8systems.com, July 22
Grady RB (1999) An economic release decision model: insights into software project management. In: Proceedings of the Applications of Software Measurement Conference, Orange Park FL, pp 227–239
Hofmann HF, Lehner F (2001) Requirements engineering as a success factor in software projects. IEEE Software 18(4):58–66
Hooks IF, Farry KA (2001) Customer-centered products: creating successful products through smart requirements management. In: Proceedings of the AMACOM Conference, Miami FL, pp 207–215
Leffingwell D (1997) Calculating the return on investment from more effective requirements management. Am Programmer 10(4):13–16
Light M (2005) Agile requirements definition and management will benefit application development. http://www.gartner.com, Apr. 18
The Standish Group Staff (2005) The CHAOS report on software design. The Standish Group, Palo Alto (CAL)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer Science+Business Media, LLC
About this paper
Cite this paper
Panian, Z. (2009). User Requirements Engineering and Management in Software Development. In: Mastorakis, N., Mladenov, V., Kontargyri, V. (eds) Proceedings of the European Computing Conference. Lecture Notes in Electrical Engineering, vol 28. Springer, Boston, MA. https://doi.org/10.1007/978-0-387-85437-3_63
Download citation
DOI: https://doi.org/10.1007/978-0-387-85437-3_63
Published:
Publisher Name: Springer, Boston, MA
Print ISBN: 978-0-387-84818-1
Online ISBN: 978-0-387-85437-3
eBook Packages: EngineeringEngineering (R0)