The Unified Modeling Language Reference Manual

1 The UnifiedModeling LanguageReference Manual The UnifiedModeling LanguageReference Manual James RumbaughIvar JacobsonGrady Booch ADDISON-WESLEY An imprint of Addison Wesley Longman, Inc. Reading, Massachusetts Harlow, England Menlo Park, CaliforniaBerkeley, California Don Mills, Ontario SydneyBonn Amsterdam Tokyo Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book and Addison-Wesley was aware of a trademark claim, the designations have been printed in initial caps or all Modeling Language , UML, and the UML cube logo are trademarks of the Object Management Group. Some material in this book is derived from the Object Management Group UML Specification documentation. Used by permission of the Object Management authors and publisher have taken care in the preparation of this book but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions.

2 No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained publisher offers discounts on this book when ordered in quantity for special sales. For more information, please contact:AWL Direct SalesAddison Wesley Longman, Jacob WayReading, Massachusetts 01867(781) 944-3700 Visit AW on the Web: Library of Congress Cataloging-in-Publication Data Rumbaugh, Unified Modeling Language Reference Manual / James Rumbaugh, Ivar Jacobson, Grady cm. (The Addison-Wesley object technology series)Includes bibliographical references and 0-201-30998-X 1. Computer software Development. 2. UML (Computer science) I. Jacobson, Ivar. II. Booch, Grady. III. Title. IV. Series. 1999 dc21 98-33392 CIPC opyright 1999 by Addison Wesley Longman, rights reserved.

3 No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior consent of the publisher. Printed in the United States of America. Published simultaneously in Editor: J. Carter ShanklinProject Editor: Krysia BebickEditorial Assistant: Kristin EricksonProduction Manager: Jacquelyn YoungCopy Editor: Arlene RichmanCompositor: James RumbaughCover Designer: Simone R. PaymentISBN 0-201-30998-XText printed on recycled and acid-free 2 3 4 5 6 7 8 9 10 MA 03 02 01 00 99 98 First printing, December 1998 For Madeline, Nick and Alex Jim vii Contents Preface .. xi Goals .. xiOutline of the Book .. xiiEncyclopedia Article Formatting Conventions .. xiiiSyntax Conventions .. xivCD .. xvFor More Information .. xvAcknowledgments.

4 Xvi Part 1: Background Chapter 1: UML overview .. 3 Brief Summary of UML.. 3 UML History .. 4 Goals of UML .. 8 UML Concept Areas .. 9 Syntax of Expressions and Diagrams .. 11 Chapter 2: The Nature and Purpose of Models .. 13 What Is a Model? .. 13 What Are Models For? .. 13 Levels of Models .. 15 What Is in a Model? .. 17 What Does a Model Mean? .. 19 viiiContents Part 2: UML Concepts Chapter 3: UML Walkthrough .. 23 UML Views .. 23 Static View.. 25 Use Case View .. 26 Interaction View .. 27 State Machine View .. 30 Activity View .. 31 Physical Views .. 32 Model Management View.. 36 Extensibility Constructs .. 37 Connections Among Views .. 38 Chapter 4: Static View .. 41 overview .. 41 Classifiers.. 42 Relationships .. 45 Associations .. 47 Generalization .. 51 Realization.. 54 Dependencies .. 56 Constraint .. 58 Instances.

5 59 Chapter 5: Use Case View .. 63 overview .. 63 Actor .. 63 Use Case .. 64 Chapter 6: State Machine View .. 67 overview .. 67 State Machine .. 67 Event .. 68 State .. 70 Transition .. 71 Composite States ..75 Chapter 7: Activity View .. 81 overview .. 81 Activity Diagram..81 Activities and Other Views .. 84 Contentsix Chapter 8: Interaction View .. 85 overview .. 85 Collaboration .. 85 Interaction .. 86 Sequence Diagram .. 87 Activation.. 88 Collaboration Diagram .. 89 Patterns .. 91 Chapter 9: Physical Views .. 93 overview .. 93 Component .. 93 Node .. 94 Chapter 10: Model Management View .. 97 overview .. 97 Package.. 97 Dependencies on Packages .. 98 Access and Import Dependency .. 98 Model and Subsystem .. 100 Chapter 11: Extension Mechanisms .. 101 overview .. 101 Constraint .. 101 Tagged Value .. 102 Stereotypes.

6 103 Tailoring UML .. 104 Chapter 12: UML Environment .. 105 overview .. 105 Semantics Responsibilities .. 105 Notation Responsibilities .. 106 Programming Language Responsibilities .. 107 Modeling with Tools .. 108 Part 3: Reference Chapter 13: Encyclopedia of Terms .. 113 Chapter 14: Standard Elements .. 499 xContents Part 4: Appendices Appendix A: UML Metamodel .. 515 UML Definition Documents .. 515 Metamodel Structure .. 515 Foundation Package .. 516 Behavioral Elements Package .. 516 Model Management Package .. 517 Appendix B: Notation Summary .. 519 Appendix C: Process Extensions .. 531 Tailoring the UML .. 531 Software Development Process Extensions .. 531 Business Modeling Extensions.. 534 Bibliography .. 537 Index .. 539 xi Preface Goals This book is intended to be a complete and useful Reference to the Unified Model-ing Language (UML) for the developer, architect, project manager, system engi-neer, programmer, analyst, contracting officer, customer, and anyone else whoneeds to specify, design, build, or understand complex software systems.

7 It pro-vides a full Reference to the concepts and constructs of UML, including their se-mantics, syntax, notation, and purpose. It is organized to be a convenient butthorough Reference for the working professional developer. It also attempts to pro-vide additional detail about issues that may not be clear from the standards docu-ments and to provide a rationale for many decisions that went into the book is not intended as a guide to the UML standards documents or to theinternal structure of the metamodel contained in them. The details of the meta-model are of interest to methodologists and UML tool builders, but most otherdevelopers have little need for the arcane details of the Object Management Group(OMG) documents. This book provides all the details of UML that most develop-ers need; in many cases, it makes information explicit that must otherwise besought between the lines of the original documents.

8 For those who do wish toconsult the source documents, they are included on the accompanying book is intended as a Reference for those who already have some under-standing of object-oriented technology. For beginners, the original books by usand by other authors are listed in the bibliography; although some of the notationhas changed, books such as [Rumbaugh-91], [Booch-94], [Jacobson-92], and[Meyer-88] provide an introduction to object-oriented concepts that is still validand therefore unnecessary to duplicate here. For a tutorial introduction to UMLthat shows how to model a number of common problems, see The Unified Model-ing Language User Guide [Booch-99]. Those who already know an object-orientedmethod, such as OMT, Booch, Objectory, Coad-Yourdon, or Fusion, should beable to read the Reference Manual and use it to understand UML notation and xiiPreface semantics; to learn UML quickly, they may nevertheless find it useful to read the User Guide.

9 UML does not require a particular development process, and this book does notdescribe one. Although UML may be used with a variety of developmentprocesses, it was designed to support an iterative, incremental, use-case drivenprocess with a strong architectural focus the kind we feel is most suitable for thedevelopment of modern, complex systems. The Unified Software Development Pro-cess [Jacobson-99] describes the kind of process we believe complements the UMLand best supports software development. Outline of the Book The UML Reference Manual is organized into three parts: an overview of UML his-tory and of Modeling , a survey of UML concepts, and an alphabetical encyclopediaof UML terms and concepts. The first part is a survey of UML its history, purposes, and uses to help youunderstand the origin of UML and the need it tries to second part is a brief survey of UML views so that you can put all the con-cepts into perspective.

10 The survey provides a brief overview of the views UML sup-ports and shows how the various constructs work together. This part begins withan example that walks through various UML views and then contains one chapterfor each kind of UML view. This survey is not intended as a full tutorial or as acomprehensive description of concepts. It serves mainly to summarize and relatethe various UML concepts and provides starting points for detailed readings in theencyclopedia. The third part contains the Reference material organized for easy access to eachtopic. The bulk of the book is an alphabetical encyclopedia of all of the conceptsand constructs in UML. Each UML term of any importance has its own entry inthe encyclopedia. The encyclopedia is meant to be complete; therefore, everythingin the concept overview in Part 2 is repeated in more detail in the same or similar information has sometimes been included in multiple ency-clopedia articles so that the reader can conveniently find Reference part also contains an alphabetic list of UML standard elements.