the file has been attached and it has all information to it
Case Description and Content Requirements for the Individual Project 1/6/2023 Case Description and Content Requirements for the Individual Project By Dr. Linying (Lin) Dong RYERSON UNIVERSITY Page 1 of 6 Table of Contents Case Description ................................................................................................................. 2 Project Phase I - Content Requirement ............................................................................... 4 Project Phase II - Content Requirement .............................................................................. 5 Grading Rubric.................................................................................................................... 6 Page 2 of 6 Case Description 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 smart phone). 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 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. Page 3 of 6 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., pickedup) 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. Page 4 of 6 Project Phase I - Content Requirement Your individual project is developed based on the case description above. All the diagrams should be created using a diagramming tool (e.g., draw.io) and copied and pasted to a MS Word document, which then should be submitted to D2L. The following details the required content for project phase I. Note: the following structure is expected to be followed and each diagram clearly formatted and presented. Required Content • Title Page • Table of Contents • Assumptions (Optional) • Domain Class diagram - Draw a domain class diagram for the system • Use case diagram - Based on the above project case description, develop a use case diagram containing all major (e.g., create xxx, update xxx, search xxx) use cases of the system. Create two use case diagrams, one for each module. • Use case description - Write a fully detailed use case description for each use case in the use case diagram. Select two use cases, one from the Device Module, and one from the Device Assignment Module. Write a fully detailed use case description for each of the two use cases. • Activity diagram - Develop one activity diagram for each use case description you have created The table below summarizes the number of diagrams needed for project phase I Diagrams Domain class diagram Use case diagram Use case description Activity diagram No. of diagram that needs to be produced 1 2 2* 2* * If a use case has more than one scenario, then the number of use case description needed will depend on the number of scenarios. For example, if a use case has two scenarios, then the number of use case descriptions and activity diagrams shall be two for that use case. As a result, the total number of use case descriptions and activity diagrams in your project shall be changed to 3 instead of 2. Page 5 of 6 Project Phase II - Content Requirement Your individual project is developed based on the case descriptions. All the diagrams should be created using a diagramming tool (draw.io) and copied and pasted to a MS Word document, which then should be submitted to D2L. The following details the required content for project phase II. Note: the following structure is expected to be followed and each diagram well formatted and presented. Required Content • Title Page • Table of Contents • Assumptions (Optional) • Revised content of project phase I including domain class diagram, use case diagrams, use case scenarios, and activity diagrams. • System sequence diagram -Develop a system sequence diagram based on each fully detailed use case description • Design class diagram - Develop a design class diagram for the system. Include all classes of the system in the diagram. However, for the classes that are not involved in the use cases you’ve chosen, you can keep their methods blank. Detailed system sequence diagram- Develop a first-cut sequence diagram for each use case description you’ve chosen for the project The table below summarizes the number of diagrams needed for project phase II Diagrams Domain class diagram Use case diagram Use case scenario Activity diagram System sequence diagrams Design class diagram Sequence diagram No. of diagram that needs to be produced 1 2 2 2 2 1 2 Grading Rubric Project I Domain Class Diagram (max 12 pts) Naming Convention max 2pts Correct identification of classes max 4pts Correct attributes max 3pts Correct multiplicities and associations max 3pts Use Case Diagram (max 10 pts) Organized in two diagrams with actors correctly identified max 2pt Correct identification and application of the < include="">> relationships max 2pts Correctly identified all major use cases and the application of UML max 6pts Use Case Description (max 9pts) Brief description is clear and complete max 2pt Preconditions and postconditions correctly identified and described max 2pts Flow of Event is logical and clearly described max 3pts Rest of use case description components are correct and complete max 2pts Activity diagrams (max 6pts) Consistent with the flows of events described in the corresponding use case description max 1pt Each step is clear, compliant with the naming convention, and logically connected max 3pts Correct application of UML symbols max 2pts Formatting based on the project format requirements max 3 points