An experiment in inspecting the quality of use case descriptions

Journal of Research and Practice in Information Technology

Volumn 36, Issue 4, 2004, Pages 211-229

  Cox, Karl ^a   Aurum, Aybüke ^a   Jeffery, Ross ^a  

^a UNIVERSITY OF NEW SOUTH WALES   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SIMULATION; CUSTOMER SATISFACTION; QUALITY CONTROL; SEMANTICS; STRATEGIC PLANNING; USER INTERFACES;

DEFECT FREE; HIGH QUALITY SOFTWARE PRODUCT; TECHNICAL ERRORS;

COMPUTER SOFTWARE;

EID: 8344225273     PISSN: 1443458X     EISSN: None     Source Type: Journal    
DOI: None     Document Type: Article

References (51)

1. ACHOUR, C., ROLLAND, C., MAIDEN, N. and SOUVEYET, C., (1999): Guiding use case authoring: results from an empirical study, 4th IEEE International Symposium on Requirements Engineering, Limerick, 7-11 June.
2. ADOLPH, S., BRAMBLE, P., COCKBURN, A. and POLS. (2003): Patterns for Effective Use Cases, Addison-Wesley.
3. ALEXANDER, I. (2003): Misuse cases: Use cases with hostile intent, IEEE Software, Jan/Feb, 58-66.
4. ANDA, B. and SJOBERG, D. (2002): Towards an inspection technique for use case models, 14th Int. Conf. on Software Engineering and Knowledge Engineering (SEKE'02), Ischia, Italy, 15-19 July, 127-134.
5. ANDA, B., SJOBERG, D. and JORGENSEN, M. (2001): Quality and understanding of use case models, In: LINDSKOV KNUDSEN, J. (editor), 15th European Conference on Object-Oriented Programming, Budapest, June 18-22, Berlin, LNCS, Springer-Verlag, 402-428.
6. BIFFL, S. and HALLING, M. (2003): Investigating the defect detection effectiveness and cost benefit of nominal inspection teams, IEEE Trans. Software Engineering, 29 (5): 385-397.
7. BITTNER, K. and SPENCE, I. (2002): Use Case Modelling, Addison-Wesley.
8. BRAY, I. (2002): An Introduction to Requirements Engineering, Addison-Wesley.
9. BRYKCZYNSKI, B. (1999): A survey of software inspection checklists, ACM Sigsoft: Software Engineering Notes, 24(1): 82-89.
10. COCKBURN, A. (2001): Writing Effective Use Cases, Addison-Wesley.
11. COX, K. (2002): Heuristics for Use Case Descriptions, PhD Thesis, Bournemouth University, UK, November.
12. COX, K., AURUM, A. and JEFFERY, R., (2004): A use case description inspection experiment, School of Computer Science and Engineering, University of New South Wales, Technical Report: UNSW-CSE-TR-0414, ftp://ftp.cse.unsw.edu.au/ pub/doc/papers/UNSW/0414.pdf.
13. COX, K. and PHALP, K. (2000): Replicating the CREWS use case authoring guidelines experiment, Empirical Software Engineering Journal, 5(3): 245-268.
14. COX, K., PHALP, K. and SHEPPERD, M. (2001): Comparing use case writing guidelines, In: ACHOUR-SALINESI, C., OPDAHL, A., POHL, K. and ROSSI, M. (editors), 7th International Workshop on Requirements Engineering: Foundation for Software Quality, Interlaken, Switzerland, 4-5 June, Essen, Essener Informatik Beitrage, 101-112.
15. DUNSMORE, A., ROPER, M. and WOOD, M. (2003): Practical code inspection techniques for object-oriented systems: An experimental comparison, IEEE Software, July/August, 21-29.
16. FAGAN, M. (1976): Design and code inspections to reduce errors in program development, IBM Systems Journal, 15(3): 182-211.
17. FUSARO, P., LANUBILE F. and VISAGGIO, G. (1997): A replicated experiment to assess requirements inspection techniques, Empirical Software Engineering Journal, 2: 39-57.
18. GAUSE, D. and WEINBERG, G. (1989): Exploring Requirements: Quality Before Design, Dorset House.
19. GARNHAM, A. and OAKHILL, J. (1996): The mental models theory language of comprehension, In: BRITTON, B. and GRAESSER, A. (editors), Models of Understanding Text, Mahwah, NJ, Lawrence Erlbaum Associates, 313-339.
20. GERNSBACHER, M. (1996): The structure-building framework: what it is, what it might also be and why, In: BRITTON, B. and GRAESSER, A. (editors), Models of Understanding Text, Mahwah, NJ, Lawrence Erlbaum Associates, 289-311.
21. GERNSBACHER, M. (1997): Two decades of structure building, Discourse Processes, 23(3): 265-304.
22. GOLDMAN, S., VARMA, S. and COTE, N. (1996): Extending capacity-constrained construction integration: toward 'smarter' and flexible models of text comprehension, In: BRITTON, B. and GRAESSER, A. (editors), Models of Understanding Text, Mahwah, NJ, Lawrence Erlbaum Associates, 73-113.
23. GRAESSER, A., SWAMER, S., BAGGETT, W. and SELL, M. (1996): New models of deep comprehension, In: BRITTON, B. and GRAESSER, A. (editors), Models of Understanding Text, Mahwah, NJ, Lawrence Erlbaum Associates, 1-32.
24. GRAHAM, I. (1998): Requirements Engineering and Rapid Development, Harlow, Addison-Wesley.
25. HALLING, M. BIFFL, S., GRECHENIG T. and KOEHLE, M. (2001): Using reading techniques to focus inspection performance, IEEE Proceedings of Euromicro Conf., 248-257.
26. JACKSON, M. (1995): Software Requirements and Specifications, Addison-Wesley.
27. JACOBSON, I., CHRISTERSON, M., JONSSON, P. and OVERGAARD, G, (1992): Object-Oriented Software Engineering: A Use Case Driven Approach, Wokingham, Addison-Wesley.
28. KAMPHAN, P. (2003): Use case specification checklist, http://cmvl.cs.concordia.ca/courses/soen-341/winter-2003/use_case_checklist.pdf
29. KLARITI (2003): Inspection checklist for use case documents, www.klariti.com/templates/use-case-checklist.shtml
30. KULAK, D. and GUINEY, E. (2000): Use Cases - Requirements in Context, Harlow, Addison-Wesley.
31. LAUESEN, S. (2002): Software Requirements: Styles and Techniques, Harlow, Addison-Wesley.
32. LAUESEN, S. and VINTER, O. (2001): Preventing requirements defects: An experiment in process improvement, Requirements Engineering Journal, 6: 37-50.
33. MCBREEN, P. (2001): http://www.mcbreen.ab.ca/papers/QAUseCases.html
34. MILLER, J., WOOD, M. and ROPER, M. (1998): Further experiences with scenarios and checklists, Empirical Software Engineering, 3: 37-64.
35. NEILL, C. and LAPLANTE, P. (2003): Requirements engineering: the state of the practice, IEEE Software, Nov/Dec, 20(6): 40-45.
36. OMG - OBJECT MANAGEMENT GROUP (2003). Unified Modeling Language Notation Guide vl.5. Document 03-03-10. http://www.omg.org/
37. PARNAS, D. and LAWFORD, M. (2003): Inspection's role in software quality assurance - Guest Editorial, IEEE Software, July/August, 16-20.
38. PHALP K. and COX, K. (2002): Supporting communicability with use case guidelines: An empirical study, EASE 2002, 6th International Conference on Empirical Assessment and Evaluation in Software Engineering, Keele University, Staffordshire, UK, April 8-10.
39. POOLEY, R. and STEVENS, P. (1999): Using UML - Software Engineering with Objects and Components, Harlow, Addison-Wesley.
40. PORTER, A., VOTTA, L. and BASILI, V. (1995): Comparing detection methods for software requirements inspections: A replicated experiment, IEEE Transactions on Software Engineering, 21(6): 563-575.
41. REGNELL, B., RUNESON, P. and THELIN, T. (2000): Are perspectives really different? - Further experiences on scenario-based reading of requirements, Empirical Software Engineering Journal, 5(4): 331-356.
42. ROMBACH, C. D., KUDE, O., AURUM, A., JEFFERY, R. and WOHLIN, C. (2003): An empirical study of an ER-model inspection meeting, 29th Euromicro Conference, Antalya, Turkey, 3-5 September, 308-315.
43. SANDAHL, K., BLOMKVIST, O., KARLSSON, J., KRYSANDER, C., LINDVALL M. and OHLSSON, N. (1998): An extended replication of an experiment for assessing methods for software requirements inspections, Empirical Software Engineering, 3: 327-354
44. SCHNEIDER, G. and WINTERS, J. (1998): Applying Use Cases: A Practical Guide, Harlow, Addison-Wesley.
45. TERVONEN I. (2003): http://tol.oulu.fi/~tervo/Checklist.pdf, accessed 28/7/2003.
46. THELIN, T., RUNESON, P. and WOHLIN, C. (2003): Prioritized use cases as a vehicle for software inspection, IEEE Software, July/August, 30-33.
47. TRABASSO, T., VAN DEN BROEK, P. and SUH, S. (1989): Logical necessity and transitivity in causal relations in stories, Discourse Processes, 12: 1-25.
48. TRAVASSOS, G. H., SHULL, F., FREDERICKS, M. and BASILI, V. (1999): Detecting defects in object oriented designs: Using reading techniques to increase software quality, Proceedings of the 14th ACM conference Object-Oriented Programming Systems Languages and Applications - OOPSLA'99, Denver, Colorado, USA, 1-5 November, 47-56.
49. VOTTA, L. (1993): Does every inspection need a meeting?, Proceedings of the ACM SIGSOFT 1993 Symposium on foundations of software engineering, 18 December, 107-114.
50. WIEGERS, K. (2003): Inspection checklist for use case documents, http://www.processimpact.com/process_assets/use_case_checklist.doc, Process Impact
51. WOHLIN, C. and AURUM, A. (2003): Evaluating cost-effectiveness of checklist-based reading of entity-relationship diagrams, Proceeding of 9th International Software Metrics Symposium, METRICS'03'. Sydney, Australia, 3-5 September, 286-296.