Sizing Use Cases: How to Create a Standard Metrical Approach
OOIS '02 Proceedings of the 8th International Conference on Object-Oriented. Information Systems
TOOLS '99 Proceedings of the Technology of Object-Oriented Languages and Systems
How natural is natural language?: how well do computer science students write use cases?
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
A Benchmarking-Based Requirement Analysis Methodology for Improving Web Sites
International Journal of Electronic Commerce
Empirical Software Engineering
An investigation of use case quality in a large safety-critical software development project
Information and Software Technology
Tool support for essential use cases to better capture software requirements
Proceedings of the IEEE/ACM international conference on Automated software engineering
Towards the improvement of use case models: the AIRDoc process
Proceedings of the 2011 ACM Symposium on Applied Computing
When use cases are not useful: data practices, astronomy, and digital libraries
Proceedings of the 11th annual international ACM/IEEE joint conference on Digital libraries
Enhanced misuse case model: a security requirement analysis and specification model
ICCSA'06 Proceedings of the 2006 international conference on Computational Science and Its Applications - Volume Part V
A comparative analysis of use case relationships
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
The Effect of Firewall Testing Types on Cloud Security Policies
International Journal of Strategic Information Technology and Applications
| Hi-index | 0.00 |
One of the beauties of use cases is their accessible, informal format. Use cases are easy to write, and the graphical notation is trivial. Because of their simplicity, use cases are not intimidating, even for teams that have little experience with formal requirements specification and management. However, the simplicity can be deceptive; writing good use cases takes some skill and practice. Many groups writing use cases for the first time run into similar kinds of problems. This paper presents the author's "Top Ten" list of use case pitfalls and problems, based on observations from a number of real projects. The paper outlines the symptoms of the problems, and recommends pragmatic cures for each. Examples are provided to illustrate the problems and their solutions.