Skip to main content
SpringerLink
Log in
Book cover

Engineering and Managing Software Requirements pp 1–15Cite as

Requirements Engineering: Setting the Context

  • Chapter

Abstract

This chapter presents a brief overview of requirements engineering and provides an introduction to some of the critical aspects of this field. This includes offering and understanding of the different levels of requirements involved in requirements engineering, namely organizational, product and project level requirements, and illustrating the role of different stakeholders in requirements engineering. The chapter also aims to demonstrate how the three parts of this book are interrelated.

This is a preview of subscription content, log in via an institution.

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   129.00
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   169.00
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   169.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Anthony RN (1965) Planning and control systems: a framework for analysis. Harvard University, Boston, USA

    Google Scholar 

  2. Aurum A, Wohlin C (2003) The fundamental nature of requirements engineering activities as decision making process. Journal on Information and Software Technology, 45(14): 945–954

    Google Scholar 

  3. Babbie E (1990) Survey research methods. Wadsworth, ISBN 0-524-12672-3

    Google Scholar 

  4. Berry DM, Lawrence B (1998) Requirements engineering. IEEE Software 25(2): 26–29

    Google Scholar 

  5. Boehm BW, (1988) A spiral model of software development and enhancement, Computer, May, 21(5): 61–72

    Article  Google Scholar 

  6. Boehm BW, Papaccio, PN (1988) Understanding and controlling software costs. IEEE transactions on software engineering, 14(10): 1462–1477

    Article  Google Scholar 

  7. Boehm BW, Grünbacher P, Brigges RO (2001) Developing groupware for requirements negotiation: lessons learned. IEEE, Software, May/June, pp. 46–55

    Google Scholar 

  8. Boehm BW (2003) Value-based software engineering. ACM SIGSOFT, Software engineering notes, March, 28(2): 1–12

    Google Scholar 

  9. BSC’04 (2004) The challenges of complex IT projects. The report of a working group from the Royal academy of engineering and the British computer society. ISBN 1-903496-15-2. Access on 20th October 2004. http://www.bcs.org/BCS/News/PositionsAndResponses/Positions/complexity.htm

    Google Scholar 

  10. Chaos’94 (1995) The Standish group. Access on 4th October 2004. http://standishgroup.com/sample_research/

    Google Scholar 

  11. Chaos’98 (1999) A recipe for success. The Standish group report. Access on 4th October 2004 http://www.standishgroup.com/sample_research

    Google Scholar 

  12. Chao’01 (2002) Extreme chaos. The Standish group report. Accessed on 4th October 2004 http://www.standishgroup.com/sample_research

    Google Scholar 

  13. Chatzoglou PD (1997) Factors affecting completion of the requirements capture stage of projects with different characteristics. Information and Software Technology, 39(9): 627–640

    Article  Google Scholar 

  14. Curtis B, Krasner H, Iscoe N (1988) A field study of the software design process for large systems. Communications of the ACM 31(11):1268–1287

    Article  Google Scholar 

  15. Davis A (1990) System testing: Implications of requirements specifications. Information and Software Technology, 32(6): 407–414

    Article  Google Scholar 

  16. Edwards J, Coutts I, McLeod S (2000) Support for system evolution through separating business and technology issues in a banking system. In: Proceedings of international conference on software Maintenance, 11–14 October, pp. 271–276

    Google Scholar 

  17. El Emam K, Madhavji NH (1995) A field study of requirements engineering practices in information systems development. In: Proceedings of 2nd international symposium on requirements engineering, York, England, IEEE CS Press, pp.68–80

    Google Scholar 

  18. European Software Institute (1996) European user survey analysis. Report USV_EUR 2.1, ESPITI project, January

    Google Scholar 

  19. Faulk SR, Harmon RR, Raffo DM (2000) Value-base software engineering: A value-driven approach to product-line engineering. In: Proceedings of 1st international conference on software product-line engineering, Colorado, August 28, 2000

    Google Scholar 

  20. Hall T, Beecham S, Rainer A (2002) Requirements problems in twelve companies: an empirical analysis. IEE proceedings software, 149(5): 153–160

    Google Scholar 

  21. Hofmann HF, Lehner F (2001) Requirements engineering as a success factor in software projects. IEEE Software, 18(4): 58–66

    Article  Google Scholar 

  22. Houdek F, Pohl K (2000): Analyzing requirements engineering processes: a case study. In: Proceedings of the 11th international workshop on database and expert systems applications, Greenwich, UK, 6–8 September, pp.983–987

    Google Scholar 

  23. Hunter A, Nuseibeh B (1997) Analyzing inconsistent specifications. In: Proceedings of 3rd international symposium on requirements engineering, RE’07, Annapolis, Md, pp.78–86

    Google Scholar 

  24. IEEE-STD 610.12-1990, Standard Glossary of Software Engineering Terminology, 1990, Institute of Electrical and Electronics Engineers

    Google Scholar 

  25. Kotonya G, Sommerville I (1998) Requirements engineering — processes and techniques, John Wiley & Sons UK

    Google Scholar 

  26. Lauesen, S (2002) Software requirements: styles and techniques, Addison-Wesley, London, UK

    Google Scholar 

  27. Loucopoulos P, Karakostas V (1995): System requirements engineering. McGraw-Hill Book company Europe

    Google Scholar 

  28. Lowe D, Eklund J (2001) Development issues in specification of web systems. In: Proceedings of 6th Australian workshop on requirements engineering, 22–23 November, University of New South Wales, Sydney, Australia, pp. 4–13

    Google Scholar 

  29. Lubars M, Potts C, Richter C (1993) A review of the state of the practice in requirements modelling. In: Proceedings of the IEEE international symposium on requirements engineering, IEEE Computer Society, San Diego, USA, pp. 2–14

    Google Scholar 

  30. Macaulay LA (1996) Requirements engineering. Springer-Verlag, New York, London

    Google Scholar 

  31. Madhavji NH, Holtje D, Hong W, Bruckhaus T (1994) Elicit: a method for eliciting process models. In: Proceedings of CAS conference, Toronto, Canada, 31 October–3 November, pp.11–122

    Google Scholar 

  32. Martin S, Aurum A, Jeffery R, Paech B (2002) Requirements engineering process models in practice. In: Proceedings of 7th Australian workshop on requirements engineering, AWRE’02, 2–3 December, Melbourne, pp. 41–47

    Google Scholar 

  33. Menzies T, Easterbrook S, Nuseibeh B, Waugh S (1999) An empirical investigation of multiple viewpoint reasoning in requirements engineering. In: Proceedings of IEEE international symposium on requirements engineering, 7–11 June, pp.100–109

    Google Scholar 

  34. Miller E (2002) For survival, start thinking lifecycle management. Computer-aided engineering, 21(1): 15–18

    MATH  Google Scholar 

  35. Nguyen L, Swatman P (2003) Managing the requirements engineering process. Requirements engineering, 8(1): 55–68

    Article  Google Scholar 

  36. Pouloudi A, Whitley EA (1997) Stakeholder identification in inter-organizational systems: Gaining insights for drug use management systems. European journal of information systems, 6: 1–14

    Article  Google Scholar 

  37. Sommerville I (2001) Software engineering. Pearson Education Ltd, UK

    Google Scholar 

  38. Tveito A, Hasvold P (2002) Requirements in the medical domain: Experiences and prescriptions. IEEE Software, Nov–Dec, pp.66–69

    Google Scholar 

  39. van Lamsweerde A (2000) Requirements engineering in the year 00: a research perspective. In: Proceedings of 22nd International conference on software engineering, pp.5–19

    Google Scholar 

  40. Wohlin C, Runeson P, Höst M, Ohlsson MC, Regnell B, Wesslén A (2000) Experimentation in software engineering — An introduction. Kluwer Academic Publishers, Boston, MA, USA

    Google Scholar 

  41. Yin RK (1994) Case study research design and methods. Sage Publications, Beverly Hills, California, USA

    Google Scholar 

Download references

Authors
  1. Aybüke Aurum
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Claes Wohlin
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. School of Information Systems, Technology and Management, University of New South Wales, Sydney, NSW, 2052, Australia

    Aybüke Aurum

  2. School of Engineering, Blekinge Institute of Technology, Box 520, 372 25, Ronneby, Sweden

    Claes Wohlin

Rights and permissions

Reprints and permissions

Copyright information

© 2005 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Aurum, A., Wohlin, C. (2005). Requirements Engineering: Setting the Context. In: Aurum, A., Wohlin, C. (eds) Engineering and Managing Software Requirements. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-28244-0_1

Download citation

  • DOI: https://doi.org/10.1007/3-540-28244-0_1

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-25043-2

  • Online ISBN: 978-3-540-28244-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation