In many projects there is often a need for a
lightweight analysis approach and a widely accepted way of doing this
involve the use cases.
Specifying requirements involves describing both the
dynamics (i.e. interactions) of the problem and static things that this
dynamic will interact with.
Use cases are good at describing at describing the
dynamic interaction, but are structurally poor at describing these static
Analysts often compensate for this by:
Uncorrected this will result in:
The solution would be:
This paper highlights an approach to how use case are
elaborated, and identifies how common pitfalls can be avoided.
It provides an example of a hypothetical trade
acceptance process that extends the example use case given
2002-2005 Codel Services Ltd