Quality assurance in requirements engineering

Engineering and Managing Software Requirements

Volumn , Issue , 2005, Pages 163-185

  Denger, Christian ^a   Olsson, Thomas ^a  

^a FRAUNHOFER IESE   (Germany)

Author keywords

Analytical approaches; Constructive approaches; Inspections; Quality assurance; Quality characteristics; Requirements

Indexed keywords

EID: 84895274479     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-28244-0_8     Document Type: Chapter

References (52)

1. 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.
2. 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.
3. 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.
4. 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.
5. Beck K (1999) Extreme programming explained. Boston: Addison-Wesley.
6. Binder RV (1999) Testing object-oriented systems: Patterns, models and tools. Boston: Addison-Wesley Object Technologies Series.
7. 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.
8. Bittner K, Spence I (2003) Use case modeling. Boston: Addison-Wesley.
9. Boehm BW, Gray TE (1984) Prototyping versus specifying: A multi-project experiment. IEEE Transaction on Software Engineering 10(3):290-302.
10. Boehm BW, Basili VR (2001) Software defect reduction top 10 list. IEEE Computer 34(1):135-137.
11. Cockburn, A (2001) Writing effective use cases. Boston: Addison-Wesley.
12. Collard R (1999) Test design: Developing test cases from use cases. Software Testing and Quality Engineering July/August 1(4): 31-36.
13. 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.
14. Denger C, Paech B, Benz S (2003) Guidelines - Creating use cases for embedded systems. IESE-Report, 078.03/E, Kaiserslautern, Germany.
15. Denger C, Medina M (2003) Test cases derived from user requirements specifications: Literature survey. IESE Report No. 033.03/E, Kaiserslautern, Germany.
16. 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.
17. Endres A, Rombach H D (2003) A handbook of software and systems engineering. Empirical Observations, Laws and Theories. New York: Addison-Wesley.
18. Fagan ME, (1976) Design and code inspections to reduce errors in program development. IBM Systems Journal 15(3):182-211.
19. 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.
20. Gilb T, Graham D (1993) Software inspection. Boston, Addison-Wesley.
21. Glass RL (1998) Software runaways. Lessons learned from massive software project failures. Upper Saddle River, NJ: Prentice Hall.
22. Graham D (2002) Requirements and testing: Seven missing-link myths. IEEE Software 19(9):15-17.
23. Heitmeyer CL, Jeffords RD, Labaw BG, (1996) Automated consistency checking of requirements specifications. ACM Transactions on Software Engineering and Methodology 5(3): 231-261.
24. IEEE Recommended practice for software requirements specification. IEEE Standard 830-1998, 1998.
25. IEEE guide for developing system requirements specification. IEEE Standard 1233- 1998, 1998.
26. IEEE standard for software reviews. IEEE Standard 1028-1997, 1997.
27. ITU-T (1993) Recommendation Z.100. Specification and description language (SDL) ITU-International Communication Unit, Geneva.
28. Jalote P (1989) Testing of completeness of specifications. IEEE Transactions on Software Engineering 15(5): 526-531.
29. Jones CB, (1990) Systematic software development using VDM. Upper Saddle River, NJ, Prentice Hall.
30. 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.
31. Keese P, Meyerhoff D (2003) Tutorial on requirements-based testing (SQS). Held in conjunction of the International Conference on Software Testing, Cologne, Germany.
32. Kitchenham B, Pfleeger S (1996) Software quality: the elusive target. IEEE Software, 13(1): 12-21.
33. Le Lann G (1996) The Ariane 5 Flight 501 Failure - A case study in system engineering for computing systems. Research report RR-3079, INRIA.
34. Laitenberger O (2000) Cost-effective detection of software defects through perspectivebased inspections. PhD Thesis in Experimental Software Engineering; Fraunhofer IRB Verlag.
35. Leffingwell D, Widrig D (2000) Managing software requirements - A unified approach. Boston: Addison-Wesley.
36. Liggesmeyer P (1990), Modultest und modulverifikation - State of the art. Mannheim, Wien Zürich, BI-Wissesverlag.
37. 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.
38. Musa J (1993) Operational profiles in software-reliability engineering. IEEE Software 10:(2): 14-32.
39. 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.
40. Porter A, Votta LG (1998) Comparing detection methods for software requirements specification: A replication using professional subjects. Empirical Software Engineering 3(4): 355-379.
41. Robertson S, Robertson JH (1999) Mastering the requirements process. Boston: Addison- Wesley.
42. Rupp C, Queins S (2003) Vom use-case zum Test-Case. OBJEKTspektrum, Vol.4.
43. Shull F, Rus I, Basili V (2000) How perspective-based reading can improve requirements inspections. IEEE Computer 33(7):73-79.
44. 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.
45. 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.
46. Sommerville I, Sawyer P (1997) Requirements engineering. A good practice guide. Chichester: John Wiley & Sons.
47. http://www.standishgroup.com/chaos-chronicles/index.php Accessed on 3rd December 2004.
48. 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.
49. Wiegers K E (2002) Peer reviews in software. A practical guide. Boston: Addison- Wesley.
50. Wiegers K E (1999) Writing quality requirements. Software Development Magazine, 7(5): 44-48.
51. Wiegers K E (2000) Karl Wiegers describes 10 requirements traps to avoid. Software Testing & Quality Engineering Journal, January/February, 2(1).
52. Wilson WM, Rosenberg LH, Hyatt LE (1996) Automated quality analysis of natural language requirements specifications. NASA Software Assurance Technology Center, USA.