Facebook Twitter Pinterest
Gebraucht kaufen
EUR 28,93
Gebraucht: Sehr gut | Details
Verkauft von Shoppers-Paradise
Zustand: Gebraucht: Sehr gut
Kommentar: Sehr guter Zustand. Nur minimale Lagerspuren. Dieser Artikel wird direkt von Amazon versendet. Der komplette Kundenservice erfolgt durch Amazon.
Möchten Sie verkaufen?
Zur Rückseite klappen Zur Vorderseite klappen
Hörprobe Wird gespielt... Angehalten   Sie hören eine Hörprobe des Audible Hörbuch-Downloads.
Mehr erfahren
Dieses Bild anzeigen

Use Cases: Patterns and Blueprints: Patterns and Modeling Problems (Software Patterns) (Englisch) Gebundene Ausgabe – 12. November 2004

Alle Formate und Ausgaben anzeigen Andere Formate und Ausgaben ausblenden
Neu ab Gebraucht ab
Gebundene Ausgabe
"Bitte wiederholen"
EUR 41,28 EUR 5,27
3 neu ab EUR 41,28 11 gebraucht ab EUR 5,27
click to open popover

Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.

  • Apple
  • Android
  • Windows Phone

Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.

Jeder kann Kindle Bücher lesen — selbst ohne ein Kindle-Gerät — mit der KOSTENFREIEN Kindle App für Smartphones, Tablets und Computer.




This book offers a patterns-based approach to producing better use cases. Thedesign patterns approach has become popular because it allows softwarepractitioners to address recurring problems by applying a catalog of provensolutions. Use cases have gained widespread popularity because they allow asystem designer to determine how software will ultimately be "used" by thesystem's customer/end-user before the process of coding even begins. For allof their benefit and widespread acceptance, use cases are still misunderstood bya great number of professionals who could benefit from their effectivedeployment. This book marries the best of design patterns and use cases. Theauthors use the patterns approach to demystify use cases, and provide a provenframework for helping organizations build software more efficiently. The majorteaching points are supported by concrete, real-world examples.


"Gunnar and Karin have not only defined a large collection of use-case patterns and examples of how specific usages are to be modeled in a use-case model, they have also provided an accurate, complete, and comprehensible description of the constructs used in use-case modeling... I am impressed by this book."

—From the Foreword by Ivar Jacobson

Employ the proven concept of design patterns to build more accurate, usable, and maintainable use-case models

This book brings together dozens of proven patterns for creating use cases that more accurately reflect real requirements, are easier to translate into working systems, and are simpler to maintain. Utilizing these patterns, architects, analysts, engineers, and managers can leverage decades of hard-earned knowledge to achieve far better results, far more quickly.

The authors carefully describe how each pattern works, what problems it is intended to solve, and the consequences associated with using it. All patterns are supported with detailed examples and platform-independent class models that demonstrate how they may be realized. All constructs and diagrams reflect the current UML 2.0 standard. This book also includes an insightful use-case primer that will be indispensable both to novices and veteran modelers seeking to become more effective.

Coverage includes

  • Modeling rules that lead to more comprehensible, maintainable, and correct models

  • Patterns for structuring, layering, mapping, sequencing, and viewing use cases more effectively

  • Blueprints for security, legacy integration, data input/ output, task scheduling, and reporting

  • Constructing use cases that separate mandatory elements from optional parts that can be delivered separately

  • Incorporating business rules in use-case modeling

  • Practical techniques for documenting use cases more effectively

  • When to use multiple patterns and blueprints together

  • Identifying and avoiding eight common mistakes in use-case modeling: guidance for designers and reviewers

  • Examples from a wide range of application domains

Rely on this book as the world's #1 reference to reusable use-case solutions—and as a catalyst for inspiration in all your use-case modeling projects.

© Copyright Pearson Education. All rights reserved.

Alle Produktbeschreibungen


Es gibt noch keine Kundenrezensionen auf Amazon.de
5 Sterne
4 Sterne
3 Sterne
2 Sterne
1 Stern

Die hilfreichsten Kundenrezensionen auf Amazon.com (beta)

Amazon.com: 5.0 von 5 Sternen 3 Rezensionen
7 von 7 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen The book to improve your "use" of use cases... 22. Mai 2005
Von Thomas Duff - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe
If you're having trouble translating all the book knowledge of use cases into practical application, check out Use Cases Patterns and Blueprints by Gunnar Overgaard and Karin Palmkvist. A very nice work...

Chapter List:

Part 1 - Introduction: Use-Case Patterns and Blueprints; Using Patterns and Blueprints in Use-Case Model Development

Part 2 - Use Cases: Use-Case Modeling - An Introduction; Use Cases; Modeling the System Environment; Structuring a Use-Case Model; Include - Reusing Existing Use Cases; Extend - Expanding Existing Use Cases; Include vs. Extend; More on Extend and Extension Points; Use-Case Generalization - Classification and Inheritance; Actor Generalization - Overlapping Roles; Describing Use Cases; Documenting a Use-Case Model; Mapping Use Cases onto Classes

Part 3 - Use-Case Patterns: Business Rules; Commonality; Component Hierarchy; Concrete Extension or Inclusion; CRUD; Large Use Case; Layered System; Multiple Actors; Optional Service; Orthogonal Views; Use-Case Sequence

Part 4 - Use-Case Blueprints: Access Control; Future Task; Legacy System; Login and Logout; Message Transfer; Passive External Medium; Report Generalization; Stream Input; Translator

Part 5 - Common Mistakes: Alternative Flow as Extension; Business Use Case; Communicating Use Cases; Functional Decomposition; Micro Use Cases; Mix of Abstraction Levels; Multiple Business Values; Security Levels with Actors

Glossary; References; Index

The feature I often find most useful in programming books is the liberal use of code samples that can be "appropriated" for your own use. But that feature seems to disappear quite often when you get into design work. You have to learn the methodology first, and then you're on your own for trying to figure out how it applies to your system. No samples, no code to steal, it's just slog away and hope you get it right. This book allows you to break out of that pattern (no pun intended) when it comes to writing up use cases. Overgaard and Palmkvist have taken their multiple years of experience with use cases and distilled down a number of repeating "patterns" that are seen over and over in many business systems. They then name the pattern, explain the type of situation that calls for it, shows the way it would be written up, and then they apply it to a few example uses. If you're the type of programmer or designer who likes to "look at the answers" to figure out how something is done, this book provides quite a few "answers" for you to study and learn from.

While the book is touted as being for all levels, I don't know that I'd recommend this as a learning guide for use cases. They do cover the basics, but it just didn't strike me as a good tutorial. Having said that, this should be the *second* book you buy in order to take your ability to work with use cases to a higher level.
5 von 5 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Solid help for real-life situations 29. Juni 2005
Von uniq - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe
This is a very informative, precise, and dense book. The authors uncover misconceptions and discuss real-life examples. They carefully and convincingly direct us to the best practices in the field. Every recommendation, pattern, and anti-pattern is supported by a detailed explanation of the tradeoffs and even suggestion of a "Way Out", i.e. how to migrate from an anti-pattern. The patterns are not contrived and are inspired by real-life cases: access control, CRUD, login/logout, multiple actors, optional service, use case squence, and others.

I recommend this volume to everyone who works closely with requirements, not just to those who creates them. This includes business and requirements analysts, architects, designers, and, of course, quality assurance practitioners: when the entire project team is familiar with how to create, maintain, and interpret use cases, the chances for success are so much higher.

On a slightly negative side the language feels a bit stiff, lacking elegance. Still unambiguous in the technical sense, some sentences are a bit hard to read and should have been re-written for better readability. For example, on page 89 we read "However, would not one extend relationship referencing one extension point, which in its turn references all these locations, also do the trick?", or on page 63 ("Otherwise, there is a risk that later descriptions will have to be made according to an include relationship that actually should not have been available because later descriptions show that the flows have precious little in common."), or on page 64 ("Note that the end section of an inclusion use case explicitly states which information is available in the base use case after the inclusion -- that is, the result of the included flow, if any, because this is important information when reusing this use case ").
4 von 6 Kunden fanden die folgende Rezension hilfreich
5.0 von 5 Sternen Best book on Use Cases 12. März 2006
Von Alberto Pedroso - Veröffentlicht auf Amazon.com
Format: Gebundene Ausgabe
This has to be the best book on use cases I have ever read. Whether you are new to use cases or an experienced practitioner, this book will become your Bible on the subject. It is an invaluable reference for writing quality use cases, which is not as trivial as it might seem.
Waren diese Rezensionen hilfreich? Wir wollen von Ihnen hören.