use case diagram for online car shopping

Use case diagram Drawing Unified Modeling Language, use case diagram actor, angle, white, text png 1920x1138px 75.95KB.Computer Cases & Housings Laptop Use case diagram Computer System Cooling Parts, article desktop, game, electronics, computer png 1024x768px 584.01KB.Letter case U Alphabet Word, Us Letter Size, english, rectangle, black png 686圆00px 8.17KB.human stick, Use case diagram Symbol Computer Icons Actor, actor, celebrities, angle, use Case png 712x980px 31.58KB.Test case Logo Software Testing Engineering Use case, Business, blue, people, innovation png 612圆13px 17.05KB.Computer hardware Computer Software Audit Inventory Use case, audit, computer Network, text, computer Program png 500x500px 21.33KB.Computer Icons Use case, Use Case, blue, angle, text png 500x500px 4.83KB.Thumbnail, use case diagram actor, angle, furniture, rectangle png 1024x716px 11.28KB.Use case diagram Actor, actor, celebrities, angle, text png 658x1024px 17.96KB.Personally I'd opt for this kind of approach, but it's a more fundamental change compared to your initial design, and the way you address the requirements. Typically, you'd use something like the state design pattern.Ī third more fundamental transformation is to differentiate the session that connects a user to the system, from the views and the transactions that may be performed during the connection. delete the shopping basket).Ī second transformation would be to get rid of inheritance and consider the buyer/seller as specific behaviors of a session. The session kill and create would work, especially as the delting a session would probably require to take a decision on going operations (e.g. You may then have a Session class, that would have the common features and be specialized into Buyer_session and Seller_session.

The first transformation to consider is that sessions would not inherit from an enterprise but be associated with an enterprise. This is the moment to remind the principle of preferring composition over inheritance. It may involve a user account or an enterprise, but it should not inherit from them. But this does not correspond to reality: a session is a session. Your diagrams says sthat a Buyer_session and Seller_session both are some kind of Enterprise, and that an Enterprise is some kind of User. Moreover, your design is flawed due to an overuse of inheritance. This means that in practice your design would not allow to keep the same session, but would require that you destroy one and create a new one. However such a change is not supported by most of the OOP programming languages. Changing the class of an object dynamically is possible in UML.

Your design divides sessions classes into Buyer_session and Seller_session.

Use case diagram for online car shopping