상황
A vehicle repair shop needs a domain model to track customers, their vehicles, service orders, labor, parts, invoices, and payments.
이 도면에 담긴 내용
그 이면의 의사결정을 읽어 보세요.
01
ServiceOrder composes ServiceLineItems (composition) to model order items.
02
Customer owns multiple Vehicles (one-to-many association).
03
Mechanic works on many ServiceOrders (one-to-many association).
04
ServiceOrder generates one Invoice (one-to-one association).
05
Invoice receives many Payments (one-to-many association).
Use this model as a starting point for a repair shop management system, preserving class names and relationships while extending with additional attributes or operations as needed.