So I'm working on an assignment for school, where I am to model (using a domain model) a web shop that delivers complete grocery bags to people's homes. (http://www.linasmatkasse.se). I wish I could be more specific here, but this is all I have unfortunately.
I haven't received any use case, but the scenario would be something like, add bag to cart, create account/add info, pay.
This is what I have so far : https://i.stack.imgur.com/3EOIL.png
- Are there any redundancies? (I only have to depict the model of the site, unsure how much to include).
- Could/Should I add composition between for instance Customer and Account, Cart and OrderLineItem, Order and Cart?
- Pretty uncertain about attributes & multiplicites in general. Any feedback or support here is appreciated.
- Payment class? Is it needed? Should it have payment methods included?
- Should I model human elements like support?
- Should I model more of the delivery
- Is association between customer and order needed?
Thanks a bunch! Again...
Delivery? Maybe more enumerations for way of delivery and supplier, ClientAddress that is seen from Account, Order. It is for you to decide if you want to cover this or that scope.
ItemDescription should be connected to Item only
If a class attribute is an instance of another class, put a dot on that another end of association (end owned by classifier).
Supplier connected to Order? Do you want to cover the theme of trade with suppliers, too? Then there should be more classes on that theme. And it could be another component and another class diagram. Or is there a graphic error?