Abstract
We are interested in the relationship between the quality of the requirements specifications for software projects and the subsequent outcome of the projects. To examine this relationship, we investigated 32 projects started and completed between 2003 and 2005 by the software development division of a large company in Tokyo. The company has collected reliable data on requirements specification quality, as evaluated by software quality assurance teams, and overall project performance data relating to cost and time overruns. The data for requirements specification quality were first converted into a multiple-dimensional space, with each dimension corresponding to an item of the recommended structure for software requirements specifications (SRS) defined in IEEE Std. 830-1998. We applied various statistical analysis methods to the SRS quality data and project outcomes.
The results showed some interesting relationships between the quality of the requirements and the success or failure of projects; for example, (1) a relatively small set of SRS items had a strong impact on whether a project succeeded or failed; (2) descriptions of SRS in normal projects tended to be balanced; (3) SRS descriptions in Section 1, which were expected to include the purpose, overview and general context for SRS, were comprehensive for normal projects but inadequate for projects that finished with overruns; and (4) when the descriptions of SRS in Section 1 were inadequate, while those of the expected functions and product perspective were comprehensive, the project tended to end up with cost overruns.
Keywords
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
Berry, D., Damian, D., Finkelstein, A., Gause, D., Hall, R., Simmons, E., Wassyng, A.: To do or not to do: If the requirements engineering payoff is so good, why aren’t more companies doing it? In: Proc. 13th International Requirements Engineering Conference (RE 2005), p. 447. IEEE, Los Alamitos (2005)
Standish Group International: The chaos report (1994), http://www.standishgroup.com/sample_research/chaos_1994_1.php
Glass, R.L.: The standish report: Does it really describe a software crisis? Communications of the ACM 49, 15–16 (2006)
Jorgensen, M., Molokken-Ostvold, K.: How large are software cost overruns? A review of the 1994 chaos report. Information and Software Technology 48, 297–301 (1997)
IEEE: Recommended practice for software requirements specifications. Technical report, IEEE, IEEE Std 830-1998 (1998)
Breiman, L., Friedman, J.H., Ohshen, R.A., Stone, C.J.: Classification and Regression Trees. Wadsworth, Belmont (1984)
The R Foundation for Statistical Computing: The R project for statistical computing, http://www.r-project.org/index.html
Damian, D., Chisan, J.: An emipirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management. IEEE Transactions on Software Engineering 32, 433–453 (2006)
Wohlwend, H., Rosenbaum, S.: Software improvements in an international company. In: 15th International Conference on Software Engineering (ICSE 1993), Baltimore, MD, USA (1993)
Sommerville, I., Ransom, J.: An empirical study of industrial requirements engineering process assessment and improvement. ACM Transactions on Software Engineering and Methodology 14, 85–117 (2005)
Verner, J., Cox, K., Bleistein, S., Cerpa, N.: Requirements engineering and software project success: An industrial survey in Australia and the U.S. Australian Journal of Information Systems 13, 225–238 (2005)
Emam, K.E., Madhavji, N.H.: Measuring the success of requirements engineering processes. In: Second IEEE International Symposium on Requirements Engineering, pp. 204–211 (1995)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Tamai, T., Kamata, M.I. (2009). Impact of Requirements Quality on Project Success or Failure. In: Lyytinen, K., Loucopoulos, P., Mylopoulos, J., Robinson, B. (eds) Design Requirements Engineering: A Ten-Year Perspective. Lecture Notes in Business Information Processing, vol 14. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-92966-6_15
Download citation
DOI: https://doi.org/10.1007/978-3-540-92966-6_15
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-92965-9
Online ISBN: 978-3-540-92966-6
eBook Packages: Computer ScienceComputer Science (R0)