Team Status Report for 11/16/2024

For validation tests, we want to ensure that when the system is given the same inputs, we get the same outputs every time. This can be done by giving the system the same sheet music and audio data and ensuring the music highlighting is the same.

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?

So for the most significant risks are that we cannot properly process complex pieces of music. This risk is being managed by slowly increasing the complexity of the music we process to ensure that we don’t have any surprises as we test more complicate pieces. The contingency plans we have are to just stick with simpler pieces of music because it is working so far so if there are complex pieces of music we have trouble processing, we will treat them as edge cases and focus our energy on polishing what we know works.

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?

No changes made.

 

Leave a Reply

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