Project Risks and Mitigation Strategies
Everything, as it sort of always does, takes longer than you think it does. With the interim demo and Carnival both fast approaching, the sheer amount of time that we possibly have to sink into this project is becoming very limited, and we’re beginning to really consider what are the most important parts of it that we need to hit as soon as possible, and what can be put off to after the demo or potentially (unfortunately) pitched, without damaging the meat of it.
Changes to System Design
We have not yet committed to it, but we’ve begun discussing seriously (as we recognized some time ago may be necessary) dropping Bluetooth communication in favor of WiFi; we were worried about how power-hungry WiFi is, but since the headset needs to be in contact with the web app at only a few particular points we may be able to mitigate this. WiFi is simpler both for the hardware as it’s already set up on the Rasppis and simply reduces the number of different thing we need to figure out, and for the software, since we know our server host cooperates better with WiFi signals than Bluetooth. This may become a system design change soon.
Schedule Progress
Independent schedule progress is addressed in our individual reports. While the order of some tasks has shuffled, our work is roughly on track.
Web scraping works now, and Diya and Charvi will work together to integrate this into the webapp in the coming week.