Feeds

Model use cases that work

Think succinct

Intelligent flash storage arrays

Book extract, part 2 In the first extract from their book Use Case Driven Object Modeling with UML: Theory and Practice, Reg Dev regular and Agile Iconoclast Matt Stephens and his colleague Doug Rosenberg introduced you to domain modeling.

In this, the second of four installments, the duo show you how to write useful use cases so the design, work estimates and tests flow logically out of each use case.

With an initial domain model in place, it's time to begin writing use cases – highlighted in red in the ICONIX Process map below.

Use case iconix process

Putting the use case model on the map

Use cases give you a structured way of capturing the behavioral requirements of a system, so that you can reasonably create a design from them. They help you to answer the fundamental questions of what are the users of the system trying to do and what is the user experience. A surprising amount of what your software does is dictated by the way in which users must interact with it.

Top 10 use case modeling guidelines

The principles discussed in this chapter can be summed up as a list of guidelines. These guidelines, in turn, can be summed up in a single sentence: describe system usage in the context of the object model.

In practical terms, this means you need to reference domain classes that participate in the use case, and you need to name your screens and other boundary objects explicitly in the use-case text. Otherwise, your behavior requirements will be completely disconnected from your object model, and - surprise - you won't be able to drive designs from the use cases.

Here, then, is this chapter's 10-point checklist for successful use case modeling. As with our list last time, pay attention because we shall be asking questions:

10. Reference boundary classes (like screens) by name

9. Reference domain classes by name

8. Write your use cases using a noun-verb-noun sentence structure

7. Write the use case in the context of the object model

6. Remember that your use case is really a runtime behavior specification

5. Use GUI prototypes and screen mock ups

4. Write your use case using an event/response flow, describing both sides of the user/system dialog

3. Write your use cases in active voice

2. Organize your use cases with actors and use case diagrams

1. Follow the two-paragraph rule, and don't pad out the use case with presentation details

Remote control for virtualized desktops

More from The Register

next story
Nexus 7 fandroids tell of salty taste after sucking on Google's Lollipop
Web giant looking into why version 5.0 of Android is crippling older slabs
Be real, Apple: In-app goodie grab games AREN'T FREE – EU
Cupertino stands down after Euro legal threats
Download alert: Nearly ALL top 100 Android, iOS paid apps hacked
Attack of the Clones? Yeah, but much, much scarier – report
SLURP! Flick your TONGUE around our LOLLIPOP – Google
Android 5 is coming – IF you're lucky enough to have the right gadget
Microsoft: Your Linux Docker containers are now OURS to command
New tool lets admins wrangle Linux apps from Windows
Bada-Bing! Mozilla flips Firefox to YAHOO! for search
Microsoft system will be the default for browser in US until 2020
prev story

Whitepapers

Choosing cloud Backup services
Demystify how you can address your data protection needs in your small- to medium-sized business and select the best online backup service to meet your needs.
A strategic approach to identity relationship management
ForgeRock commissioned Forrester to evaluate companies’ IAM practices and requirements when it comes to customer-facing scenarios versus employee-facing ones.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
Getting ahead of the compliance curve
Learn about new services that make it easy to discover and manage certificates across the enterprise and how to get ahead of the compliance curve.
Saudi Petroleum chooses Tegile storage solution
A storage solution that addresses company growth and performance for business-critical applications of caseware archive and search along with other key operational systems.