It's a pity that "object-oriented" is such a popular term. It's the domain relationships between things that truly define the rules for a domain. Their formalization as associations of various kinds are often far more interesting than the objects because associations capture the rules in the domain. Taken together, classes, attributes, relationships, and their descriptions form the class model that is the basis for all subsequent work because Executable UML models define the behavior of instances of classes and associations. We begin by examining actions on classes, objects, attributes, and links. |