Commencez à lire Applying Use Cases: A Practical Guide (2nd Edition) sur votre Kindle dans moins d'une minute. Vous n'avez pas encore de Kindle ? Achetez-le ici Ou commencez à lire dès maintenant avec l'une de nos applications de lecture Kindle gratuites.

Envoyer sur votre Kindle ou un autre appareil


Essai gratuit

Découvrez gratuitement un extrait de ce titre

Envoyer sur votre Kindle ou un autre appareil

Désolé, cet article n'est pas disponible en
Image non disponible pour la
couleur :
Image non disponible

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

Geri Schneider , Jason P. Winters

Prix conseillé : EUR 30,58 De quoi s'agit-il ?
Prix éditeur - format imprimé : EUR 47,16
Prix Kindle : EUR 21,41 TTC & envoi gratuit via réseau sans fil par Amazon Whispernet
Économisez : EUR 25,75 (55%)

App de lecture Kindle gratuite Tout le monde peut lire les livres Kindle, même sans un appareil Kindle, grâce à l'appli Kindle GRATUITE pour les smartphones, les tablettes et les ordinateurs.

Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.


Prix Amazon Neuf à partir de Occasion à partir de
Format Kindle EUR 21,41  
Broché EUR 47,10  

Descriptions du produit

Présentation de l'éditeur

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.

Quatrième de couverture

Many projects struggle to define the specific functions of software, and end users often find that the final product does not perform as expected. Use cases allow analysts to identify the required features of a software system based on how each end user will use the system. This efficient and straightforward analysis process gives end users direct input into the design of the system that will serve them.

Applying Use Cases provides a practical and clear introduction to developing use cases, demonstrating their use via a continuing case study. Using the Unified Software Development Process as a framework and the Unified Modeling Language (UML) as a notation, the authors step the reader through applying use cases in the different phases of the process, focusing on where and how use cases are best applied.

Other highlights include:

  • A collection of realistic examples showing how to apply use cases, drawn from the authors' extensive experience in this area
  • A case study that offers insight into the common mistakes and pitfalls that can plague an object-oriented project
  • An illustration of the latest version of the UML notation for diagramming use cases
  • A practical "how-to" discussion on applying use cases to identify system requirements


Détails sur le produit

  • Format : Format Kindle
  • Taille du fichier : 4394 KB
  • Nombre de pages de l'édition imprimée : 272 pages
  • Utilisation simultanée de l'appareil : Jusqu'à 5 appareils simultanés, selon les limites de l'éditeur
  • Editeur : Que Publishing; Édition : 2 (31 mars 2001)
  • Vendu par : Amazon Media EU S.à r.l.
  • Langue : Anglais
  • Synthèse vocale : Activée
  • X-Ray :
  • Word Wise: Non activé
  •  Souhaitez-vous faire modifier les images ?

En savoir plus sur les auteurs

Découvrez des livres, informez-vous sur les écrivains, lisez des blogs d'auteurs et bien plus encore.

Commentaires en ligne

Il n'y a pas encore de commentaires clients sur
5 étoiles
4 étoiles
3 étoiles
2 étoiles
1 étoiles
Commentaires client les plus utiles sur (beta) 4.1 étoiles sur 5  34 commentaires
36 internautes sur 38 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Excellent and Practical 2 novembre 1998
Par - Publié sur
This book provides an excellent introduction to practical application of use cases. Most UML-related books hardly devote a chapter to use cases and use examples which are so elementary they provide little practical value. Applying Use Cases is devoted entirely to the subject of use cases (analysis, rather than design). It touches on design at the boundary between analysis and design and discusses this transitition point. It discusses use case development as an iterative cycle which doesn't end when design begins. Design may uncover more use cases when then need to be anaylzed and the developer(s) must iterate through use cases again.
The book uses an online ordering system as an example for building use cases. It presents this fictitious project from inception through to the point of design. This project is large enough that it works well with the topic. It provides enough detail to understand how important use cases are and how much effort should be devoted to them. However, it is not so complex that a UML beginner would have difficulty following it. It is fairly easy reading for a technical book and can be completed in a day. Reading it twice was helpful for me.
The little dialogs between the make-believe project team is perhaps a little overdone, but I think it works well in the context of the subject. This presentation style presents the "roots" of use cases fairly well. These types of dialogs are almost always part of the process even though they go undocumented.
As with all methodologies, UML included, the analysis of requirements is the most important step. Doing a poor job on use cases will lead to a poorly implemented software system. This book is the best I've seen covering use cases, the UML analysis method. I highly recommend it. I would like to see a follow-on book with a much more complex example which delves into more detail on use cases.
34 internautes sur 37 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 Learing abstraction by example 18 janvier 2000
Par Charles Ashbacher - Publié sur
For every abstraction used in the development of software, there is a definition and a set of rules concerning how to use it. Unfortunately, being an abstraction, the definition is often open to interpretation and the rules are nebulous guidelines. The concept of use cases is one such abstraction. Therefore, the best way to explain them is to use them in an understandable context. That is the approach taken in this book.
The scenario is that a group of designers want to build a "simple" online ordering system. They begin with the proverbial conversation over coffee which contained the usual, "that system stinks and we could do better" phrase. From there, a general, but fairly complete process is presented. Every step in the sequence of requirements definitions is given. Many potential use cases are put forward, which is excellent, as this allows the authors to demonstrate the culling process, whereby some use cases are eliminated and others are combined.
The presentation is a combination of simulated dialog between the principals and more formal techniques of requirements capture such as actors and their diagrams. One thing that impressed me was the accuracy of the dialog. Anyone who has participated in the requirements capture process will experience a flashback. It is written with the beginner in mind, as very little programming background is needed to understand it. This is a thorough demonstration of how to create and apply use cases, without the depth that requires more formal notational techniques.
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. However, you still may not be able to offer a precise definition.
31 internautes sur 35 ont trouvé ce commentaire utile 
5.0 étoiles sur 5 This is a great book and fun to read 8 octobre 1999
Par Un client - Publié sur
This book will give you a great foundation for applying use cases and does so in a format that is to the point and user friendly. The book is only about 180 pages and does well with this amount of space. It doesn't attempt any great tangents of though or reason bit stays focussed on use cases and the relevant material that is associated with the subject. Two points that could be strengthened in the book are: 1) the level of abstraction that you are applying to the use case at a particular time and how this may evolve over time, 2) there could be a little more structure provided for traceability throughout the project lifecycle. Both points are mentioned but the authors never really provide a structured mechanism to handle these issues, which would be a complex requirement for all but he simplest projects. I thought the ongoing fictional case study approach was a great idea. It allowed the reader to catch their breath along the way and also provides for some contextual insight that can be missed in a strictly academic format. Although not directly related to this title, "Designing Object-Oriented Software" by Wirfs-Brock, et. al. is also right on the nose with using a responsibility driven approach and CRC cards. It's a good read by itself but especially in combination with Applying Use Cases.
15 internautes sur 15 ont trouvé ce commentaire utile 
3.0 étoiles sur 5 There's a good, more practical alternative 5 juillet 2000
Par Andreas Pizsa - Publié sur
" Applying Use Cases : A Practical Guide" is not bad, but when I browsed through several Use Case books at a local book store, I decided to buy "Use Cases: Requirements in Context", which - to me - seems to be a far more practical book than this one.
Check out "Use Cases: Requirements in Context" before you buy any book on this topic.
9 internautes sur 9 ont trouvé ce commentaire utile 
4.0 étoiles sur 5 From the perspective of the experienced beginner 17 mai 2001
Par Charles Ashbacher - Publié sur
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.
I found this book to be a superb introduction to the power of use cases, being easy to follow. Everyone from beginners to veterans can relate to the principals as they struggle to turn their good idea into an implemented one. You find yourself rooting for them as they move ever closer to their brass ring of success. In that respect, it is less like a technical book and more like a novel.
Ces commentaires ont-ils été utiles ?   Dites-le-nous

Discussions entre clients

Le forum concernant ce produit
Discussion Réponses Message le plus récent
Pas de discussions pour l'instant

Posez des questions, partagez votre opinion, gagnez en compréhension
Démarrer une nouvelle discussion
Première publication:
Aller s'identifier

Rechercher parmi les discussions des clients
Rechercher dans toutes les discussions Amazon

Rechercher des articles similaires par rubrique