Patterns for effective use cases
著者
書誌事項
Patterns for effective use cases
(The agile software development series / Alistair Cockburn and Jim Highsmith, series editors)
Addison-Wesley, c2003
大学図書館所蔵 全2件
  青森
  岩手
  宮城
  秋田
  山形
  福島
  茨城
  栃木
  群馬
  埼玉
  千葉
  東京
  神奈川
  新潟
  富山
  石川
  福井
  山梨
  長野
  岐阜
  静岡
  愛知
  三重
  滋賀
  京都
  大阪
  兵庫
  奈良
  和歌山
  鳥取
  島根
  岡山
  広島
  山口
  徳島
  香川
  愛媛
  高知
  福岡
  佐賀
  長崎
  熊本
  大分
  宮崎
  鹿児島
  沖縄
  韓国
  中国
  タイ
  イギリス
  ドイツ
  スイス
  フランス
  ベルギー
  オランダ
  スウェーデン
  ノルウェー
  アメリカ
注記
Includes bibliographical references (p. 217-218) and index
内容説明・目次
内容説明
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.
目次
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
「Nielsen BookData」 より