How to elaborate a use case

Authors:
D. C. McDermid
Affiliations:
Edith Cowan University, West Australia
Venue:
Practicing software engineering in the 21st century
Year:
2003

Citing 5
Cited 0

On visual formalisms

Communications of the ACM
Object-oriented software engineering

Object-oriented software engineering
Rule-based behaviour modelling: specification and validation of information systems dynamics

Information and Software Technology
The right tools for coding business rules

Datamation
A Behaviour Integrated Entity-Relationship Approach for the Design of Object-Oriented Databases

Proceedings of the Seventh International Conference on Enity-Relationship Approach: A Bridge to the User

Quantified Score

Hi-index	0.01

Visualization

Abstract

This paper challenges established wisdom with respect to use cases. Use cases are classically elaborated by directly identifying objects, methods and data. The research reported in this paper indicates that there are other better constructs for modeling use cases, at least initially, and that objects are not a particularly good medium for discussing requirements with users. This paper rehearses the arguments leading up to these conclusions and identifies some implications of these conclusions.