UML Class Diagram of The Order Management System
Uploaded by
ScribdTranslationsUML Class Diagram of The Order Management System
Uploaded by
ScribdTranslationsThe UML class diagram of the order management system consists of the following classes:
Client
Personal and Corporate (Classes that inherit from the Client class)
Order
Product (Class added to the system)
Seller
Requests
The only composition relationship in the UML class diagram is between the inherited class Corporate and the
class Requests. It was considered to leave it with this relationship, since if there is no Corporate Client there will not be
requests. Therefore, the requests would no longer be received in the system. It was decided to leave the cardinality
<<1..*>> and <<*..1>>, since a Corporate client can make many requests, but a request
will belong to a single client.
Relationships:
Customer - Order: A Customer can make many orders over a period of time, but an order
it will be done by a single client. Therefore, cardinality <<1..*>> and <<1..1>> was left.
Order – Product: Many Orders will belong to a single Product, but a single Product can
to have many orders. Therefore, the cardinality <<*..1>> and <<1..*>> was left.
Order - Seller: This relationship was not mentioned in the partial. I chose to do it, since in a
In the real system, a Salesperson is required to make the purchase of product X or Y. An Order
will be attended by a Seller, but a Seller can handle many Orders.
Seller - Requests: It was decided to leave the cardinality <<*..1>> and <<1..*>>, since many
Requests can be handled by a single Seller, but a Seller can handle many.
Request.
