Team Status Report for 10/26/2024

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?

The most significant risk that could jeopardize the success of the project is the accuracy of each sub component. Neither the sheet music scanning component nor the audio component will be able to have 100% accuracy meaning the timing algorithm will have to be able have some level of tolerance for that. For example if we classify a note duration for the pianist correctly but the singer incorrectly that can mean we incorrectly identify that they are out of sync. Currently we are managing this risk by ensuring that the duration classification is as high possible however this does not completely mitigate the risk. If this ends up being a significant issue then we can allow the user to manually edit the duration of certain notes so that if they notice that they are consistently getting out of sync after a certain point they can override the MusicXML we have with the correct duration.

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?

Changes made: None

Leave a Reply

Your email address will not be published. Required fields are marked *