Abstract:
Use-case modelling provides a means of specifying external
features of a system during requirements elicitation. In principle, use
cases can be used to size the system about to be built but, for that, a
standard format for their documentation is required. Furthermore, gathering
use-case metrics requires a software development process that
prodnces complete use-case descriptions in a repeatable way. Here, we
set out the requirements for such a standardization so that use cases can
be metricated. Once accomplished, it is possible to evaluate the important
research questions of whether use-case attributes such as size and
complexity can be controlled and whether use-case metrics are sufficiently
rigorous for estimating effort. Finally, we note that this added
rigour applied to use cases shonld improve the consistency and quality
of communication between client and developer, helping to ensure that
the right system is built.
