Start reading Applying Use Cases: A Practical Guide (2nd Edition) on your Kindle in under a minute. Don't have a Kindle? Get your Kindle here.

Deliver to your Kindle or other device

 
 
 

Try it free

Sample the beginning of this book for free

Deliver to your Kindle or other device

Anybody can read Kindle bookseven without a Kindle devicewith the FREE Kindle app for smartphones, tablets, and computers.
Applying Use Cases: A Practical Guide (2nd Edition)
 
See larger image
 

Applying Use Cases: A Practical Guide (2nd Edition) [Kindle Edition]

Geri Schneider , Jason P. Winters
4.3 out of 5 stars  See all reviews (29 customer reviews)

Print List Price: CDN$ 51.99
Kindle Price: CDN$ 24.52 includes free international wireless delivery via Amazon Whispernet
You Save: CDN$ 27.47 (53%)

Formats

Amazon Price New from Used from
Kindle Edition CDN $24.52  
Paperback CDN $41.59  

Customers Who Bought This Item Also Bought


Product Description

From Amazon

With the emergence of the Unified Modeling Language (UML) over the last few years, developers new to the advantages of thorough software-engineering practices now have a better notational system for designing more effective software. To use UML effectively, you will want to create use cases, which help describe the requirements of a system. In their concise and very readable book, the authors of Applying Use Cases show how use cases can benefit all aspects of the software-design process and let you create better software in less time.

This guide provides a case study for a mail-order business (with some e-commerce as well) as its central example. Use cases define how actors (i.e., users) are defined for all the various components of a mail-order business, including inventory, accounting, and order fulfillment. The authors suggest that while use cases are particularly useful at the beginning of a project cycle--for assessing risks and setting project timetables, for instance--they are also useful for testing and deployment of systems (specifically, for creating documentation and help manuals). The sample use cases--and supporting design documents--are what's best in this text. --Richard Dragan

Product Description

Use case analysis is a methodology for defining the outward features of a software system from the user's point of view. Applying Use Cases, Second Edition, offers a clear and practical introduction to this cutting-edge software development technique. Using numerous realistic examples and a detailed case study, you are guided through the application of use case analysis in the development of software systems.

This new edition has been updated and expanded to reflect the Unified Modeling Language (UML) version 1.3. It also includes more complex and precise examples, descriptions of the pros and cons of various use case documentation techniques, and discussions on how other modeling approaches relate to use cases.

Applying Use Cases, Second Edition, walks you through the software development process, demonstrating how use cases apply to project inception, requirements and risk analysis, system architecture, scheduling, review and testing, and documentation. Key topics include:

  • Identifying use cases and describing actors
  • Writing the flow of events, including basic and alternative paths
  • Reviewing use cases for completeness and correctness
  • Diagramming use cases with activity diagrams and sequence diagrams
  • Incorporating user interface description and data description documents
  • Testing architectural patterns and designs with use cases
  • Applying use cases to project planning, prototyping, and estimating
  • Identifying and diagramming analysis classes from use cases
  • Applying use cases to user guides, test cases, and training material

An entire section of the book is devoted to identifying common mistakes and describing their solutions. Also featured is a handy collection of documentation templates and an abbreviated guide to UML notation.

You will come away from this book with a solid understanding of use cases, along with the skills you need to put use case analysis to work.


Product Details

  • Format: Kindle Edition
  • File Size: 4394 KB
  • Print Length: 272 pages
  • Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
  • Publisher: Que Publishing; 2 edition (March 31 2001)
  • Sold by: Amazon Digital Services, Inc.
  • Language: English
  • ASIN: B003YMNVCK
  • Text-to-Speech: Enabled
  • X-Ray:
  • Average Customer Review: 4.3 out of 5 stars  See all reviews (29 customer reviews)
  • Amazon Bestsellers Rank: #215,720 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
  •  Would you like to give feedback on images?


Customer Reviews

Most helpful customer reviews
1 of 1 people found the following review helpful
Format:Paperback
Over the last year I have come to love Use Cases ... I write them before embarking on any software development project, large or small. The first taste I got of Use Cases was in the "UML Distilled" book (Fowler, Scott).
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, rather than just providing some templates for producing Use Case documents without instructions on their use.
The best, and worst, thing about books in the Object Technology Series (of which "Applying Use Cases" and "UML Distilled" both belong to) is their brevity. The concepts are conveyed very clearly and concisely, but it feels like I should be getting more substance ... .
Overall, this is a wonderful book and belongs on the shelf of any Software Engineer or Project Manager. It goes well with "Extreme Programming Explained" and "A Practical Guide to Extreme Programming", two of my favorites in this genre.
Was this review helpful to you?
1 of 1 people found the following review helpful
5.0 out of 5 stars Useful as a refresher Nov. 12 2002
Format:Paperback
As someone who has followed the development of UML and Use Cases for the past several years and who is now confronted with a project needing definition, I find the Scheider-Winters book very helpful -- not only in applying Use Cases, but also in defining the project itself.
I chose this book because I know Geri Schneider-Winters as a professional (we worked together at UCSC Extension.) I was not disappointed.
Was this review helpful to you?
5.0 out of 5 stars Use Case Points June 22 2004
By A Customer
Format:Paperback
An excellent book. Gustav Karner did a really good job, finding the solution of estimating resources for object oriented projects.
Was this review helpful to you?
5.0 out of 5 stars Terrific resource March 8 2002
Format:Paperback
Though small, thin, and expensive, this books packs a ton of useful information. It is well worth the price. UML is a complex subject and the authors do a great job with clear examples of what use cases (to a midlevel depth of complexity) should look like. Yes, the story that goes along with it is a bit hokey, but it makes for light reading between the mass of valuable and important data. I expect to use this a reference for quite a while.
Was this review helpful to you?
4.0 out of 5 stars From the perspective of the experienced beginner May 17 2001
Format:Paperback
Given the proper instruction, working with use cases is not as hard as it may appear. Demonstrating them requires a large, detailed example to illustrate how complex structures can be reduced to understandable chunks. Therefore, the most critical part of any book on how to apply use cases is the choice of the system to model. That feature is what makes this book stand out.
The premise is that several people, with some experience in designing systems, but certainly not experts, decide to build an order processing system. Choosing a group of non-experts is a stroke of genius, since it allows the authors to use dialog based on the premise of learning as you go, which describes most of us. This approach makes it much easier to relate to their trials and tribulations as they plunge in over their head, only to be rescued by the proper applications of use cases.
Requirements are iteratively added as needed or discovered, demonstrating how iterative development is superior to others such as the waterfall. The developers are learning the background while constructing their system. Elaborating on their initial model is a slow and steady process, however it is not without the frequent step back. These glitches are presented in a realistic format with sections devoted to common mistakes made when using use cases.
A great deal of effort is also expended in describing how refined the use cases should be. One of the topics in the section on common mistakes is making the use cases too small. Like anything else, they can be split down to the point where they complicate rather than simplify. With no fixed rules to guide the process, you are forced to rely on more common sense notions. This is always hard, but some good, effective guidelines are given.
Read more ›
Was this review helpful to you?
3.0 out of 5 stars Was OK in its time Jan. 20 2001
By A Customer
Format:Paperback
Back when, this was probably an OK book for the real novice - easy reading. Nowadays there are better ones, the Cockburn and Kulak ones contain real information. Get this one as an adjunct to the others and for the real basic intro.
Was this review helpful to you?
5.0 out of 5 stars Very informative and to the point! Dec 29 2000
Format:Paperback
This book will get you up to speed very quickly w/ the needed information to successfully write and use "use Cases". Although this is just one piece of the UML puzzle, this is a great piece to start out with!
Was this review helpful to you?
3.0 out of 5 stars ehhh ... so-so Nov. 13 2000
By A Customer
Format:Paperback
Summary: If you've got plenty of $$ go ahead and buy it to get a good, simplistic start but you will need more. I've been doing requirements for quite a few years now and am convinced that use cases are the way to go especially for interactive systems. The key reason being that it forces the analyst to focus on WHAT the system should do rather than the HOW it should do it(I fall in that trap quite often). This particular book uses a different writing method, more story telling in nature. Some people may like it ... I don't care for it personally because the time spent reading Jane and Billy's annoyingly pleasant and simplistic banter could be better spent playing with my kids. It does, however, get around to giving a good academic introduction to the topic but the lack of examples severely hinders it from living up to a level of "practicality" to warrant the inclusion of the word in its title in my opinion. If you are a "just give me some guidelines and show me some good examples and get out of my way" kind of person, this book will make good kindling for your next BBQ -- especially if your software will involve any remotely complex scenarios. Perhaps the problem is that I tend to conceptualize systems in too complex a manner ... but it would be nice if the book helped in that regard as well by educating me relative to pitfalls that may lead me to overcomplicate things. In the end (couldn't finish the book) I find myself still looking for a good book mostly one loaded with realistic, practical, applicable examples.
Was this review helpful to you?
Want to see more reviews on this item?
Most recent customer reviews
Search Customer Reviews
Only search this product's reviews

Popular Highlights

 (What's this?)
&quote;
RUP is divided into four primary phases: inception, elaboration, construction, and transition. &quote;
Highlighted by 9 Kindle users
&quote;
One method for finding alternative paths is to go through the basic path line by line and ask questions: &quote;
Highlighted by 8 Kindle users
&quote;
A use case is a behavior of the system that produces a measurable result of value to an actor. &quote;
Highlighted by 8 Kindle users

Look for similar items by category