"A pragmatic introduction to UML"--Cover.

Includes index.

Content: Chapter 1 Introduction What's in a Modeling Language? Why UML 2.0? Models and Diagrams "Degrees" of UML UML and the Software Development Process Views of Your Model A First Taste of UML Want More Information? Chapter 2 Modeling Requirements: Use Cases Capturing a System Requirement Use Case Relationships Use Case Overview Diagrams What's Next? Chapter 3 Modeling System Workflows: Activity Diagrams Activity Diagram Essentials Activities and Actions Decisions and Merges Doing Multiple Tasks at the Same Time Time Events Calling Other Activities Objects Sending and Receiving Signals Starting an Activity Ending Activities and Flows Partitions (or Swimlanes) Managing Complex Activity Diagrams What's Next? Chapter 4 Modeling a System's Logical Structure: Introducing Classes and Class Diagrams What Is a Class? Getting Started with Classes in UML Visibility Class State: Attributes Class Behavior: Operations Static Parts of Your Classes What's Next Chapter 5 Modeling a System's Logical Structure: Advanced Class Diagrams Class Relationships Constraints Abstract Classes Interfaces Templates What's Next Chapter 6 Bringing Your Classes to Life: Object Diagrams Object Instances Links Binding Class Templates What's Next? Chapter 7 Modeling Ordered Interactions: Sequence Diagrams Participants in a Sequence Diagram Time Events, Signals, and Messages Activation Bars Nested Messages Message Arrows Bringing a Use Case to Life with a Sequence Diagram Managing Complex Interactions with Sequence Fragments What's Next? Chapter 8 Focusing on Interaction Links: Communication Diagrams Participants, Links, and Messages Fleshing out an Interaction with a Communication Diagram Communication Diagrams Versus Sequence Diagrams What's Next? Chapter 9 Focusing on Interaction Timing: Timing Diagrams What Do Timing Diagrams Look Like? Building a Timing Diagram from a Sequence Diagram Applying Participants to a Timing Diagram States Time A Participant's State-Line Events and Messages Timing Constraints Organizing Participants on a Timing Diagram An Alternate Notation What's Next? Chapter 10 Completing the Interaction Picture: Interaction Overview Diagrams The Parts of an Interaction Overview Diagram Modeling a Use Case Using an Interaction Overview What's Next? Chapter 11 Modeling a Class's Internal Structure: Composite Structures Internal Structure Showing How a Class Is Used Showing Patterns with Collaborations What's Next? Chapter 12 Managing and Reusing Your System's Parts: Component Diagrams What Is a Component? A Basic Component in UML Provided and Required Interfaces of a Component Showing Components Working Together Classes That Realize a Component Ports and Internal Structure Black-Box and White-Box Component Views What's Next? Chapter 13 Organizing Your Model: Packages Packages Namespaces and Classes Referring to Each Other Element Visibility Package Dependency Importing and Accessing Packages Managing Package Dependencies Using Packages to Organize Use Cases What's Next? Chapter 14 Modeling an Object's State: State Machine Diagrams Essentials States Transitions States in Software Advanced State Behavior Composite States Advanced Pseudostates Signals Protocol State Machines What's Next? Chapter 15 Modeling Your Deployed System: Deployment Diagrams Deploying a Simple System Deployed Software: Artifacts What Is a Node? Hardware and Execution Environment Nodes Communication Between Nodes Deployment Specifications When to Use a Deployment Diagram What's Next? Appendix A Object Constraint LanguageAppendix B Adapting UML: Profiles Appendix C A History of UML Index

Since its original introduction in 1997, the Unified Modeling Language has revolutionized software development. Every integrated software development environment in the world--open-source, standards-based, and proprietary--now supports UML and, more importantly, the model-driven approach to software development. This makes learning the newest UML standard, UML 2.0, critical for all software developers--and there isn't a better choice than this clear, step-by-step guide to learning the language.'--Richard Mark Soley, Chairman and CEO, OMG If you're like most software developers, you're building systems that are increasingly complex. Whether you're creating a desktop application or an enterprise system, complexity is the big hairy monster you must manage.The Unified Modeling Language (UML) helps you manage this complexity. Whether you're looking to use UML as a blueprint language, a sketch tool, or as a programming language, this book will give you the need-to-know information on how to apply UML to your project. While there are plenty of books available that describe UML, Learning UML 2.0 will show you how to use it. Topics covered include:Capturing your system's requirements in your model to help you ensure that your designs meet your users'needsModeling the parts of your system and their relationshipsModeling how the parts of your system work together to meet your system's requirementsModeling how your system moves into the real world, capturing how your system will be deployedEngaging and accessible, this book shows you how to use UML to craft and communicate your project's design. Russ Miles and Kim Hamilton have written a pragmatic introduction to UML based on hard-earned practice, not theory. Regardless of the software process or methodology you use, this book is the one source you need to get up and running with UML 2.0.Russ Miles is a software engineer for General Dynamics UK, where he works with Java and Distributed Systems, although his passion at the moment is Aspect Orientation and, in particular, AspectJ. Kim Hamilton is a senior software engineer at Northrop Grumman, where she's designed and implemented a variety of systems including web applications and distributed systems, with frequent detours into algorithms development.