The scenario
Designing a UML class diagram for a point-of-sale and invoice management system used in a traditional market/fair (PuntoFeria) to track sales invoices and payments.
What is in this drawing
Read the decisions behind it.
01
Modeled Invoice as composed of InvoiceItems referencing Products
02
Linked Payment to Invoice with optional multiplicity to allow partial or multiple payments
03
Used a simple attribute for payment method instead of a separate enum class
When building a sales invoicing and payment module for small retail or market-based POS applications.
More like this