How does requirements quality relate to project success or failure?

Proceedings - 15th IEEE International Requirements Engineering Conference, RE 2007

Volumn , Issue , 2007, Pages 69-78

  Kamata, Mayumi Itakura ^a   Tamai, Tetsuo ^b  

^a IBM RESEARCH   (United States)

^b UNIVERSITY OF TOKYO   (Japan)

Author keywords

[No Author keywords available]

Indexed keywords

COST OVERRUNS; DIMENSIONAL SPACES; LARGE BUSINESSES; PROJECT OUTCOMES; PROJECT PERFORMANCES; PROJECT SUCCESSES; QUALITY DATUMS; REQUIREMENTS SPECIFICATIONS; RESEARCH GOALS; SOFTWARE QUALITY ASSURANCES; SOFTWARE REQUIREMENTS SPECIFICATIONS; STATISTICAL ANALYSIS TECHNIQUES; TIME OVERRUNS;

COMPUTER SOFTWARE SELECTION AND EVALUATION; INTERACTIVE COMPUTER SYSTEMS; PROJECT MANAGEMENT; QUALITY ASSURANCE; REQUIREMENTS ENGINEERING; SAFETY ENGINEERING; SPECIFICATIONS; STIMULATED RAMAN SCATTERING; TOTAL QUALITY MANAGEMENT;

QUALITY CONTROL;

EID: 47949121308     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/RE.2007.33     Document Type: Conference Paper

References (12)

1. D. Berry, D. Damian, A. Finkelstein, D. Gause, R. Hall, E. Simmons, and A. Wassyng. 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'05), page 447. IEEE, 2005.
2. L. Breiman, J. H. Friedman, R. A. Ohshen, and C. J. Stone. Classification and Regression Trees. Wadsworth, Belmont, CA, 1984.
3. D. Damian and J. Chisan. 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(7):433-453, July 2006.
4. K. E. Emam and N. H. Madhavji. Measuring the success of requirements engineering processes. In Second IEEE International Symposium on Requirements Engineering, pages 204-211, 1995.
5. R. L. Glass. The standish report: Does it really describe a software crisis? Communications of the ACM, 49(8):15-16, Aug. 2006.
6. IEEE. Recommended practice for software requirements specifications. Technical report, IEEE, 1998. IEEE Std 830-1998.
7. M. Jorgensen and K. Molokken-Ostvold. How large are software cost overruns? A review of the 1994 chaos report. Information and Software Technology, 48(4):297-301, Apr. 1997.
8. I. Sommerville and J. Ransom. An empirical study of industrial requirements engineering process assessment and improvement. ACM Transactions on Software Engineering and Methodology, 14(1):85-117, Jan. 2005.
9. Standish Group International. The chaos report (1994). http://www.standishgroup.com/sample-research/ chaos_1994_1.php, 1994.
10. The R Foundation for Statistical Computing. The R project for statistical computing. http://www.r-project.org/index.html.
11. J. Vemer, K. Cox, S. Bleistein, and N. Cerpa. Requirements engineering and software project success: An industrial survey in Australia and the U.S. 13:225-238, 2005.
12. H. Wohl wend and S. Rosenbaum. Software improvements in an international company. In 15th International Conference on Software Engineerig (ICSE'93), Baltimore, MD, USA, 1993.