Feeds

Model use cases that work

Think succinct

Secure remote control for conventional and virtual desktops

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

Secure remote control for conventional and virtual desktops

More from The Register

next story
The Return of BSOD: Does ANYONE trust Microsoft patches?
Sysadmins, you're either fighting fires or seen as incompetents now
Munich considers dumping Linux for ... GULP ... Windows!
Give a penguinista a hug, the Outlook's not good for open source's poster child
Intel's Raspberry Pi rival Galileo can now run Windows
Behold the Internet of Things. Wintel Things
Linux Foundation says many Linux admins and engineers are certifiable
Floats exam program to help IT employers lock up talent
Microsoft cries UNINSTALL in the wake of Blue Screens of Death™
Cache crash causes contained choloric calamity
Eat up Martha! Microsoft slings handwriting recog into OneNote on Android
Freehand input on non-Windows kit for the first time
Linux kernel devs made to finger their dongles before contributing code
Two-factor auth enabled for Kernel.org repositories
prev story

Whitepapers

Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Top 10 endpoint backup mistakes
Avoid the ten endpoint backup mistakes to ensure that your critical corporate data is protected and end user productivity is improved.
Top 8 considerations to enable and simplify mobility
In this whitepaper learn how to successfully add mobile capabilities simply and cost effectively.
Rethinking backup and recovery in the modern data center
Combining intelligence, operational analytics, and automation to enable efficient, data-driven IT organizations using the HP ABR approach.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.