UML 2 For Dummies

Overview

In This Chapter

• Avoiding overly complex state diagrams

• Handling concurrent states

• Using a shorthand notation to reduce diagram complexity

• Working with protocol state machines

• Steering clear of data-flow diagrams

S ome objects are really dynamic. They are expected to perform many different behaviors at many different times. The rules for what behavior your objects must execute—and just when to execute that behavior—can get really complex. To help you avoid your own state of confusion, this chapter shows you how to build complex state diagrams that really do the job—and can help maintain your sanity.