Activity diagrams describe service coordination at different abstraction levels. Initial state shows entry point, final state shows end of activity. Flow Final node terminates specific flows in UML 2.0. Actions represent single atomic steps within activities
Book divided into 10 chapters covering requirements gathering, analysis, design, and architecture. Each chapter builds on previous ones to explain OOA&D principles. Uses visual storytelling and humor to enhance learning experience
A class is a blueprint for objects, which describe what objects will be. Objects are instances of classes, which contain states and behaviors. Classes encapsulate state (attributes) and behavior (operations)
UML state diagrams model system behavior in response to events. States represent system phases shown as rectangles. Events trigger transitions between states. Transitions show events, guards, and actions between states
Visual representation of system usage scenarios from user perspective. Part of Unified Modeling Language (UML) for system design. Shows basic flow of events and system-user interactions
UML class diagrams illustrate program structure and relationships. Class diagrams are most common and important UML type. Rough diagrams can be created using class names for feedback