Tausif - AS2 - Week 6 Blog: Scope Restructuring and Prototype Demonstration

By

 Week 6 was a significant week for the team. The checkpoint demonstration gave us the opportunity to present not just what we had built but also explain the reasoning behind the direction we had taken.

During the demonstration Roshan asked each of us to speak to our progress. I walked through the shift in our approach. Originally VehicleGrid was designed as a broad EV routing platform that pulled together all charger types including government, private, Tesla and community chargers into one unified system. Private and community chargers were always part of that vision but as a data source feeding into the route planner rather than a feature in their own right.

Based on Roshan's feedback over the previous weeks and the reality of our timeline and team situation, we restructured the app to bring the community home charger marketplace forward as the primary focus. This is where homeowners and private providers can register, verify and list their chargers for other EV users. The routing and navigation elements sit around this rather than leading it. The question of where private charger data comes from is answered by this model, the users themselves are the source.

The key point I made to Roshan was that this was not a departure from our proposal. The private charger marketplace was always in our original thinking. We had not invented a new direction, we had shifted the emphasis to the part of the proposal that was most distinctive, most achievable at this stage, and most reflective of what VehicleGrid could genuinely offer that existing apps do not.

Roshan acknowledged the reasoning and the demo reflected that the feedback from previous weeks had been taken seriously and acted on.

Comments

Post a Comment

Popular posts from this blog

Week 3 Blog: Individual Contributions

By
 This week I suggested that we build a web-based application, since it would be easier to present and maintain . I also shared my screen to walk my team through serveral of my past project s, includes a Movie Review Web App , an Advanced Web Project , a Shooter Game and a Task/Calender App . These demonstrations highlight my technical ability acrosss both web and game development and based on this the team suggrested that I would be the most suitable choice to take on the role of main developer for the project. Beyond my project showcases, I also supported our collaboration setup by creating a Discord server so the team could share updates and stay connected outside formal meetings.
Read more

Week 3 Blog: Individual Contributions

By
Tausif Rahman This week I presented the  Audit App  concept with its two parts:  Order Audit (OrderAuditPro)  and  Walkthrough Auditor . I later uploaded documentation and demonstration files of an Android version of the Order Audit module, which helped the team understand the concept more clearly. In addition, I encouraged the team to think about their  past subject projects  by asking what they had worked on in Android, iOS, cross-platform, and project management courses, to see if those experiences could be adapted into our current project. Alongside that, I shared several of my own past coursework projects, such as  ScholarSwap  (resource and book exchange platform),  SurvivAway  (a budgeting and life-flow helper), and  FocusFlow  (a study planner with ADHD-focused features). I also raised the issue of  legal risks  in some ideas, such as consumer liability in a Parking App or data security concerns in a Pass...
Read more

Week 5 Blog: Individual Contributions

By
  participated in the voting process and initially leaned toward the Audit App, but after deeper discussions, I found the Customer Service Checker and Vehicle Manager ideas more scalable and innovative. I located an academic paper titled E-Charge, which described an EV-charging-station planning system using open data and efficiency modelling. I shared the paper with the group and led a discussion on how its methods could guide our approach—particularly its use of driver-collected data, efficiency mapping, and route-planning optimisation. I also helped analyse how to simplify our version for Trimester 1, keeping it practical while leaving room for AI integration later. Additionally, I began finding and reviewing more EV-planning research papers to contribute to our shared knowledge base.
Read more