Patterns for effective use cases

Author(s)

    • Adolph, Steve
    • Bramble, Paul
    • Cockburn, Alistair
    • Pols, Andy

Bibliographic Information

Patterns for effective use cases

Steve Adolph and Paul Bramble ; with contributions by Alistair Cockburn and Andy Pols

(The agile software development series / Alistair Cockburn and Jim Highsmith, series editors)

Addison-Wesley, c2003

Available at  / 2 libraries

Search this Book/Journal

Note

Includes bibliographical references (p. 217-218) and index

Description and Table of Contents

Description

Use cases have become a very popular requirements-gathering technique, yet many developers struggle when faced with writing them. They grasp the basic concepts, but find that writing effective use cases turns out to be more difficult than they expected. One factor contributing to this difficulty is that the community lacks objective criteria for judging the quality of use cases. This new book articulates the qualities of effective use cases by applying the proven patterns concept of development to this requirements-gathering technique. The authors present a catalog of thirty-six patterns that help the reader become proficient at judging the quality of their (and other's) patterns. These patterns represent solutions to recurring problems that application developers have faced in writing use cases. Each pattern is presented with examples that help the reader understand the benefit of the pattern, and just as importantly, the consequences of ignoring its proper use.

Table of Contents

Preface. 1. What is a Quality Use Case? Why Use Cases at All? What's So Hard About Telling Good Stories? Why a Use Case Pattern Language? What are Patterns. How Should I use this Pattern Language. What is he Use Case Pattern Form? Stepping Through a Sample Pattern. The Examples. Organization of the Pattern Catalog. Process Patterns. Structural Patterns. Supplement: A Brief Tutorial on Writing Use Cases. 2. The Team. Team organizational issues. SmallWritingTeam(47). ParticipatingAudience(50). BalancedTeam(54). Tradeoffs and Collaborations. 3. The Process. BreadthBeforeDepth(63). Breadth Before Depth and UML by Dan Rawthorne. SpiralDevelopment(66). SpiralDevelopment and UML Models by Dan Rawthorne. MultipleForms(83). QuittingTime(71). TwoTierReview(76). WritersLicense(80). Tradeoffs and Collaborations. 4. The Use Case Set. SharedClearVision(95). VisibleBoundary(101). VisibleBoundary(101) and UML Models by Dan Rawthorne. ClearCastOfCharacters(105). UserValuedTransactions(110). EverUnfoldingStory(117). EverUnfoldingStory and UML Models by Dan Rawthorne. Tradeoffs and Collaborations. 5. The Use Case. CompleteSingleGoal(132). IntentionRevealingName(144). ScenarioPlusFragments(136). ExhaustiveAlternatives(140). Adornments(147). PreciseAndReadable(152). Tradeoffs and Collaborations. 6. Scenarios and Steps. DetectableConditions(168). LeveledSteps(173). VisibleActorIntent(161). ForwardProgress(164). TechnologyNeutral(177). Tradeoffs and Collabora

by "Nielsen BookData"

Related Books: 1-1 of 1

Details

Page Top