New answers tagged

0

It might help to remember that classes don't really exist in the real world (they exist in our mental models), but objects do exist. So, when I'm using a UML object diagram, I'm showing things that are instances, usually of real-world things. For example, if I say a Student is a Person, it's a generalization relationship. That relationship exists mentally, ...


3

Association and Composition make sense for objects, as well as classes. An object may use another (Association), and an object may contain another (Composition). But you can only Generalize a base class to create a derived class. It's not possible for one object to be a Generalization of another object. If the base class isn't abstract, it's possible to ...


2

Do you need to build both? Maybe. It depends. I'd say that if there is a 1:1 mapping between classes in a UML Class Diagram and components in a UML Component Diagram, you probably don't need both diagrams. The intention of both diagrams is different, though. Class diagrams specifically show classes (and modules or packages), along with their attributes, ...


Top 50 recent answers are included