It shows how we can be flexible in the requirements space and still achieve project success Very usefully - though definitely not entertainment. Oct 22, Nat rated it liked it. It's a good book, but not to my liking. It has too many examples examples are cool, but I'm not going to just copy your use cases , confusing made-up terminology if I say something like 'indigo goals', nobody on the team will understand me , childish symbols kites, waves, houses?
I personally would much prefer if it was more concise and to the point. Nov 13, Franck Chauvel rated it liked it Shelves: software-enginering. Use cases? Cockburn is the place to start. I am always unsure about how much requirement I need, especially when building prototypes? So, reading about use-cases, I came across it on M.
Here come pages on use-cases only. Part I details the various sections they include, whereas Part II discusses frequently asked questions. UML diagrams only show up in appendix. Cockburn is another contributor to the Agile Manifesto and created the Crystal family of agile methodology. He authored several books on both use-cases and agile methods. I found this book very practical as it focuses on textual use-cases as opposed to graphical views as in UML, for instance.
We dive straight in with the use case document and its different sections: Scope, main scenario, extensions, etc. Alistair helps with the writing style and provides two templates for the so-called casual and fully-dressed formats.
On the downside, I feel the process to collect and refine use-cases is somewhat less clear, but I am guessing this goes beyond the intended scope. I finally give it 3 stars. It is a good and practical book and a reference I will definitely keep in mind. On the downside, I still do not get how far to go with the requirements. Apr 30, Erich Oswald rated it really liked it. Opinionated but with a lot of helpful advice. Sep 11, Wayne rated it really liked it Shelves: software , non-fiction , engineering , computer-science.
Mar 29, Omar Trejo rated it it was ok. Practical methodology for comprehensive use cases. Jan 19, Mitzi Fox rated it liked it. Good if you're in the field albeit a bit dry, but gotta expect that with the subject Feb 02, Jim rated it it was ok.
It's unfortunate that the authors became too enamored with their own cleverness that they forgot to actually involve with consumers of their book. Use this on that rarest of occasions when you see that the steps in the use case are themselves white goals.
Use a clam, [clam i It's unfortunate that the authors became too enamored with their own cleverness that they forgot to actually involve with consumers of their book. Use a clam, [clam icon:], to mark a use case that needs to be merged with its calling use case. In the second snippet, what I suspect they were trying to say is "this function is too low-level to be a use case.
Nov 12, Deniss Ojastu rated it really liked it Shelves: software-development. The book describes the methodology of putting the software requirements in written through the use cases.
Very systematic and logical approach, clear and easy to understand guidelines for writing, quite good examples. Sometimes, the methodology as a whole feels too dogmatic and sets quite strict limits. I did not find suggestions for schematic icons too useful either.
Besides, the methodology feels a little bit outdated in the book was written in Overall, recommended to software anal The book describes the methodology of putting the software requirements in written through the use cases. Overall, recommended to software analysts and software team leads - along with some newer books on the software requirements methodology. View 2 comments. May 27, EOB rated it it was amazing.
These templates can work so well and robustly with test-driven development, a variety of flow-based planning methods, and classic BMP and ops planning, it's perfect for my kind of widely-scoped work.
Jul 29, Paulius rated it really liked it. Review: Why did I chose this book? So, it was quite easy to decide what to read. Book is dedicated to writing effective use cases. Simple and effective tips are placed in one book. You could follow book step by step and make a use case at the same moment although I didn't it.
For me as with 0 background in this area, book was perfect choice. Type of book: Self study guide. Goals: To know ho Review: Why did I chose this book? Goals: To know how to write effective use case. Tags: Use case.
Feb 03, Eric rated it it was amazing Shelves: usability , tech. This is one of the most useful technical books that i ever read. Cockburn presents a pragmatic, hands-on method for writing use cases. Based on 2 decades of practical experience. Go Green - We Care About the Environment We believe it is the responsibility of both individuals and corporations to be environmentally friendly. We're committed to environment-friendly practices throughout our company, and to leaving the smallest carbon footprint possible.
We support environment-friendly businesses whenever possible, and encourage you to do the same. Visit Our Blogs! How do I benefit from this eBook? The practical tips in this eBook will help you and your team:.
Can I benefit from this eBook without buying your software? We also do not have links that lead to sites DMCA copyright infringement. If You feel that this book is belong to you and you want to unpublish it, Please Contact us. Writing Effective Use Cases. Download e-Book. Posted on. Page Count. Alistair Cockburn, Alistair Cockburn,.
0コメント