Tausif -A2- Week 3 Blog: Checkpoint Presentation and Proposal Requirements Extraction

By


This week we had our first mandatory checkpoint presentation. Manzil and I presented our frontend progress and received feedback from Roshan, particularly around focusing on phone-based features and leveraging native device capabilities.

Following last week's news about Jayden leaving the team, I had begun task redistribution. During the checkpoint class, Jayden attended and we learned there had been a subject enrollment mixup. He is back on the team, requiring workflow readjustment.

After the checkpoint, I focused on extracting specific requirements from our original proposal. I noticed some of our development work had diverged from what we committed to deliver. Team members also asked me to clarify the actual proposal requirements so everyone could understand what we need to build.

I am systematically working through the entire proposal document, pulling out concrete requirements, technical specifications, and feature commitments. This involves reviewing each section to identify what we promised to deliver and creating clear documentation the team can reference. The goal is to give everyone a proper understanding of their responsibilities and ensure our development aligns with our original commitments.

I am also planning multiple work sessions with the team to establish a strong development flow moving forward. This requirements breakdown will help me designate specific tasks during these sessions.


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