Objectives
We will use graphical charts to represent focus in on a portion of the system proposed in Project 2. Using the tool(s) of your choosing (Figma or Google Drawings are good choices),
- Select one specific feature of the proposed system, and use UML to construct all of the following:
- a Behavioral Use Case Diagram with multiple user roles interacting with all the components of the chosen feature
- a Class Diagram with Model Objects and Methods
- an ERD to show an example of what those model attributes look like in the backend db, primary and foreign keys, and their relations
- an Activity Diagram (the analogue of a flowchart) for that specific activity
If you chose a comprehensive vendor-based solution, using their product literature, speculate on how their product works in order to diagram the above.
- use a timeline of dependent activities, identify major project milestones, the critical path, and construct a Gantt chart.
- Using this Gantt chart, identify 3 possible risks to the project. Write a proactive narrative plan for how you can adapt/react to these risks.
Submit this documentation as a collection of PDFs and construct slides from this information. On Monday March 30th, we will have each team give a short slide presentation of no more than 10 minutes for the instructor and the rest of the class, who will pose as the Development team, with a discussion and Q&A to follow each presentation. In Project 4, we will use the artifacts of this project and feedback to inform further analysis and design.