The scenario
A public library needs a class model to design its circulation system, covering members, librarians, catalog, physical book copies, loans, reservations, and fines.
What is in this drawing
Read the decisions behind it.
01
Abstract User class centralizes shared attributes for Member and Librarian
02
Separate Book (catalog metadata) from BookItem (physical copy)
03
Loan connects Member, Librarian, and BookItem with a 1-to-0..1 association to Fine
Reuse when designing or documenting the object-oriented domain model for any library circulation, catalog, or self-service system.
More like this