|
||||||||||||||||||||
|
||||||||||||||||||||
|
||||||||||||||||||||
商品の説明
内容説明
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.
Back Cover Copy
Use cases have become an integral part of modeling software requirements, but many software developers are discovering that writing effective use cases is more difficult than they had anticipated. An understanding of the basic principles of use cases is not enough. Software developers need a source of objective criteria by which to judge quality and effectiveness.
Patterns for Effective Use Cases provides this set of objective criteria. Written by experienced use case practitioners, this book fills a critical information gap by presenting a pattern language that contains over thirty patterns, providing simple, elegant, and proven solutions to the most common problems in use case development. These patterns distill and define the properties and characteristics of quality use cases. As such, they facilitate the development of original use cases and provide a diagnostic tool for evaluating existing ones.
The book opens with a review of use cases and pattern fundamentals, along with a discussion of the requirements-gathering team. These patterns address the use case development process, the internal structure of use cases, and the relationships among use cases within the system as a whole. Examples of patterns include:
- BreadthBeforeDepth
- VisibleBoundary
- EverUnfoldingStory
- IntentionRevealingName
- PreciseAndReadable
- LeveledSteps
- InterruptsAsExtensions
- RedistributeTheWealth
Each pattern discussion includes at least one example demonstrating its real-world application, highlighting both the benefits of using the pattern and the consequences of not doing so. In addition, the book presents guidelines for the effective use of UML with relevant patterns.
Anyone involved in use case writing or requirements gathering will find Patterns for Effective Use Cases an indispensable handbook and reference.
0201721848B07302002
登録情報
|
この本のなか見！検索より
（詳細はこちら）
この商品にタグをつける(詳細)タグは、商品との関連性が非常に強いキーワードまたはラベルのようなものです。
タグにより、すべてのお客様がお気に入りの商品の整理と確認を行うことができます。 ※タグは初期設定で公開になっています。詳しくはこちら |
カスタマーレビュー
最も参考になったカスタマーレビュー
1 人中、1人の方が、｢このレビューが参考になった｣と投票しています。
形式:ペーパーバック|Amazonが確認した購入
Alistair CockburnのWriting Effective Use Caseの続編的な本で、著者達が持ち寄ったユースケース図やイベントフローを記述する時に守るべきことが約３０まとめられています。具体的にユースケース図やイベントフローの良い例、悪い例が掲載されているので理解しやすかったです。開発プロジェクトのユースケースモデルのガイドラインとして十分使えます。
形式:ペーパーバック
Alistair CockburnのWriting Effective Use Case（邦訳：ユースケース実践ガイド 翔泳社）だけでも他書に比べれば実践的で素晴らしいと思っていましたが、それでもまだ理論的な話が多かったように思っていました。
それに対してこの本はユースケースを書く上で、さらに状況とポイントを絞って解説をした上で、良い例と悪い例を比較するなど非常に噛み砕いたチュートリアルとなっています。
各章の長さも手頃で起承転結がはっきりしていて、結論がはっきり述べられているので読みやすいです。
ただ、私見ではありますがユースケースの初心者向けかというとそうでもないのではと思っています。あくまでも一応の基礎を持った人が、それを実践でどの様に生かしていけばよいのかということに関して非常に役に立つガイドとして捉えたほうがいいと思います。!
なので、先に挙げたAlistair Cockburnの本を読まれてからこの本にトライすることをお薦めします。
Amazon.com で最も参考になったカスタマーレビュー (beta)
Amazon.com:
6件のカスタマーレビュー
20 人中、16人の方が、｢このレビューが参考になった｣と投票しています。
Good advice but fails to address the real UC issues
2003/7/29
形式:ペーパーバック
This book attempts to take use cases to a higher level of science and in part succeed. Its plus points are discussions on management of use cases and the processes a team goes through in completing the creation / validation cycle. There's a lot of good sense here. Some of the patterns are useful. However, there's also a lot of regurgitation from various other texts and papers, some written by the authors themselves. And some key aspects are missing, aspects that are really important to industry and others that have concerned academia. Industry is not too worried about how to name use cases these days; that's easy. They want to be able to estimate how long it will take to build the system from use case points, for instance, or how to achieve forward traceability to the design and maintain traceability back to the requirements and business strategies (not the same thing exactly as the use case goal - which typically is not to stuff up and to make the principal actor happy). Academics are concerned too with effort estimation, with grammar and consistency checking, with dependencies and product lines, and non-functional requirements and whether use cases are at all to do with requirements in the first place and what they are no good for. Not whether we can build a little online booking web site - we can already do that. Though the book does not set out to answer these difficult questions, in its 200-odd pages, it ought to have, since this is what we really want to know about. So, though the book is excellent on what it does address, there's a lot of over kill in this. What's missing is what it does not address - all the hard problems we really need answers to.
59 人中、44人の方が、｢このレビューが参考になった｣と投票しています。
Overkill
2002/11/16
形式:ペーパーバック
The fact that this book describes a "pattern" named PreciseAndReadable should tell you what you need to know. If you need to be told that use cases should be precise and readable, or that you should name them with active verb phrases (VerbPhraseName), or that they should describe things of value to the business people (UserValuedTransactions), or that you should involve those people in the process of writing them (ParticipatingAudience), or that you should stop writing them when they make those people happy (QuittingTIme), you'll certainly get some value from this book, but it's clear evidence that your problems run considerably deeper than this book will be able to address.
This represents 25 pages of fundamentally simple content spread across 200 pages, and in a thoroughly pretentious manner to boot. Avoid.
7 人中、6人の方が、｢このレビューが参考になった｣と投票しています。
The How, What and Why of Use Cases
2002/12/22
形式:ペーパーバック
Patterns for Effective Use cases is a must read if you need to develop for a software application. The authors describe what makes for a good use case, and make the points memorable with stories, and examples. If you have lots of experience writing use cases many of the patterns will cover things that you already know, but the way the patterns are presented make for an effective tool to help you teach others how to write a good use case. The pattern language format makes it clear that any single practice will not make for a good use case, you need to take a number together, otherwise you may have something that looks good at first glance, but just does not work.
I recommend this book for anyone who is learning to write use cases, or for experienced people who want a refesher course.
これらのレビューは参考になりましたか？
ご意見はクチコミでお聞かせください。
関連商品を探す
同じキーワードの商品を探す
フィードバック
- カタログ情報、または画像について報告
- 著者からのコメント
- 出版社からのコメント
|
