What’s Wrong with Requirements Specification? An Analysis of the Fundamental Failings of Conventional Thinking about Software Requirements, and Some Suggestions for Getting it Right
Tom Gilb
.
DOI: 10.4236/jsea.2010.39096   PDF   HTML     6,127 Downloads   11,671 Views   Citations

Abstract

We know many of our IT projects fail and disappoint. The poor state of requirements methods and practice is frequently stated as a factor for IT project failure. In this paper, I discuss what I believe is the fundamental cause: we think like programmers, not engineers and managers. We do not concentrate on value delivery, but instead on functions, on use-cases and on code delivery. Further, management is not taking its responsibility to make things better. In this paper, ten practical key principles are proposed, which aim to improve the quality of requirements specification.

Share and Cite:

T. Gilb, "What’s Wrong with Requirements Specification? An Analysis of the Fundamental Failings of Conventional Thinking about Software Requirements, and Some Suggestions for Getting it Right," Journal of Software Engineering and Applications, Vol. 3 No. 9, 2010, pp. 827-838. doi: 10.4236/jsea.2010.39096.

Conflicts of Interest

The authors declare no conflicts of interest.

References

[1] T. Gilb, “Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage,” Elsevier Butterworth-Heinemann, Boston, 2005.
[2] B. V. Koen, “Discussion of the Method: Conducting the Engineer’s Approach to Problem Solving,” Oxford University Press, Oxford, 2003.
[3] L. Kelvin, “Electrical Units of Measurement,” a Lecture Given on 3 May 1883, Published in the Book “Popular Lectures and Addresses, Volume 1,” 1891.
[4] T. Gilb, “Principles of Software Engineering Management,” Addison-Wesley, Boston, 1988.
[5] Z. Yanga, S. Caib, Z. Zhouc and N. Zhoua, “Development and Validation of an Instrument to Measure User Perceived Service Quality of Information Presenting Web Portals,” Information & Management, Vol. 42, No. 4, 2005, pp. 575-589.
[6] T. Gilb, “Real Requirements”. http://www.gilb.com/tiki- download_file.php?fileId =28
[7] T. Ohno, “Toyota Production System: Beyond Large- Scale Production,” Productivity Press, New York, 1988.
[8] T. Johansen and T. Gilb, “From Waterfall to Evolutionary Development (Evo): How we Created Faster, More User-Friendly, More Productive Software Products for a Multi-National Market,” Proceedings of INCOSE, Rochester, 2005. http://www.gilb.com/tiki-download_file.php? fileId=32
[9] T. Gilb, “Rich Requirement Specs: The Use of Planguage to Clarify Requirements”. http://www.gilb.com/tiki-down- load_file.php?fileId=44
[10] T. Gilb, “Agile Specification Quality Control, Testing Experience,” March 2009. www.testingexperience.com/ testingexperience01_08.pdf
[11] K. Hopper and W. Hopper, “The Puritan Gift,” I. B. Taurus and Co. Ltd., London, 2007.
[12] “Top Level Objectives: A Slide Collection of Case Studies”. http://www.gilb.com/tiki-download_file.php?fileId= 180
[13] “Profile: BP’s Tony Hayward, BBC Website: News US and Canada,” 27 July 2010. http://www.bbc.co.uk/news/ world-us-canada-10754710

Copyright © 2021 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.