Abstract
This chapter presents a survey of the state of the art for quality assurance for requirements. The meaning of quality in the requirements context is discussed, as is the influence of the quality assurance during requirements on other parts of the development. Different quality assurance approaches are categorized as either constructive (e.g., standards, guidelines, elicitation techniques) or analytical (e.g., inspections) and discussed with respect to their impact on the requirements quality. Based on the approaches, future challenges are discussed. The main future challenges lie in investigating the return on investment of quality assurance in the requirements context and to provide more empirical results which approach that effectively prevent or detect which problems.
Access provided by Autonomous University of Puebla. Download to read the full chapter text
Chapter PDF
Similar content being viewed by others
Keywords
References
Ahlowalia N (2002) Testing from use cases using path analysis technique. In: Proceedings of the International Conference on Software Testing, Analysis & Review, Anaheim, CA, USA
Anda B, Sjøberg D I K (2002) Towards an inspection technique for UC models. In: Proceedings of the 14th International Conference on Software Engineering and Knowledge Engineering (SEKE), Italy, pp 127–134
Aurum A, Petersson H, Wohlin C (2002) State-of-the-Art: Software Inspections Turning 25 Years. Journal on Software Testing, Verification and Reliability 12(3): 133–154
Basili V R, Green S, Laitenberger O, Lanubile F, Shull F, Sorumgard S, Zelkowitz M (1996) The empirical investigation of perspective-based reading. Empirical Software Engineering 1(2): 133–164
Beck K (1999) Extreme programming explained. Boston: Addison-Wesley
Binder RV (1999) Testing object-oriented systems: Patterns, models and tools. Boston: Addison-Wesley Object Technologies Series
Briand L, Freimut B, Vollei F, (2000) Assessing the cost-effectiveness of inspections by combining project data and expert opinion. In: Proceedings of the 11th International Symposium on Software Reliability Engineering, pp.124–135
Bittner K, Spence I (2003) Use case modeling. Boston: Addison-Wesley
Boehm BW, Gray TE (1984) Prototyping versus specifying: A multi-project experiment. IEEE Transaction on Software Engineering 10(3):290–302
Boehm BW, Basili VR (2001) Software defect reduction top 10 list. IEEE Computer 34(1):135–137
Cockburn, A (2001) Writing effective use cases. Boston: Addison-Wesley
Collard R (1999) Test design: Developing test cases from use cases. Software Testing and Quality Engineering July/August 1(4): 31–36
Denger C, Paech B (2004) An integrated quality assurance approach for use case based requirements. In: Proceedings of the German conference of Modellierung, pp.59–74
Denger C, Paech B, Benz S (2003) Guidelines — Creating use cases for embedded systems. IESE-Report, 078.03/E, Kaiserslautern, Germany
Denger C, Medina M (2003) Test cases derived from user requirements specifications: Literature survey. IESE Report No. 033.03/E, Kaiserslautern, Germany
Denger C, Kerkow D, Knethen Av, Paech B (2003) A comprehensive approach for creating high-quality requirements and specifications in automotive projects. In: Proceedings of the International Conference Software and Systems Engineering and their Applications, 2–6 December, Paris, France
Endres A, Rombach H D (2003) A handbook of software and systems engineering. Empirical Observations, Laws and Theories. New York: Addison-Wesley
Fagan ME, (1976) Design and code inspections to reduce errors in program development. IBM Systems Journal 15(3):182–211
Fantechi A, Gnesi S, Lami G, Maccari A (2002) Application of linguistic techniques for use case analysis. In: Proceedings of the International Conference on Requirements Engineering, pp 157–164, Essen, Germany
Gilb T, Graham D (1993) Software inspection. Boston, Addison-Wesley
Glass RL (1998) Software runaways. Lessons learned from massive software project failures. Upper Saddle River, NJ: Prentice Hall
Graham D (2002) Requirements and testing: Seven missing-link myths. IEEE Software 19(9):15–17
Heitmeyer CL, Jeffords RD, Labaw BG, (1996) Automated consistency checking of requirements specifications. ACM Transactions on Software Engineering and Methodology 5(3): 231–261
IEEE Recommended practice for software requirements specification. IEEE Standard 830–1998, 1998
IEEE guide for developing system requirements specification. IEEE Standard 1233–1998, 1998
IEEE standard for software reviews. IEEE Standard 1028–1997, 1997
ITU-T (1993) Recommendation Z.100. Specification and description language (SDL) ITU-International Communication Unit, Geneva
Jalote P (1989) Testing of completeness of specifications. IEEE Transactions on Software Engineering 15(5): 526–531
Jones CB, (1990) Systematic software development using VDM. Upper Saddle River, NJ, Prentice Hall
Kamsties E, Pohl K, Reis S, Reuys A (2004) Szenario-basiertes systemtesten von software-produktfamilien mit ScenTED. In: Proceedings of Modellierung, Marburg, Germany, pp.169–186
Keese P, Meyerhoff D (2003) Tutorial on requirements-based testing (SQS). Held in conjunction of the International Conference on Software Testing, Cologne, Germany
Kitchenham B, Pfleeger S (1996) Software quality: the elusive target. IEEE Software, 13(1): 12–21
Le Lann G (1996) The Ariane 5 Flight 501 Failure-A case study in system engineering for computing systems. Research report RR-3079, INRIA
Laitenberger O (2000) Cost-effective detection of software defects through perspective-based inspections. PhD Thesis in Experimental Software Engineering; Fraunhofer IRB Verlag
Leffingwell D, Widrig D (2000) Managing software requirements — A unified approach. Boston: Addison-Wesley
Liggesmeyer P (1990), Modultest und modulverifikation — State of the art. Mannheim, Wien Zürich, BI-Wissesverlag
Briand LC, Freimut B, Vollei F (2000) Assessing the cost-effectiveness of inspections by combining project data and expert opinion. In: Proceedings of the 11th International Symposium on Software Reliability Engineering, pp 124–135
Musa J (1993) Operational profiles in software-reliability engineering. IEEE Software 10:(2): 14–32
Ostraned T J, Balcer M J (1988) The category-partition method for specifying and generating functional tests. Communications of the ACM 31(6):676–686
Porter A, Votta LG (1998) Comparing detection methods for software requirements specification: A replication using professional subjects. Empirical Software Engineering 3(4): 355–379
Robertson S, Robertson JH (1999) Mastering the requirements process. Boston: Addison-Wesley
Rupp C, Queins S (2003) Vom use-case zum Test-Case. OBJEKTspektrum, Vol.4
Shull F, Rus I, Basili V (2000) How perspective-based reading can improve requirements inspections. IEEE Computer 33(7):73–79
Shull F, Basili V, Boehm B, Brown AW, Costa P, Lindvall M, Port D, Rus I, Tesoriero R, Zelkowitz M (2002) What we have learned about fighting defects. In: Proceedings of 8th International Metrics Software Metrics Symposium: p 249ff., Ottawa, Canada
Shull F, Travassos G H, Carver J (1999) Evolving a set of techniques for OO inspections. Technical Report CS-TR-4070, UMIACS-TR-99-63; University of Maryland
Sommerville I, Sawyer P (1997) Requirements engineering. A good practice guide. Chichester: John Wiley & Sons
http://www.standishgroup.com/chaos_chronicles/index.php Accessed on 3rd December 2004
Thelin T, Runeson P, Wohlin C (2003) An experimental comparison of usage-based reading and checklist-based reading. IEEE Transactions on Software Engineering, 29(8): 687–704
Wiegers K E (2002) Peer reviews in software. A practical guide. Boston: Addison-Wesley
Wiegers K E (1999) Writing quality requirements. Software Development Magazine, 7(5): 44–48
Wiegers K E (2000) Karl Wiegers describes 10 requirements traps to avoid. Software Testing & Quality Engineering Journal, January/February, 2(1)
Wilson WM, Rosenberg LH, Hyatt LE (1996) Automated quality analysis of natural language requirements specifications. NASA Software Assurance Technology Center, USA
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2005 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Denger, C., Olsson, T. (2005). Quality Assurance in Requirements Engineering. In: Aurum, A., Wohlin, C. (eds) Engineering and Managing Software Requirements. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-28244-0_8
Download citation
DOI: https://doi.org/10.1007/3-540-28244-0_8
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)