Objects collaborate through relationships. Choosing the right one clarifies ownership and lifetime. Relationship Meaning Lifetime UML Example Dependency uses temporarily none dashed arrow OrderService.place(order, mailer) Association knows about independent line Teacher ↔ Student Aggregation has-a (weak) parts can exist alone hollow diamond ◇ Team ◇— Player Composition owns (strong) parts die with the whole filled diamond ◆ Order ◆— OrderLine Inheritance is-a — hollow triangle △ Manager △— Employee Realisation implements — dashed triangle ArrayList ⇢ List Multiplicity Relationships also have cardinality: one-to-one (User–Profile), one-to-many (Customer–Orders), many-to-many (Student–Course, usually via a join entity like Enrollment). Why it matters These map directly onto code design…