UseCases – Writing – Samples

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)

Scope: Insurance company Operations
Level: Business strategic
Release: Future Status: Draft Revision: Current
Context of use: Claims Adjuster handles claim.
Primary Actor: Claimant
Preconditions: A loss has occurred
Trigger: A claim is reported to Insurance company
Main Success Scenario:
1. A reporting party who is aware of the event reports a claim to Insurance company.
2. Clerk receives and assigns the claim to a claims adjuster.
3. The assigned Claims Adjuster

-conducts an investigation
-evaluates damages
-sets reserves
-negotiates the claim
-resolves the claim and closes it

Extensions

to be written

Success End Condition:Claim is resolved and closed
Failed End Protection:
Stakeholder & interest:

Insurance company Divisions who sell Insurance company policies
Insurance company Customers who have purchased policies
Depart of Insurance who sets market conduct
Claimants who have loss as a result of act of an insured
Insurance company Claims Division
Future Customers


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.

(Ctn)

From: Writing Effective Use Cases

Oliver.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: