Advertisement

User Requirements Engineering and Management in Software Development

  • Zeljko Panian
Conference paper
Part of the Lecture Notes in Electrical Engineering book series (LNEE, volume 28)

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.

Keywords

Requirement Engineering Software Project Requirement Management Traceability Link Requirement Development 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

References

  1. 1.
    Bates J (2005) Business in real time – Realizing the vision. DM Review, 05/2003 (http://www.dmreview.com/)
  2. 2.
    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–885CrossRefGoogle Scholar
  3. 3.
    Boehm BW, Papaccio PN (1998) Understanding and controlling software costs. IEEE Tran Software Eng 14(10):1462–1476CrossRefGoogle Scholar
  4. 4.
    Davis AM (1993) Software requirements: Objects, functions, and states. Prentice Hall PTR, Upper Saddle River (NJ)MATHGoogle Scholar
  5. 5.
    Ellis K (2006) The executive briefing on the issues surrounding getting business requirements right. http://www.digital-mosaic.com, May 2
  6. 6.
    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
  7. 7.
    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–239Google Scholar
  8. 8.
    Hofmann HF, Lehner F (2001) Requirements engineering as a success factor in software projects. IEEE Software 18(4):58–66CrossRefGoogle Scholar
  9. 9.
    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–215Google Scholar
  10. 10.
    Leffingwell D (1997) Calculating the return on investment from more effective requirements management. Am Programmer 10(4):13–16Google Scholar
  11. 11.
    Light M (2005) Agile requirements definition and management will benefit application development. http://www.gartner.com, Apr. 18
  12. 12.
    The Standish Group Staff (2005) The CHAOS report on software design. The Standish Group, Palo Alto (CAL)Google Scholar

Copyright information

© Springer Science+Business Media, LLC 2009

Authors and Affiliations

  • Zeljko Panian
    • 1
  1. 1.Faculty of Economics and BusinessUniversity of ZagrebCroatia

Personalised recommendations