- What are the most significant risks that could jeopardize the success of the project? How are these risks being managed? What contingency plans are ready?
One of the most significant risks that we have identified is the integration of all the separate parts of our project. We think that integrating our classification to be stored in a database which our backend can pull from will be difficult considering all the moving parts. We are managing this risk by setting early deadlines for our individual pieces so that we have a lot of time to integrate. The contingency plan for us not being able to integrate in time would be to simplify our project to make integration easier.
Another significant risk has to do with the clothing classification for our project. Currently, the dataset we are using is displaying -1s for all of the attributes. We are managing this risk by troubleshooting with the file, however if this does not work as a contingency plan we will look into using alternative datasets that still classify clothing based on item, fabric, and color.
- Were any changes made to the existing design of the system (requirements, block diagram, system spec, etc? Why was this change necessary, what costs does the change incur, and how will these costs be mitigated going forward?
We are going to lower the requirements that we created for classification accuracy, because they were set very high and according to faculty feedback, are too high to be feasible. Instead of the 98% clothing type accuracy, 100% color accuracy, and 85% fabric accuracy, we’ll be looking for 90%, 95%, and 80% respectively. Since our classification requirements have been changed to lower the accuracy we are looking for, we will also lower our requirement for outfit correctness to 80% from 90%. This is because item classification accuracy plays a large part in outfit correctness, so we must lower both accuracy/correctness thresholds. Additionally, we have started to finalize our hardware decisions and have narrowed it down to a few suitable choices for each part.
- Provide an updated schedule if changes have occurred.
The github setup task was reassigned from Alanis to Riley. Aside from this, the web app mockup task was changed to making the demo Flutter app, and the mockup task is now moved to being done with the UI animation task. We are currently on track with our scheduled tasks and assignments.
Here is the updated schedule.
- This is also the place to put some photos of your progress or to brag about a component you got working.
Photos of our progress are located in our individual status reports.
