10 ;;Quote: functional design of software leads to brittle systems that can not change easily

11 ;;Quote: objects are things drawn from the problem/solution space; a class describes a set of common objects

11+;;Quote: each object has a identity or name, data or state, and behavior

54 ;;Quote: use classes to model abstractions from the problem or solution space

54+;;Quote: classes define the vocabulary for describing a system

55 ;;Quote: classes represent objects in the problem/solution space with a set of responsibilities that are implemented through attributes and operations

163 ;;Quote: need to know a component's mechanisms and the order for calling its operations

300 ;;Quote: a state machine defines the legal ordering of states over time; how the current behavior depends on the past

435 ;;Quote: UML defines software through structures (classes, interfaces, use cases), behavior (state machines), groups (packages), and notes or annotations

438 ;;Quote: a UML dependency occurs when a change in one thing affects the semantics of another

438 ;;Quote: a UML association describes a set of links between objects; e.g., an employer employs employees

438 ;;Quote: a UML generalization substitutes for objects of the specialized element

439 ;;Quote: extend UML with stereotypes (new elements), tagged values (new attributes), and constraints (new semantics)

439 ;;Quote: UML diagrams for classes, objects, use cases, sequences, collaboration, statecharts, activities, components, and deployment

439+;;Quote: a diagram is a graphical presentation of a set of elements and their relationships