D Anthony wrote:Thanks, yes that was a mistake, i meant patron. Ok, so you are basically saying to use a generalization relationship and have an abstract class call 'account' then have admin and patron as x2 concrete classes?
D Anthony wrote:Yes, i get that, i meant i usaully develop from a design that is done by a system analyst whom would have gathered the requirements and model the system.
I wrote:The relationship line between Patron and Book that you show on your diagram is bogus.
Junilu Lacar wrote:One more thing. You may or may not have done this intentionally but notice how your Patron class is kind of the central hub for your diagram. This tells me that you probably see a Patron is a key entity in your system design. I would argue otherwise. If this is a Library Reservation system, the key entities are more likely to be things like Title, Item, and Reservation. Everything this system does revolves mainly around these classes. Just because a real-world patron is a key user of your system, that doesn't mean the software representation of a patron is central to your system's design.
D Anthony wrote:Based am are you feedback i will continue to improve the diagram until i get it right.