Team Status Report 4/12

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 at this stage of our project is ensuring that we have enough time remaining for integration. To mitigate this, we’re integrating components as they’re developed, rather than waiting until all parts are complete. In addition, we’re thoroughly testing each component during development, since the time we have for final project testing may be limited. This helps us catch potential issues early and reduces the risk of running into issues during the integration phase.

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 have been made to our block diagram in the past two weeks.

Now that you have some portions of your project built, and entering into the verification and validation phase of your project, provide a comprehensive update on what tests you have run or are planning to run. In particular, how will you analyze the anticipated measured results to verify your contribution to the project meets the engineering design requirements or the use case requirements?

To test our end-to-end integrated system, we plan on using event logs at each stage of our system to measure the latency and ensure it meets our design requirements. We plan to closely monitor the synchronization between audio and lyrics, ensuring that the delay is small enough as to not impact the user experience. In addition to system integration testing, we plan to each thoroughly test our components as described in our individual status reports.

Leave a Reply

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