Question

Draw a UML class diagram that describes the following things. Use the standard UML stereotypes where appropriate. Show visibility, but do not show method signatures, attribute types, constructors, or destructors. Where appropriate distinguish between class and instance attributes and between class and instance methods. (Assume that all are instance attributes/methods unless otherwise indicated.) When an attribute is not another class in the diagram, show it inside the appropriate compartment. Otherwise show it as an aggregation relationship, with the appropriate role name. Remember to show multiplicities, and no class should appear more than once in the diagram.

• Invoice is a class containing private attributes paid (a boolean), total (a double), and protected attribute purchases (an array of Purchase). In addition to a default constructor and a destructor, it has public methods isPaid() and getTotal().
• Purchase is a class containing private attribute quantity (an integer). Its constructor has two parameters: an integer and an Item. It also has a destructor, plus public methods getQuantity(), getTotalCost() getItemCost(), and getItemName().
• Item is a class containing public attributes name (a string) and cost (a double).

Answer 1

In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects.

It is the general purpose modeling language used to visualize the system. It is a graphical language that is standard to the software industry for specifying, visualizing, constructing and documenting the artifacts of the software systems, as well as for business modeling.

The above class diagram is given below