This week, we continued developing several core components of our project, particularly: lesson creation, web template design, and tone detection from calculated pitch contours. Thus far, we are on schedule and our pacing is generally what we anticipated.
While most of our design has stayed the same, we have made changes to how we will be storing data. As we have iterated over our project design and ideas, the data that we require have changed and to reflect that we updated our data model scheme from
to
.
This new scheme will provide us with more flexibility and reusability in how we represent and store data across users and exercises.
Perhaps the biggest risk we face right now is insufficient integration planning and testing. As we continue to develop our individual components, we must be conscious about exactly how these components will fit into the overall system, and most importantly the assumptions that we make at the interface of two disjoint components. To mitigate these risks, every time we meet we discuss the assumptions that we make in developing our parts: what we expect to be input and what will be output. We aim to have our first round of system integration just in time for the demo in about a week and a half, where the pitch detection and pitch/music theory lessons are working in order. We hope to be able to extensively test our integrated model before the demo to avoid any unexpected errors from occurring. Moreover, after our first round of integration we hope to test our product on a musically mature group of users and ask for their suggestions and feedback, which we will use to guide us in our future development.
Here is our updated schedule:
