Wk 8 – Modeling Exercise: Part 4 – Class Diagram Assignment

OVERVIEW
For this Modeling Exercise:
Part 4 – Class Diagram Assignment, you will revisit the scenario given in the Modeling Exercise: Part 2 – TO-BE Activity Diagram Assignment Instructions and Modeling Exercise: Part 3 – Use-Case Diagram Assignment Instructions documents and create a class diagram representing the classes, attributes, operations, relationships, and multiplicities.

INSTRUCTIONS:
Now that you have a good idea what the system must do as it interacts with the user, the next step is to define the internal structure of the system. To do that, you will create a class diagram. For this Modeling Exercise: Part 4 – Class Diagram Assignment, develop a class diagram (similar in look and feel to the one in figure 3.1 of your UML Distilled textbook). Your class diagram must include all of the information-based classes in the scenario along with the key attributes and operations for each of the classes, as well as appropriate relationships with specified multiplicities on each end of each relationship. Remember that classes are more than just the actors involved in the process. Think of all the objects used within the process and create a class for each class of object. You will need to refer back to the to-be process description given in the Modeling Exercise: Part 2 – TO-BE Activity Diagram Assignment Instructions, as well as the notes provided in Modeling Exercise: Part 3 – Use-Case Diagram Assignment Instructions documents from the user interviews.
As you complete this Modeling Exercise: Part 4 – Class Diagram Assignment, keep the following in mind:
Refer to the Modeling Exercise grading rubric before you begin this Modeling Exercise: Part 4 – Class Diagram Assignment.
Even though we are now modeling the classes for a technology system, the use cases should still avoid references to any specific technology.
The purpose of this diagram is to visually communicate with the client how the internal structure of the system will be designed. As such, your diagram should be easy to read for a non-technical person, follow correct UML syntax for class diagrams (see the UML textbook), and include a proper title and legend (you will need to draw the legend manually, using the unique shapes used in the diagram along with a short textual description of what each shape represents).
Be sure to model your classes such that they represent actual information and behavior that occurs within the context of the system.
There are no set-in-stone solutions for this Modeling Exercise: Part 4 – Class Diagram Assignment. Just as in the real world, there are no off-the-shelf solutions for every IT challenge. It is not our intention to limit your creative knowledge designs.
Resources:
https://plantuml.com/
https://www.lucidchart.com/pages/
https://app.diagrams.net/
https://staruml.io/

Last Completed Projects

topic title academic level Writer delivered