Applying Use Cases: A Practical Guide

Geri Schneider and Jason P. Winters

“I like this book because it teaches me a lot about use cases, and I can read it without having to use a dictionary to find the “big” words.” Richard, Sacramento, CA.“My favorite aspect of “Applying Use Cases” is how it follows a hypothetical project from Inception to Transition phases. The authors provide the reader with a clear idea of how Use Cases fit into the software development process as a whole.” Scott, Monterey, CA.

“After reading through the sixth chapter of this book, the light bulb goes on, and suddenly you start to understand how everything fits together using UML and Unified Process. This book is the missing link for UP and UML”. Linus, Alexandria, VA.

“Great book for a practical and concise introduction to use cases.” Chetah, Austin, TX.

“Use cases are sometimes very hard to teach, as is the case with most abstractions. In this book the abstract is made concrete and if you read it you will learn a lot about use cases.” Charles, Hiawatha, IA.

This book is available in several editions. Click on an image to order your copy:

US English	Japanese	Chinese	Polish
	Applying Use Cases Japanese Edition, amazon.co.jp	Applying Use Cases Chinese Edition, china-pub.com	Applying Use Cases Polish Edition, ksiegarnia4u.pl

3 Responses to “ Applying Use Cases: A Practical Guide ”

alex Dec 30th, 2009 at 3:45 pm

I have searched high and low to find an answer to this question. Not sure if this is the right place to ask but here goes.
My development team is embarking on implementing an N-Tier architecture. Should this impact how we document requirements? Currently we generate use cases, business rules, functional & non-functional requirements. I am not convinced that the way we approach requirements should change because there is a change in approach to architecture and development. What are your thoughts?
admin Dec 30th, 2009 at 4:10 pm

Hi Alex -

You are correct. You should not change the way you document your requirements.

You may find the need for additional non-functional requirements, especially if the N-tiers are to be distributed. Think about if you need additional requirements in the areas of (for example) response times, other performance requirements, network load, database load, and consider if you need transaction management.

Best!

Geri
Amanuel Tekalign Feb 10th, 2010 at 12:34 pm

Hi Mrs.Winters how are you? I am Student of HilCoE from Master of Software Engineering class. Thank you for your wonderful presentation last time. I do have so many questions first i want to have contact with you.
thanks
aman

Resources for Business Analysts

Helping you create a Successful Career as a Business Analyst