Prix bas
CHF49.20
Habituellement expédié sous 5 à 7 jours ouvrés.
Preface.
Why bother with the UML?
Structure of the book.
Changes for the Third Edition.
Acknowledgements.
1. Introduction.
What Is the UML?
Ways of Using the UML.
How We Got to the UML.
Notations and Meta-Models.
UML Diagrams.
What is Legal UML?
The Meaning of UML.
UML is not enough.
Where to Start with the UML.
Looking for More Information.
2. Development Process.
Iterative and Waterfall Processes.
Predictive and Adaptive Planning.
Agile Processes.
Rational Unified Process.
Fitting a Process to a Project.
Fitting the UML into a process.
Understanding Legacy Code.
Choosing a Development Process.
Where to Find Out More.
3. Class Diagrams: The Essentials.
Properties.
Attributes.
Associations.
Multiplicity.
Programming Interpretation of Properties.
Bi-directional Associations.
Operations.
Generalization.
Notes and Comments.
Dependency.
Constraint Rules.
When to Use Class Diagrams.
Where to Find Out More.
4. Sequence Diagrams.
Creating and deleting participants.
Loops, conditionals and the like.
Synchronous and Asynchronous Calls.
When to use Sequence Diagrams.
5. Class Diagrams: Advanced Concepts.
Keywords.
Responsibilities.
Static Operations and Attributes.
Aggregation and Composition.
Derived Properties.
Interfaces and Abstract Classes.
Read Only and Frozen.
Reference Objects and Value Objects.
Qualified Associations.
Classification and Generalization.
Multiple and Dynamic Classification.
Association Class.
Template (Parameterized) Class.
Enumerations.
Active Class.
Visibility.
Messages.
6. Object Diagrams.
When to use Object Diagrams.
7. Package Diagrams.
Packages and Dependencies.
Package Aspects.
Implementing Packages.
Where to Find Out More.
When to Use Package Diagrams.
8. Deployment Diagrams.
When to use deployment diagrams.
9. Use Cases.
Content of a Use Case.
Use Case Diagrams.
Levels of Use Cases.
Use cases and features (or stories).
When to Use Use Cases.
Where to Find Out More.
10. State Machine Diagrams.
Internal Activities.
Activity States.
Superstates.
Concurrent States.
Implementing State Diagrams.
When to Use State Diagrams.
Where to Find Out More.
11. Activity Diagrams.
Decomposing an action.
Partitions.
Signals.
Tokens.
Flows and Edges.
Pins and Transformations.
Expansion Regions.
Flow Final.
Join Specifications.
And there's more.
When to Use Activity Diagrams.
Where to Find Out More.
12. Communication Diagrams.
When to use Communication Diagrams.
13. Composite Structures.
When to Use Composite Structures.
14. Component Diagrams.
When to use Component Diagrams....
Auteur
Martin Fowler is an independent consultant who has applied objects to pressing business problems for more than a decade. He has consulted on systems in fields such as health care, financial trading, and corporate finance. His clients include Chrysler, Citibank, UK National Health Service, Andersen Consulting, and Netscape Communications. In addition, Fowler is a regular speaker on objects, the Unified Modeling Language, and patterns.
Texte du rabat
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.
Résumé
Gets students thinking about efficient object-oriented software design using UML 2.0. The book describes the major UML 2.0 diagram types, what they are intended to do, and the basic notation involved in creating and deciphering them, with a concise format.
Contenu
Preface.
Why bother with the UML?
Structure of the book.
Changes for the Third Edition.
Acknowledgements.
1. Introduction.
What Is the UML?
Ways of Using the UML.
How We Got to the UML.
Notations and Meta-Models.
UML Diagrams.
What is Legal UML?
The Meaning of UML.
UML is not enough.
Where to Start with the UML.
Looking for More Information.
2. Development Process.
Iterative and Waterfall Processes.
Predictive and Adaptive Planning.
Agile Processes.
Rational Unified Process.
Fitting a Process to a Project.
Fitting the UML into a process.
Understanding Legacy Code.
Choosing a Development Process.
Where to Find Out More.
3. Class Diagrams: The Essentials.
Properties.
Attributes.
Associations.
Multiplicity.
Programming Interpretation of Properties.
Bi-directional Associations.
Operations.
Generalization.
Notes and Comments.
Dependency.
Constraint Rules.
When to Use Class Diagrams.
Where to Find Out More.
4. Sequence Diagrams.
Creating and deleting participants.
Loops, conditionals and the like.
Synchronous and Asynchronous Calls.
When to use Sequence Diagrams.
5. Class Diagrams: Advanced Concepts.
Keywords.
Responsibilities.
Static Operations and Attributes.
Aggregation and Composition.
Derived Properties.
Interfaces and Abstract Classes.
Read Only and Frozen.
Reference Objects and Value Objects.
Qualified Associations.
Classification and Generalization.
Multiple and Dynamic Classification.
Association Class.
Template (Parameterized) Class.
Enumerations.
Active Class.
Visibility.
Messages.
6. Object Diagrams.
When to use Object Diagrams.
7. Package Diagrams.
Packages and Dependencies.
Package Aspects.
Implementing Packages.
Where to Find Out More.
When to Use Package Diagrams.
8. Deployment Diagrams.
When to use deployment diagrams.
9. Use Cases.
Content of a Use Case.
Use Case Diagrams.
Levels of Use Cases.
Use cases and features (or stories).
When to Use Use Cases.
Where to Find Out More.
**10. S…