Posted on

Brandon’s Status Report for 02/07

What did you personally accomplish this week on the project? Give files or photos that demonstrate your progress. Prove to the reader that you put sufficient effort into the project over the course of the week (12+ hours).

This week I got to work out the specific details of the implementation. There was a lot of unknowns when it came to the specific hardware and how it would interact with the algorithms and backend we were using. Having to understand what is needed for Pedestrian Dead Reckoning and what kind of hardware is needed to collect the right data showed me a lot about how I plan to integrate the IMU and GNSS modules. This also gave me a chance to start working on the PCB, as I now have pinouts for all of the modules, except for the screen. One of the kinks you have to work out when considering all of this is how to conserve battery an one of my issues will be implementing the usb c charger, this will be a major concern as it could take up lots of space if not implemented properly….

Is your progress on schedule or behind? If you are behind, what actions will be taken to catch up to the project schedule?

According to the schedule I have to prepare for the Design Review and finish the PCB for the device.

Right now I am on schedule, however it feels behind because this upcoming week with the design review I will have other commitments that will make me and other team members busy, focus will be essential. Therefore we are essentially late, but to make it work we need to communicate daily and follow up on commitments we made during our weekly Friday meeting.

What deliverables do you hope to complete in the next week?

Design Review slides, PCB Design, and ordering parts. We have established timelines, and the preparation ready, but need to get the work done.

Posted on

Team Status Report for 02/07

Currently our most significant risk is that our PCB may not be ready in time. Because this process takes so long, and can take more than one iteration to get it right, the PCB is our bottleneck. To manage this risk, we will be ordering our PCB by the end of the week to ensure we have as much time as possible to test and iterate if necessary.

We did not make changes to the overall design of our device. This is because we had a good idea going into our proposal presentation of what exact features we wanted to implement. However, we did ad user requirements to include more emotional user requirements, like spontaneity of meetup. This change was necessary because our device at its core is designed to connect and build community. It is not faster, smoother, or better designed than an iphone, but people will still gravitate towards it because it makes connecting with friends easier. Our previous requirements didn’t capture this nuance.

After making this change, we also had to change testing plans. Now our testing plans include user surveys and interviews. We have allocated 3 days for these plans. Our current schedule already includes these changes.

Posted on

Katherine’s Status Report for 02/07

This week , I worked on creating the proposal presentation. We created a document where we wrote out our content. I specifically worked on the use case and use case requirement section. Prof. Theo told us that our abstract missed the emotional use case requirements, such as metrics that measure stress reduction, or more spontaneous meetups. I wanted to make sure our requirements measured these requirements in a quantifiable way. Additionally, I wanted it to be very clear why our device is useful and is better than an iphone. I spent a good amount of time looking into the market our device fits into and how our device is different from the iphone.

I are currently right on schedule, as we created the schedule very recently. The main milestones we want to reach this next week is to have the PCB designed and ordered. I need to learn more about Google maps APIs and develop an understanding of how I would integrate it into our project.