Use Case Modelling
Use Case modelling addresses requirements by focusing on how a system will be used, and describing all possible useage scenarios. This perspective, which is then used to drive analysis. design, coding and testing, ensures that the delivered system does what the users want, because that is how it has been conceived and implemented.
Capturing a use case involves describing the interactinos between the user and the system. These event-response dialogues are captured as use case flows; any variances in behaviour of the system are captured as alternate flows. A particular path through a use case in terms flows represents a useage scenario.
The problems that most organisations experience when adopting use case modelling relate mainly to the style of describing use case flows - where the flows. This is not helped by the fact that there are literally dozens of books on the subject, and all have their own favourite style - and yet many of them shy away from giving a proscriptive style with well-defined rules of correctness.
Improvix has developed a proscriptive style for specifying use cases that has been proven effective by many organisaions. We have found that such a proscriptive apporach has many benefits, beyond those that seem obvious:-
- Helps those new to use case modelling get started quickly
- Eliminates ambiguity and irrelevant test from use cases
- Enables the size of use case flows to be compared, and useful in estimation
- Eases the transition to Analysis
- Reduces maintenance of use cases
Team members require this skill to successfully perform the following roles: System Analyst and Requirements Specifier.
This skill is taught as part of the following courses:-
Users require this skill to gain the full benefits from the following tools:-