Post Title: Team Status Report for 04/22

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?

A large risk we had faced, and managed, for a while, was the integration of the frontend javascript audio recording API and the backend python django. Ultimately, after a few weeks of efforts, we were unable to overcome this challenge. Instead, we ended up opting for asynchronous feedback provided to the user after they sang the demo. This version of our project is currently available.

As of now, after pivoting, we do not have too many concerns about the state of our project. The largest concern is making sure the web application always works as desired, and that it is robust enough to deal with uses other than the intended design.

Right now, our project is functional but basic. Making sure it withstands testing means using it a lot more, as well as navigating to the links throughout the project in a way unintended by our application. Our main focus as a group is currently to rigorously test the performance of our project and figure out any ways it could potentially be exploited. Upon doing so, we will add corresponding checks and build in specific functionality.

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?  

As mentioned earlier, we made a large pivot in our project. Although, for a long period of time, we had focused on real time feedback, we were ultimately unable to implement this within the time scope of our project. Instead, we have opted for a new navigation system, where the user performs our sample song, with corresponding graphics, downloads their performance, and views their performance afterwards.

We were hoping not to make this change, but integrating recording and pitch detection had proved difficult, with most of our group members focusing on this for the last few weeks, so we decided it was appropriate to change the scope of our project to ensure the best outcome.

We are hoping to mitigate these costs by providing interactive and in depth, although asynchronous feedback.

This is also the place to put some photos of your progress or to brag about a component you got working.

Video of current functionality.