01.02.2013 Views

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

Software Development Cross Solution - Index of - Free

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

An equivalent Use Case<br />

that describes the same<br />

“Send a picture to other<br />

users” requirement<br />

Observation<br />

is a key<br />

component<br />

in getting<br />

good use cases<br />

written.<br />

A use case’s sequence<br />

normally contains more<br />

steps and detail than a<br />

user story. This makes<br />

it easier to work to<br />

for developers, but<br />

means extra work with<br />

the customer to nail<br />

these details down.<br />

1. Click on the “Send a Picture button”<br />

2. Display users the picture can be sent to in<br />

the address book list box.<br />

2a. Enter the destination user’s name in the<br />

search box<br />

2b. Click on search to find the user<br />

3. Select the user to send the picture to<br />

4. Click on send<br />

Send a picture to other users<br />

5. The receiver is asked if they want to accept<br />

the photo<br />

5a.1. The receiver accepts the photo<br />

5a.2. The receiver views the photo<br />

5b.1. The recevier rejects the photo<br />

5b.2. The photo is trashed.<br />

So what’s the big difference?<br />

Well, actually not a lot, really. User stories are usually around three lines long, and are<br />

accompanied by an estimate and a priority, so the information is all in one bite-sized place.<br />

Use cases are usually reasonably more detailed descriptions <strong>of</strong> a user’s interaction with the<br />

s<strong>of</strong>tware. Use cases also aren’t usually written along with a priority or an estimate—those<br />

details are <strong>of</strong>ten captured elsewhere, in more detailed design documentation.<br />

User stories are ideally written by the customer, whereas traditionally use cases are not.<br />

Ultimately either approach does the same job, capturing what your customer needs your<br />

s<strong>of</strong>tware to do. And one use case, with alternate paths (different ways to use the s<strong>of</strong>tware in<br />

a specific situation) may capture more than one user story.<br />

Download at WoweBook.Com<br />

leftovers<br />

You can add more<br />

detail to your user<br />

story, or modify your<br />

use case to have a<br />

little less detail... it’s<br />

really up to you and<br />

your customer.<br />

There are a number <strong>of</strong><br />

different ways that you can<br />

write down a use case. This<br />

one describes the interactions<br />

that a user has with the<br />

s<strong>of</strong>tware, step by step.<br />

you are here 4 439

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!