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?
At this stage of the project we don’t have too many major risks that we have identified that could affect the course of the next few weeks. However, this may still change and we definitely are ready to solve them as they come. One risk that stands out is the constant running of the proximity module. The current design of the proximity module involves the ultrasonic sensors being turned on and measuring distance continuously and during testing we realized that this may be an unnecessary load on the Jetson that can be mitigated by having it so that the toggling of the modes also control the ultrasonic sensor of the proximity module and not just the vibration motor output. This is a call that we will make once the OR module is integrated into the system and we can actually test the overall latency and functionality of the device.
A second risk is the development time and cost of 3D printing a device case. We have decided that given the few weeks we have remaining, risking it with the extended development time 3D printing may need may not be worth the small difference in user experience between 3D vs laser cutting or other methods for building the case and strap to make the device wearable. Hence, that is the approach we will be taking for the device case.
A final risk is that the PCB may need to be redesigned. Since we are having issues with the proximity module code, we plan to test whether the issues stem from interfering signals on the PCB. If this is the case, we will need to redesign the PCB and order a new one as soon as possible, so that we are able to test that one.
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?
We have decided to deviate from the original plan to 3D print our device case and instead look into laser cutting or simply hand-building our case using other materials. This change was necessary because of the cost and time required to 3D print with the minimal experience we have as a group. This will help us reduce cost and we believe this is a practical move given the remaining timeline of this project.
Provide an updated schedule if changes have occurred.
Integrating the OR model to NVIDIA Jetson will be extended due to unexpected system errors in the Jetson. 
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?
After we combine all subsystems to Jetson, we are planning to test the device in terms of accuracy. We will use several different indoor settings and check whether the device is able to detect the closest object within 2 meters and able to transfer the result to the audio output. We will validate the device by checking whether the result is the same as the actual closest object. The project will be successful if the accuracy is above 70%, which was the use case requirement. In addition to the quantitative testing, we will be reaching out to our contacts through the Library of Accessible Media Pittsburgh to ask for volunteers to test our device. This will happen closer to completion of the project, with some time given to fine-tune our device based on the feedback that we receive.