1. Moving high level to low level
I selected the following use cases because they are examples built using the Stakeholder-Interests model. There is almost no discernible difference in the writing – it is just that the writing was double-checked against the stakeholders and their interests along the way. The inclusion of stakeholders was an experiment, and considered a successful one at the end of the writing period. Including them did not cost much energy or time, while giving us a tighter framework for thinking about what we were producing, and helped us notice when we had accidentally omitted steps.
These use cases start from very high ("white" / "strategic"), move through "blue" or "user goal" level, down to "indigo’ or "subfunction", illustrating how to shift goal levels. Watch also as the system scope shrinks from "company operations" to "all computer systems" to just the system under design.
1.1. Handle Claim(business)
Commentary on this use case:
This is a "business" use case – the "system under design" is the
entire operations of the company. The computer system is not even mentioned. The use case will be used by the business to anchor its business procedures, and to search for a way to use the computer to facilitate its operations. At the moment, this use case is only in its first stage of sketching. As usual, the main success scenario looks trivial … it should, because it shows how
things work in the main success situation! The interesting bits will show up in the failure conditions, and in how the company uses this information to nominate improvements to its IT support of operations.
From: Writing Effective Use Cases