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 currently is firmware and hardware not being integrated well and us having to physically remove prints again. The enclosure is not fully designed yet so it hard to get a feel of the device. We need to conduct user testing starting Monday. There are also a lot of deliverables due next week so we need to forward plan.
Unit Tests:
GPS accuracy (Firmware): logged GNSS points over 10 minutes at a known location across 500 samples. Target was ≤5m error. Mean error was 3.2m. Pass.
PDR accuracy (Firmware): walked multiple paths including straight, 90-degree, and 180-degree turns to validate distance calculation. Target was ≤2.5m error. Mean error was 2.5m. Pass.
Bearing computation (Software): fed known lat/lon pairs with known expected bearings and compared output. Target was ≤1° error across all cases. Max error was 0.3° across 16 cases. Pass.
Server latency (Software): ran two simulator clients for 10 minutes and logged server processing time per update cycle. Target was 90th percentile ≤50ms. 90% of updates completed within 35ms. Pass.
SUCCESS detection (Software): simulated two devices converging to <3m across 16 scripted cases. Target was SUCCESS event firing at ≤3m in ≥15/16 cases with DB write confirmed. Fired in 16/16 cases with DB write confirmed. Pass.
Battery endurance (Hardware): ran device continuously under campus-day state distribution. Target was ≥6 hours runtime. Achieved 8 hours. Pass.
System Tests (In Progress):
Navigation update latency: timing full update cycle across 10 trials. Target is 90th percentile ≤200ms. In progress. Session setup timing: measuring device wake to invite sent, invite to arrow displayed, and WiFi connection time across 10 trials. In progress.
Planned: Usability and stress reduction: user survey measuring mean ≥3/5 across usability questions and ≥70% yes on spontaneity question. Planned.
No failing tests were recorded across completed unit tests. PDR accuracy hit exactly the 2.5m threshold . This is worth monitoring under more varied terrain or longer paths to confirm robustness. Server latency outperformed the target significantly (35ms vs 50ms), System-level tests are still in progress and may surface integration issues not visible at the unit level.
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 were made here
Provide an updated schedule if changes have occurred.
No changes to schedule were made this week