| Towards an inspection technique for use case models |
| Full text |
Pdf
(406 KB)
|
| Source
|
SEKE; Vol. 27
archive
Proceedings of the 14th international conference on Software engineering and knowledge engineering
table of contents
Ischia, Italy
SESSION: Requirements engineering
table of contents
Pages: 127 - 134
Year of Publication: 2002
ISBN:1-58113-556-4
|
|
Authors
|
|
| Publisher |
|
| Bibliometrics |
Downloads (6 Weeks): 9, Downloads (12 Months): 88, Citation Count: 2
|
|
|
ABSTRACT
A use case model describes the functional requirements of a software system and is used as input to several activities in a software development project. The quality of the use case model therefore has an important impact on the quality of the resulting software product. Software inspection is regarded as one of the most efficient methods for verifying software documents. There are inspection techniques for most documents produced in a software development project, but no comprehensive inspection technique exists for use case models. This paper presents a taxonomy of typical defects in use case models and proposes a checklist-based inspection technique for detecting such defects. This inspection technique was evaluated in two studies with undergraduate students as subjects. The results from the evaluations indicate that inspections are useful for detecting defects in use case models and motivate further studies to improve the proposed inspection technique.
REFERENCES
Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.
| |
1
|
Bente Anda , Hege Dreiem , Dag I. K. Sjøberg , Magne Jørgensen, Estimating Software Development Effort Based on Use Cases-Experiences from Industry, Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools, p.487-502, October 01-05, 2001
|
| |
2
|
|
| |
3
|
|
| |
4
|
|
| |
5
|
|
| |
6
|
|
| |
7
|
Fagan, M. E. Design and Code Inspections to Reduce Errors in Program Development. IBM Systems Journal, Vol. 15(3), pp. 182-211, 1976.
|
| |
8
|
|
| |
9
|
Hurlbut, R. R. A Survey of Approaches for Describing and Formalizing Use Cases. Technical Report: XPT-TR-97-03, Expertech, Ltd., 1997.
|
| |
10
|
|
| |
11
|
|
| |
12
|
Lanubile.F. and Visaggio, G. Assessing defect detection methods for software requirements inspections through external replication, ISERN-96-01, January 1996.
|
| |
13
|
|
| |
14
|
|
| |
15
|
Kristian Sandahl , Ola Blomkvist , Joachim Karlsson , Christian Krysander , Mikael Lindvall , Niclas Ohlsson, An Extended Replication of an Experiment for AssessingMethods for Software Requirements Inspections, Empirical Software Engineering, v.3 n.4, p.327-354, December 1998
[doi> 10.1023/A:1009724120285]
|
| |
16
|
|
| |
17
|
|
| |
18
|
Shull, F., Travassos, G. H., Carver, J. and Basili, V. R. Evolving a Set of Techniques for OO Inspections. CS-TR-4070 and UMIACS-TR-, October 1999.
|
| |
19
|
|
| |
20
|
Thelin, T., Runeson, P. And Wohlin, C. An Experimental Comparison of Usage-Based and Checklist-Based Reading. WISE 2001.
|
| |
21
|
|
| |
22
|
www.mcbreen.ab.ca/papers/QAUseCases.html
|
|