Read the project below and draw the UML Domain class Diagram using the tool draw.io. You actually have to draw it. It should not be a written explanation. If you are unable to draw it using the the tool draw.io, please don't do the question in that case. I will also leave screenshot of a UML Domain Class Diagram.

The written explanation of what the diagrams should look like:

The Domain Class Diagram consists of the following classes:

1. Device: This class should have attributes such as Device ID manufacturer, type, model name, model number, serial number, color, screen size, device image, year of purchase, purpose of use, and status
2. Employee: Represents an employee of the company. This class should have attributes, including their full name, ID, and department, email.
3. Loaner: Represents a loaner device that can be provided to an employee when their mobile device is not working. This class should have attributes such as Device ID, borrower ID, loan date, return date.
4. Device Assignment: Represents the assignment of a mobile device to an employee. This class should have attributes including the employee's ID, the device's ID, assignment ID, the pickup time, the return time, and the employee's signature.
5. Device Request: Represents a request for a loaner device by an employee. This class should have attributes including the employee's ID, the requested loaner's ID, the pickup time, the return time and the loaner's status .
6. If you think there something else could be it please add it in there.

The Project content:

The following picture has marking Rubric .Make sure the UML Domain Class Diagram follows with the rubric.

I am also leaving a screenshot of UML DOMAIN CLASS DIAGRAM  to give you a general idea on how to draw it.

NOTE: IT IS NOT ACTUAL THE DIAGRAM FOR my project

 

I Hope the person answering my question understood that you are suppose to create  UML Domain Class Diagram with the help of the tool such as daw.io. Please don't write me an explanation. I need a diagram drawn.

Project Paul is the Director of IT Services for a consulting firm Avant. The firm has been growing fast since it was launched in 2010. With over 100 employees and hundreds of clients, Avant is facing a challenge of operating more efficiently, particularly in its internal IT services. Avant equips each consultant with two mobile devices (one laptop and one smartphone). Typically, a consultant will receive a laptop and a cell phone on the first day of his/her job. Every two years Avant will replace the existing mobile devices with new ones. Each mobile device is tagged with a unique ID and registered under the employee ID of the person to whom it is assigned. If for some reason, a mobile device is not working, the consultant needs to contact the IT Services, and an IT Services staff will provide a loaner to the employee until the mobile device is fixed. If the device is not fixable, a replacement will be provided upon the return of the loaner. If a device is lost, the staff will investigate the issue, and then either write the device off or charge the employee for the device's residual market value. Over time, as the number of employees goes up which results in corresponding increase in the number of equipment to manage, Paul and his department of ten staff have found it increasingly difficult to manage all the devices efficiently. Quite often, an employee is given a loaner without returning the original device, and sometimes a loaner is not recorded so the department runs out of loaners. Paul has received numerous complaints recently from other departments, which forces Paul to come up with a solution to deal with the issues. "Maybe an asset management system (AMS) would help solve the headache," he says to himself. Then he starts to jot down some key functions of the asset management system. Device Module This module is important to Paul because he needs to have a full inventory count of all devices that are currently being used by employees, used by the IT Services as loaners, or need to be replaced. For each device, he wants the system to store at least following information including manufacturer, type (e.g., laptop, cell phone), model name, model number, serial number, color, screen size (laptop), device image, year purchased, purpose of use (e.g., for employees, as a loaner), and status (e.g., just arrived, assigned, being in use, to be replaced, returned, lost). Each device shall be tagged with a unique five-digit ID. Device Assignment Module Paul really wants a clear view of device assignment. In particular, he wants his staff to be able to use the system to record to whom a device is assigned. For example, on March 1, 2018, Jane Smith was provided a device with the tag ID 22335. He wants the system to record all the information. Specifically, the staff should be able to use the system to indicate that the device has been picked up by Jane at the pickup time (date and time). And the system shall record Jane's signed signature as a proof. If the employee David needs a loaner for the malfunctioning device he is using, he would file a loaner request using the AMS. With the full inventory information in the system, David shall be able to see what is available in inventory and pick one he likes. After receiving the request, the staff would prepare the requested device, note in the system when the device is ready for pickup and send the notification to David. Upon receiving the notification, David needs to return in person the malfunctioning device, for which the staff will first update the status in the AMS, indicate the time of receipt of the device and reasons for return. Before giving the loaner to David, the staff will need to indicate in the system the pickup time. David will then add his signature; the staff will update the status of the loaner request to "fulfilled" as well as the status of the loaner (i.e., picked up). Once a replacement arrives, the staff will create a record of the replacement first in the AMS and then notify David to pick up the replacement. David will then return the loaner, and pick up the replacement. His signature is required for the replacement pickup and loaner return, and the staff needs to show the time of the return/pickup and update the status of both devices. After carefully reviewing the requirements of two modules, Paul seems to be convinced that the AMS is the solution for the inefficiency faced by his department