Skip to main content

Advertisement

Springer Nature Link
Log in

Good requirements practices are neither necessary nor sufficient

  • Viewpoints
  • Published:
Requirements Engineering Aims and scope Submit manuscript

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

Access this article

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2

Notes

  1. We are deliberately ignoring whether this means, “that only good practices were employed,” or “that all the good practices applicable to this project were employed,” as highlighted in the previous paragraph.

  2. We could also use the word “hole” here, but we won’t go there!

References

  1. Davis A (2004) Just enough requirements management. Dorset House, New York

  2. Gause D, Weinberg J (1989) Exploring requirements: quality before design. Dorset House, New York

    Google Scholar 

  3. Glass R (2002) Searching for the Holy Grail of software engineering. Commun ACM 45(5):15–16. DOI: 10.1145/506218.506231

    Google Scholar 

  4. Gottesdiener E (2002) Requirements by collaboration: workshops for defining needs. Addison Wesley, Reading

    Google Scholar 

  5. Hickey A, Davis A (2004) A unified model of requirements elicitation. J Manag Inf Syst 20(4):65–84

    Google Scholar 

  6. IEEE Standard 830 (1998) IEEE recommended practice for software requirements specifications. IEEE Computer Society Press, Los Alamitos

  7. Laueson S (2002) Software requirements: styles and techniques. Addison Wesley, Reading

    Google Scholar 

  8. Leffingwell D, Widrig D (1999) Managing software requirements—a unified approach. Addison Wesley, New York

  9. Robertson J, Robertson S (1999) Mastering the requirements process. Addison Wesley, New York

  10. Sommerville I, Sawyer P (1997) Requirements engineering: a good practice guide. Wiley, New York

    Google Scholar 

  11. Wiegers K (2003) Software requirements. Microsoft Press, Redmond

  12. Young R (2001) Effective requirements practices. Addison Wesley, Reading

Download references

Author information

Authors and Affiliations

  1. Department of Information Systems, College of Business, The University of Colorado at Colorado Springs, 1420 Austin Bluffs Parkway, PO Box 7150, Colorado Springs, CO, 80933-7150, USA

    Alan M. Davis

  2. Department of Software Engineering, Faculty of Information Technology, University of Technology, Sydney, P O Box 123, Broadway, Sydney, NSW, 2007, Australia

    Didar Zowghi

Authors
  1. Alan M. Davis
    View author publications

    You can also search for this author inPubMed Google Scholar

  2. Didar Zowghi
    View author publications

    You can also search for this author inPubMed Google Scholar

Corresponding author

Correspondence to Alan M. Davis.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Davis, A.M., Zowghi, D. Good requirements practices are neither necessary nor sufficient. Requirements Eng 11, 1–3 (2006). https://doi.org/10.1007/s00766-004-0206-4

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-004-0206-4

Keywords