Kevin’s Status Report for 2/21/2026

This week I have started prototyping the GPS transponder pipeline for our project. I am still in the process of working through with my teammates to figure out what the best way to connect the backend to the transponder. On top of that, I also started prototyping the webapp solution for our frontend functionality. I am still considering which API backend to use for our maps interface and I am working to make this robust. This aligns with the prototyping schedule outlined in our proposal. In the next week, I hope to have a solid website implemented and further integrating the different pipelines into the backend.

Kevin’s Status Report for 2/14/2026

This week I have proposed our website solution for PotSpot and also have a plan for implementing our map API functionality. This plan was made from continued research of map APIs. Additionally, I helped flesh out our design proposal outlining concrete solution flows for PotSpot on the backend. As of right now, this aligns with the schedule outlined in our proposal. In the next week, I intend on starting the actual design of the website portion of our project and work on the GPS transponder implementation.

Kevin’s Status Report for 2/7/2026

Earlier this week I presented our project proposal so I prepared my presentation/speaking on PotSpot. Additionally, I also worked on helping make the parts list needed for our project. I helped research on what GPS module that we want to use for our system. I also started brainstorming the style that we want our webapp to look like. On top that, I researched on an initial implementation for the APIs needed to complete the map functionality. This is on schedule and aligns with what I outlined in our project proposal for what I need to get completed this week. In the next week, I intend to propose a more finalized approach to implementing our initial prototype of the webapp of PotSpot.

Team Status Report for 1/31/2026

The most significant risk would be falling behind due to unknown knowledge/situations. To mitigate this, we will communicate with each other if we have any concerns.  The contingency plan for us is to be actively communicating  and set up meetings and work together. At this point in the project, there has been no changes to the design of our system.

Kevin’s Status Report for 1/31/2026

This week I finished the “Technical Challenges” and “Software Solution” slides for our proposal presentation. I also established what the flow for our software side of our project will look like in the end. I made changes to the requirement numbers and provided justification for why we chose those numbers. I am currently on schedule to finish the scheduled tasks outlined in our project proposal. Next week, I hope complete research on what GPS transponder we are using as well as finishing brainstorming what our website will look like.