- Outlet Anciennes collections, fin de séries, articles commandés en trop grande quantité, … découvrez notre sélection de produits à petits prix Profitez-en !
- Idées cadeaux de Noël Retrouvez toutes nos suggestions, rien que pour vous.
- Rentrée scolaire : trouvez tous vos livres, cartables, cahiers, chaussures, et bien plus encore... dans notre boutique dédiée
UML Distilled: A Brief Guide to the Standard Object Modeling Language (Anglais) Broché – 15 septembre 2003
- Choisissez parmi 17 000 points de collecte en France
- Les membres du programme Amazon Premium bénéficient de livraison gratuites illimitées
- Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
- Sélectionnez cette adresse lors de votre commande
Offres spéciales et liens associés
Produits fréquemment achetés ensemble
Les clients ayant acheté cet article ont également acheté
Descriptions du produit
Présentation de l'éditeur
Pressured with tight deadlines, application developers do not have the luxury of keeping completely up-to-date with all of the latest innovations in software engineering. Once in a great while, a tremendous resource comes along that helps these professionals become more efficient. The first two editions of UML Distilled have been perennial best-sellers because of their concise, yet thorough, nature. This eagerly-anticipated third edition allows you to get acquainted with some of the best thinking about efficient object-oriented software design using the latest version of the industry-standard for modeling software: UML 2.0. The author has retained the book's convenient format that has made it an essential resource for anyone who designs software for a living. The book describes all the major UML 2.0 diagram types, what they are intended to do, and the basic notation involved in creating and deciphering them. A true treasure for the software engineering community.
Quatrième de couverture
- Would you like to understand the most important elements of Class diagrams? (See page 35.)
- Do you want to see the new UML 2.0 interaction frame notation for adding control flow to sequence diagrams (see page 58) and the unofficial notation that many prefer? (See page 60.)
- Do you want to know what changes have been made to all versions of the UML? (See page 151.)
- Do you want a quick reference to the most useful parts of the UML notation? (See the inside covers.)
- Do you want to find out what diagram types were added to the UML 2.0 without wading through the spec? (See page 11.)
More than 300,000 developers have benefited from past editions of UML Distilled. This third edition is the best resource for quick, no-nonsense insights into understanding and using UML 2.0 and prior versions of the UML.
Some readers will want to quickly get up to speed with the UML 2.0 and learn the essentials of the UML. Others will use this book as a handy, quick reference to the most common parts of the UML. The author delivers on both of these promises in a short, concise, and focused presentation.
This book describes all the major UML diagram types, what they're used for, and the basic notation involved in creating and deciphering them. These diagrams include class, sequence, object, package, deployment, use case, state machine, activity, communication, composite structure, component, interaction overview, and timing diagrams. The examples are clear and the explanations cut to the fundamental design logic.
If you are like most developers, you don't have time to keep up with all the new innovations in software engineering. This new edition of Fowler's classic work gets you acquainted with some of the best thinking about efficient object-oriented software design using the UML--in a convenient format that will be essential to anyone who designs software professionally.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Meilleurs commentaires des clients
C'est ausi sa faiblesse, si l'on cherche une information très détaillée.
Commentaires client les plus utiles sur Amazon.com (beta)
The first chapter is an introduction to UML, including some short history on the language. The second chapter covers the Development Process with a quick overview of a couple of them - i.e. Agile, RUP, ...- followed by some guidance on choosing the right one.
The following chapters cover the main UML diagrams, respectively, the Class, Sequence, Object, Package, Deployment, Use Case, State Machine, Activity, Communication, Composite Structure, Component, Collaboration, Interaction Overview and Timing Diagrams. At the end, there is an appendix that summarizes the changes between UML versions.
Not all of the diagrams get in-depth coverage. Whereas Class Diagrams get the most attention of the author with two chapters specifically dedicated to them, Object, Deployment, Communication, Composite Structures, Component, Collaboration, Interaction Overview and Timing Diagrams get only a few pages, between two and four. Some of them are just limited to the sample diagrams that illustrate the chapter, with no or little text to support them. Rather than a shortcoming, this seems to be ensuing from the author's willingness to have the book limited to a few pages - 150 exactly, without the appendix -, covering what he considers to be essential.
As such, this book is no replacement for the three classic UML books, i.e. the User's Guide, the Reference Manual and the Unified Process of the Booch/Jacobson/Rumbaugh Object Technology Series that the reader, in my opinion, will anyway have to go through until he/she gains sufficient working proficiency with the language. If the reader's intention is so, he/she'll be better inspired reading "UML Distilled" after, or better, in parallel with the User's Guide, diagram after diagram and have a look at the Reference Manual on selected dictionary terms, as necessary. The Unified Process book can be read independently.
This is not a book an OOA/OOD. As prerequisite, the reader is expected to be comfortable enough with OO concepts such as Class, Object, Relationship, Aggregation, Composition, Inheritance, etc. Although not required, working proficiency with a former OO modeling method - e.g. Fusion, in my case - will help.
One thing I must say is that I found the coverage of 'Development Process' (Ch 2) very sketchy and superficial, and most probably it does not even belong in a book so focussed in being used as a reference for a software project.
There is only one more thing which I expected from this book. Different UML diagrams are sketched and used in different stages of a project, if only these were overlapped with RUP project phases (inception, elaboration, construction and transition) along with a representative of other documents used in those phases the use of the UML diagrams could have been realized from a better perspective.
I would highly recommend the book 'Building J2EE Applications with RUP' (Peter Eeles, Kelli Houston and Wojtek Kozaczynski) for the J2EE practitioners, these two books complement each other very well in the J2EE/RUP world.
I must confess that I didn't know UML at all when I picked up this book. I just had this simple question in mind: What the heck is UML anyway? Now that I have finished reading it, I feel like to give the book a score of 90 out of 100 for the answer it provides.
Numbered in 180 or so pages, the book really is a feather-weight compared with its peers in the same series such as _The Unified Software Development Process_. With wide margins on both sides, texts are printed in bigger fonts than what we normally see in technical books. Adding the neatly drawn diagrams, and we have a book with tremendous visual appeal to a busy professional who, after a day's hard work with the computer, just wants to read something less intimidating and demanding than a reference manual while still catching up with the trend in technology. I am talking about myself here. In this regard, the book suits my need perfectly.
I particularly enjoy the author's sense of humor, notably in the light-hearted presentation of the brief history of UML, which is part of Chapter 1. Chapter 2, titled 'An Outline Development Process', serves as a road map to the chapters that follow. By outlining the development process in four major phases (inception, elaboration, construction and transition), the author not only brings up important components in UML such as 'use cases' and class diagram, but also offers a good deal of sound advices on software engineering based on his own experience, which I find invaluable.
One thing I am not completely satisfied with is the example used in Chapter 3 ('Use Cases'. The author makes a well-intent, but ill-planned, attempt to illustrate the concepts in use cases with a diagram of a financial trading system, which, however, is totally foreign to me. Although I can understand that people like to pick examples from their past work, I must disagree on the author's choice in this case. Another area that can be improved in the book is the diagrams, which I feel are simply thrown at my face in one piece -- mixed with annotation marks in some cases (e.g., the class diagram on p.50) -- to save the space, I assume. Novices like me would have a hard time telling the annotation marks apart from the diagram at the beginning. In addition, to make the diagrams easier to follow, complex ones such as the class diagram on p.50 might be better presented in several steps (e.g., first disassembled, then assembled together).
Copyright (C) 1999 by Huayong Yang.
Definitly a classic.