Customer Milestone 1 Report of CMPE 451 Fall 2025 - bounswe/bounswe2025group8 GitHub Wiki

Milestone 1 Report

Introduction

Before getting right into the Milestone Review, it is nice to remember the project. Neighborhood Assistance Board brings back the community spirit of old neighborhoods, powered by modern technology. Whether you need help with grocery shopping, tutoring, minor repairs, or want to volunteer your skills, our web and mobile platform connects neighbors who need assistance with those ready to help. With personalized task feeds, secure communication, verified ratings, and location-based matching, we make neighborhood cooperation simple, safe, and trustworthy.

Even though all the features are not implemented yet, we had a great leap towards being a great team with the lessons we learned from the previous semester, which will make us build the community we want to live in.

Project Status

The project is approaching the Minimum Viable Product (MVP) stage. It includes most of the key functionalities such as creating a request, volunteering, and being accepted as a volunteer. We are ahead of schedule for the first milestone and we implemented some of the features from our intermediate milestone Milestone 1.5 - DaVinci. The system has already been deployed, although it is currently operating without an HTTPS certificate. We have taken immediate steps to get one.

However, it currently lacks crucial accessibility features, which are essential for such a project.

Consequently, we are revising the deliverables for upcoming milestones to integrate this work. Our immediate priority will be a targeted subset of these features, specifically, focusing on enhancements for the visually impaired, rather than addressing all accessibility standards at once. This focused approach will help us deliver higher-quality, well-tested implementations that make a real impact.

Summary of Customer Feedback and Reflections

The customer provided targeted feedback emphasizing feature alignment, user safety, and inclusivity. Each scenario should explicitly correspond to a defined system feature, avoiding elements outside scope. While the category-based filtering was well received, the addition of location-based search was requested.

The customer recommended implementing a complaint and reporting mechanism for inappropriate content and ensuring strict privacy protection by concealing personal information. They also highlighted the need for volunteer confirmation workflows and reminder notifications prior to assigned events.

Further feedback included improving the review system with sub-categories and separate ratings for requester and volunteer roles, and enhancing visual representations to clearly illustrate interactions. The platform should also foster community inclusivity and broaden activity domains. Finally, global accessibility in location selection should be supported in the mobile version.

List and Status of All Project Deliverables

Below is a summary table listing all major deliverables required for Customer Milestone 1, along with their current completion status and relevant links.

Deliverable Description Status Link / Reference
Revised Software Requirements Specification (SRS) Requirements document updated to align with W3C standards and customer feedback. Existing requirements were reviewed, clarified, and expanded. 🟢 Completed Requirements Wiki Page
Revised Software Design (UML Diagrams) Use case, class, and sequence diagrams were revised according to updated requirements. The class structure was refined to better represent the project architecture, sequence diagrams were aligned with the new class diagram and corrected for alt fragments, and new admin features were added to the use case diagrams. 🟢 Completed Design Diagrams Wiki Section
Team Development Policies The team follows clear collaboration and version control standards. The communication plan (revised for CMPE451) defines weekly meetings, rapid communication channels, and lab coordination. Existing Git conventions from CMPE352 are maintained, including branch naming (name/field/topic) and Conventional Commits for structured commit history. 🟢 Completed Communication Plan, Commit Message Standards, Branch Naming Standard
Project Plan The project plan is structured around five GitHub milestones that define development phases and deliverables. Milestones 0.5 and 1 have been largely completed, covering requirements, design updates, and deployment of initial core features (login, register, post assistance, volunteer, visiting profile). Milestones 1.5, 2, and 3 are scheduled for MVP delivery and final deployment. Each milestone includes specific deliverables and future objectives. Even though we have defined objectives and deliverables, plans are prone to change which is their strength. 🟡 In Progress Milestone 0.5 – Renaissance, Milestone 1 – init, Milestone 1.5 – DaVinci, Milestone 2 – MVP Delivery, Milestone 3 – Final Delivery
Weekly Reports and Meeting Notes Weekly reports and meeting notes are regularly maintained on the wiki, including summaries of internal discussions and customer meetings. These records ensure consistent tracking of progress, decisions, and feedback. 🟢 Completed Meeting Notes Wiki Section
Milestone Review The milestone review is written collaboratively and the full review is compiled. 🟢 Completed —
Individual Contributions You can see the individual contributions in this page. 🟢 Completed —
Pre-release Version of the Software Pre-release created on 21 October 2025 including full source code (frontend, backend, mobile) and an Android APK file. The release contains all features implemented for this milestone. 🟢 Completed Pre-release on GitHub

Evaluation of the Status

We now have fully functional Frontend, Mobile, and Backend components that deliver both the planned features and several additional improvements beyond our initial schedule. Our documentation, including meeting notes, implementation documentations, and lab reports, along with our repository structure and Wiki page, are well-organized and consistently follow established conventions.

Despite these achievements, a few areas still require attention. The system currently lacks HTTPS certificate and accessibility features, both of which are critical for ensuring user trust, data protection, and inclusivity.

To address these issues promptly, we have begun the process of obtaining and configuring an HTTPS certificate. In parallel, we have opened an issue in our repository to revise the milestone deliverables, incorporating a structured plan for the implementation of accessibility features. This ensures that future development efforts remain organized, transparent, and aligned with our overall project goals.

Evaluation of tools and processes for project management

Tools: Github Projects

To effectively manage our project tasks and monitor overall progress, we started using GitHub Projects. This tool served as our central hub for organizing work, tracking progress, and maintaining visibility across the team.

How it was used: GitHub Projects proved instrumental in structuring our work. We effectively utilized its iteration view for granular task management within our development cycles, enabling us to decompose larger objectives into manageable items. The roadmap view provided a higher-level overview, helping us visualize the project's trajectory and key milestones over time. Each task was assigned, its status updated, and progress was tracked directly within the platform.

Enhanced Tracking: GitHub Projects significantly "improved our tracking." It offered a clear, centralized location for all tasks, making it easy for team members to see what needed to be done, who was responsible, and the current status. This clarity was invaluable for individual accountability and team alignment.

Comprehensive Visibility: The various views (backlog, roadmap) provided excellent visibility into both granular task progress and the broader project timeline. This helped us anticipate potential bottlenecks and communicate progress.

Challenges/Limitations: A notable limitation we encountered was the absence of custom automated workflows in that would synchronize updates between issues and the Project board. This meant repetitive manual status assignments and updates to field values, rather than having these actions triggered automatically by changes in issue progress. This occasionally added overhead and required manual maintenance to ensure the project board accurately reflected the current state of work.

Effective communication and a structured approach to our work were vital for our team's cohesion and productivity.

Processes: Iteration-based Development

How it was implemented: We adopted a development cycle inspired by Agile methodologies, operating in 2 or 3-week long iterations. This structured approach allowed us to focus on a defined set of deliverables within each period. Complementing this, we held weekly syncs every Thursday. These meetings served as a crucial touchpoint for the entire team, providing a dedicated forum for updates, discussions, and problem-solving.

Improved Efficiency: The "iterations improved efficiency by dividing the tasks" into manageable chunks. This fostered focused work and made progress easier to measure. It allowed us to deliver value incrementally and adapt to changes more readily.

Accountability and Alignment: Weekly syncs ensured that everyone was aware of individual and team progress, upcoming challenges, and any blockers. They provided a regular forum for discussion, decision-making, and real-time problem-solving, keeping the team aligned with project goals and fostering a strong sense of shared ownership.

Predictability: The consistent rhythm of iterations and syncs brought a welcome sense of predictability to our workflow, which aided in planning, managing expectations, and providing regular updates.

Challenges/Limitations: The initial planning and breakdown of tasks for each 2-3 week iteration required dedicated time and effort. If not done thoroughly, this could occasionally lead to mid-cycle adjustments or a less clear focus for the team.

**Covered Requirements:

1. Functional Requirements

1.1 User Requirements

1.1.1 Registration/Login

  • 1.1.1.1 Guest users shall be able to register using their credentials. These credentials are: Name, surname, username, e-mail address and phone number.
  • 1.1.1.2 Registered users shall be able to log in using their e-mail address and password.
  • 1.1.1.5 Passwords shall meet minimum strength as defined in the glossary, without any additional complexity rules.
  • 1.1.1.6 Credentials shall be stored with strong one-way hashing.
  • 1.1.1.8 Registration shall include explicit consent to privacy/terms; collect minimum necessary data only. (Partially Implemented)

1.1.2 Guest User

  • 1.1.2.1 Guest users shall be able to view public assistance requests but cannot interact with them.
  • 1.1.2.2 To post a request or volunteer, guest users shall register and log in.
  • 1.1.2.4 Where interaction is disabled for guests, the UI shall clearly explain why and how to enable access (register/login).

1.1.3 Registered User

  • 1.1.3.1 Registered users shall be able to create, edit, and delete assistance requests. (except delete)
  • 1.1.3.2 Registered users shall be able to volunteer for available requests.
  • 1.1.3.3 Registered users shall have access to a dashboard displaying their current activities and past activities.
  • 1.1.3.4 Requesters shall be able to cancel or update their tasks.
  • 1.1.3.5 Registered users shall be able to enter location for tasks manually.
  • 1.1.3.8 Location entry shall support locale formats; exact location is hidden from public by default. (Partially Implemented)

1.1.6 Personal Page

  • 1.1.6.1 The system shall display each registered user’s essential information -including name, past and active tasks, average rating, total completed tasks, and reviews- without revealing the registered user’s location.
  • 1.1.6.2 Registered users shall be able to edit their personal information.
  • 1.1.6.3 Sensitive data (e.g. phone, exact location) shall not be public by default.

1.1.7 Feed

  • 1.1.7.2 All users shall be able to filter assistance requests based on relevant criteria (e.g., category, location, urgency) to facilitate easy discovery.

1.1.8 Task Creation & Management

  • 1.1.8.1 Tasks shall include: title, description, category, location, deadline, requirements, urgency level and volunteer number.
  • 1.1.8.2 All users shall be able to categorize tasks (groceries, tutoring, repairs, etc.).
  • 1.1.8.3 Volunteers shall be able to browse and search available tasks. (Partially Implemented)
  • 1.1.8.4 All users shall be able to track task status (posted, assigned, in-progress, completed). (Partially Implemented)
  • 1.1.8.11 Task data shall be stored securely and only shared with authorized users (e.g., assignee, requester). (Security & Protection)

1.1.9 Task Assignment & Completion

  • 1.1.9.1 Registered users shall only be able to see the exact location and phone number once they are assigned to the task.
  • 1.1.9.3 Requesters shall be able to select the assignee among volunteers. Both one-by-one and group selection approaches shall be supported.
  • 1.1.9.4 Requesters shall be able to change the assignee for a task after it was assigned to a volunteer.
  • 1.1.9.5 Registered users shall not be able to volunteer for a task once it has been assigned. However, if the assignment is canceled, the task shall become available for new volunteers.
  • 1.1.9.6 Communication of sensitive details (phone, address) shall be encrypted in transit and access-logged.

1.2 System Requirements

1.2.1 Communication & Notifications

  • 1.2.1.1 The system shall send real-time notifications when a registered user’s request is accepted or updated.
  • 1.2.1.3 Registered users shall be allowed to share their phone numbers only after a task has been assigned. A built-in chat feature is not required.
  • 1.2.1.5 Notifications shall respect user privacy: they shall not include sensitive personal data (e.g., phone number, exact address) unless explicitly authorized.
  • 1.2.1.8 All notification events shall be logged securely to provide traceability and accountability.

1.2.2 Search (Partially Implemented)

  • 1.2.2.1 The system shall provide a search function allowing all users to find assistance requests based on keywords, location, and category. (except location)
  • 1.2.2.5 The task titles shall be searchable.

2. Non-Functional Requirements

2.3 Privacy and Security

  • 2.3.1 The platform shall comply with the General Data Protection Regulation (GDPR), ensuring that all personal data is processed in a lawful, transparent, and purpose-specific manner.
  • 2.3.2 The platform shall adhere to the Turkish Law on the Protection of Personal Data (KVKK) by enforcing data minimization, ensuring data accuracy, and implementing robust security measures to prevent unauthorized access and data breaches.
  • 2.3.4 Privacy by Design shall be applied: collect only minimum necessary data, support anonymization/pseudonymization where possible, and provide users with clear consent and control over their data.
  • 2.3.5 All sensitive data shall be encrypted both in transit and at rest, with strong authentication and access control mechanisms.

2.4 UI/UX (Usability)

  • 2.4.1 The user interface shall be designed for maximum usability, featuring intuitive navigation and a clear presentation of critical information (such as task details and user ratings) to facilitate a seamless user experience.
  • 2.4.2 The interface shall follow consistent and predictable navigation patterns, adapting to different devices and contexts (responsive/adaptive design).
  • 2.4.3 The system shall support inclusive design principles, ensuring equitable access across abilities, cultures, and demographics, and avoiding discriminatory patterns. (Partially Implemented)

Individual Contributions

Üveys Aydemir

Ahmet Eren Aslan

  • Responsibilities:
    • Frontend development for web, integration with backend APIs, and reviewing major PRs related to the frontend.
  • Main Contributions:
    • Implemented core frontend features: Login/Register page, Home Page, Post Assistance, Volunteering, and Visiting Profile.
    • Integrated backend functionality with frontend components.
    • Developed Request Detail page with edit and delete functionalities.
    • Maintained weekly reports and documentation for milestone progress.
  • Code-related Significant Issues:
    • Issue #235 – Implemented frontend of Login/Register page
    • Issue #261 – Developed frontend for Post Assistance feature
    • PR #269 – Integrated backend for login and registration
    • PR #314 – API integration for Home Page
    • PR #342 – Added Request Detail page with edit/delete
  • Non-code-related Significant Issues:
    • Issue #220 – Updated requirements according to W3C standards
    • Issue #310 – Prepared frontend documentation for the first milestone
    • Issue #378 – Documented Meeting 4 notes
    • Issue #252 – Configured GitHub Projects for milestone tracking
  • Pull Requests Created, Merged, and Reviewed:
  • Additional Information:
    • Participated actively in meetings and agenda preparation.
    • Contributed to milestone planning and deployment preparations.

Musa Kaan Güney

  • Responsibilities:

    • Frontend development for web, integration with backend APIs, and reviewing major PRs related to the frontend.

  • Main Contributions:

    • Implemented core frontend features: Login/Register page, Home Page, Post Assistance, Volunteering, and Visiting Profile.
    • Integrated backend functionality with frontend components.
    • Maintained weekly reports and documentation for milestone progress.
    • Refactored the components and pages of frontend.
    • Developed All Request Page in home page.
    • Developed Profile page with edit profile features.

  • Code-related Significant Issues:

  • Non-code-related Significant Issues:

    • Issue #208 – Update & Add Milestones
    • Issue #219 – Updated requirements according to W3C standards
    • Issue #362 - Deploy the current version of the App

  • Pull Requests Created, Merged, and Reviewed:

  • Additional Information:

    • Participated actively in meetings.
    • Contributed to milestone planning and deployment preparations.

Alperen Garip

  • Responsibilities:

    • Developer for the mobile application (React Native/Expo).
    • Helped to implement key mobile features, backend integrations, and bug fixes.
    • Reviewed and merged PRs related to mobile development.
    • Maintained weekly effort logs and documentation for Customer Milestone 1.

  • Main Contributions:

    • PR #411 – Helped to solve a bug about number of volunteered while selecting.
    • PR #417 – Reviewed and merged teammates’ PRs related to mobile functionality.
    • PR #418 – Resolved a privacy bug where phone numbers were visible to non-assigned users.
    • PR #421 – Fixed request detail errors and configured deployed backend IP for the mobile app.
    • PR #422 – Added new signup field validations for improved user experience.
    • Documented personal weekly effort reports and milestone progress on the wiki.

  • Code-related Significant Issues:

    • Issue #391 – Fixed request details error as volunteer/guest.
    • PR #417 – Reviewed and merged teammate’s fixes for status message and related errors.
    • PR #418 – Fixed phone number visibility bug.
    • PR #421 – Fixed request details and configured deployed IP.
    • PR #422 – Added signup field validations.

  • Non-code-related Significant Issues:

    • Issue #224 – Updated Use Case Diagram and the Register Feature Diagram.
    • Issue #369 – Wrote UX Design part of Demo documentation.
    • Issue #372 – Wrote Script part of Demo documentation.
    • Closed and reviewed several coordination and meeting issues (#232, #238, #246, #271, #281, #349).
    • Updated personal effort logs on the wiki for each week.

  • Pull Requests Created, Merged, and Reviewed:

    • Created: #418,#421,#422
    • Merged: #417
    • Reviewed: #417
    • Conflicts & Resolutions: No major conflicts occurred; minor syncs handled during merges into mobile/development.

  • Additional Information:

    • Maintained the Efforts Page – Alperen Garip.
    • Participated in weekly meetings, lab meetings and milestone planning.
    • Contributed to documentation and demo preparations for Customer Milestone 1.

Eray Yüklü

  • Responsibilities

    • Backend architecture maintenance and documentation from previous semester (CMPE 352)
    • Requirements engineering and W3C standards compliance
    • Customer meeting preparation and elicitation question development
    • Frontend development (transitioned mid-milestone due to team workload distribution)
    • Cross-platform integration and deployment coordination
    • Meeting facilitation, note-taking, and issue management

  • Main Contributions

    • Backend Foundation & Documentation: Successfully migrated and maintained the backend system developed in CMPE 352, ensuring its reliability for Milestone 1. Reviewed and approved the backend migration PR #249, analyzed existing API documentation, and identified areas for improvement #232.

    • Requirements & Standards Compliance: Updated UML Sequence diagrams for Select Assignee and Recover Password features to reflect current implementation #225. Reviewed and validated sequence diagram implementations from team members #228.

    • Customer Engagement & Elicitation: Organized and facilitated customer alignment meeting #263, prepared comprehensive elicitation questions #265, created detailed meeting agenda #266, and implemented post-meeting requirement updates #268. Led backend team meeting specifically for elicitation question preparation #275.

    • Frontend Development (Critical Mid-Milestone Transition): Recognizing the frontend team's heavy workload and leveraging the stable backend foundation, transitioned to active frontend development role for the second half of Milestone 1. This demonstrated versatility across project domains, which is highly valued in this course. Key implementations include:

      • Developed Volunteer a Task feature #290
      • Implemented Select Volunteer functionality #335 with PR #334
      • Created Request Details Page with comprehensive functionality PR #342
      • Fixed critical page reload bug after volunteering action #347
      • Reviewed the resolved UI issues including categories, cards, and password reset flows PR #331

    • Backend Logic Refinement: Implemented critical task status management logic to enforce count-based POSTED/ASSIGNED transitions #383 with PR #384, ensuring tasks remain in POSTED status until volunteer capacity is reached.

    • Deployment & Integration: Led deployment efforts for Milestone 1 #362, resolved critical backend-frontend connection issues on remote server #404 with PR #416. Conducted intensive cross-platform troubleshooting with mobile team to resolve authentication issues #419, implementing CORS configuration fixes PR #420 through synchronous HTTP status monitoring between GCP VM server and Expo-Go mobile environment.

    • Demo Preparation: Created comprehensive demo users and sample tasks for Milestone 1 presentation #425 to showcase platform functionality effectively.

    • Project Management & Documentation: Systematically created and organized parent-child issue hierarchies from meeting notes with proper labels and assignments Issues #217-232. Took detailed meeting notes and maintained wiki documentation for Meeting 1 (Wiki Link) and Meeting 3 (Wiki Link). Created Lab 3 report documentation (Wiki Link). Updated and managed milestone implementation issue due dates #313.

    • Code-related Significant Issues

      • Issue #225 – Updated UML Sequence diagrams for Select Assignee and Recover Password
      • Issue #232 – Analyzed backend implementation and reviewed API documentation
      • Issue #290 – Implemented Volunteer a Task frontend feature
      • Issue #335 – Developed Select Volunteer frontend functionality
      • Issue #347 – Fixed page reload bug after volunteering
      • Issue #383 – Implemented task status logic for POSTED/ASSIGNED transitions
      • Issue #404 – Resolved backend-frontend connection issues on deployment server
      • Issue #419 – Fixed authentication issues for mobile platform access

    • Non-code-related Significant Issues

      • Issue #216 – Attended and participated in Thursday evening team meeting
      • Issue #263 – Organized Customer Alignment Meeting
      • Issue #265 – Prepared comprehensive elicitation questions for customer meeting
      • Issue #266 – Created detailed customer meeting agenda
      • Issue #268 – Implemented post-meeting requirement updates
      • Issue #275 – Organized backend team meeting for elicitation questions
      • Issue #296 – Created Lab 3 report and documentation
      • Issue #307 – Took detailed notes during Meeting 3
      • Issue #313 – Updated due dates for Milestone 1 implementation issues
      • Issue #362 – Coordinated deployment of current application version
      • Issue #425 – Created demo users and tasks for Milestone 1 presentation
      • Issue #446 – Documented Milestone 1 personal contributions

  • Pull Requests Created, Merged, and Reviewed

    • Created & Merged

      • PR #334 – feat: FRONTEND - Select Volunteer Page
      • PR #342 – feat: FRONTEND - Request Details Page
      • PR #384 – feat(task-status): enforce count-based POSTED/ASSIGNED logic
      • PR #416 – fix(deployment): point frontend API to 35.222.191.20:8000
      • PR #420 – fix(auth): allow all origins (intensive cross-platform debugging with mobile team)

    • Reviewed & Merged

      • PR #249 – Old Backend Added (critical migration from CMPE 352)
      • PR #331 – fix(ui): categories, cards, forgot and reset password
      • PR #389 – Reviewed and approved frontend improvements

    • Issues Reviewed

      • #228 – Diagram Update(Cancel Assistance & Ban User)
      • #235 – Login/Register frontend review
      • #252 – GitHub Projects configuration review
      • #253,#348 – Other Team Members' Personal Weekly Report review
      • #285 – Requirements Update Review
      • #330 – Frontend UI Refactors Review

    • Conflicts & Resolutions: No major merge conflicts encountered. Minor conflicts during PR integrations were resolved through careful coordination with team members. The authentication fix PR #420 required extensive synchronous debugging sessions with the mobile team, monitoring HTTP status codes between the GCP VM server and Expo-Go mobile environment to identify and resolve CORS configuration issues.

    • Additional Information

      • Cross-Domain Expertise: Demonstrated versatility by actively contributing to backend architecture, requirements engineering, customer engagement, frontend development, and deployment operations throughout Milestone 1. This comprehensive involvement across multiple project domains aligns with course expectations for holistic participation.

      • Meeting Participation: Consistently attended all team meetings (#216, #256, #275, #373), took detailed notes, and facilitated discussions. Created comprehensive meeting documentation on the project wiki.

      • Issue Management Excellence: Systematically created 15+ well-structured parent-child issues from meeting notes in Week 1 (#217-232), establishing clear task hierarchy with appropriate labels, assignments, and categorization. Maintained consistent weekly personal reporting (#238, #278, #336, #390).

      • Physical Collaboration: Organized in-person meeting with team member Erdem to review and resolve deployment issues from previous semester #231, demonstrating commitment to hands-on problem-solving. I met with frontend team in the CMPE Lounge in the Week-3's weekend and we implemented the features that I mentioned above. Also we met with entire team 1 day before 1st Milestone and worked long hours, handle the deployment problems and authentication problems with Mobile team collaboratively.

      • Strategic Pivot: Successfully transitioned from backend-focused role to active frontend development when team needs shifted, maintaining high-quality contributions across both domains. This flexibility was crucial for Milestone 1 success given the stable backend foundation from CMPE 352 and increased frontend workload.

      • Deployment Leadership: Took ownership of critical last-minute deployment challenges, coordinating across web and mobile platforms to ensure successful Milestone 1 demonstration. The authentication fix particularly required intensive collaborative debugging sessions with the mobile team.

Hayrettin Eren YILDIZ

Ali Sonmez

  • Responsibilities:

    • Project planner
    • Communicator
    • Developer in the Frontend Team

  • Main Contributions:

    • Planning what to implement when
    • Organizing meetings
    • Frontend codes for:
      • Login & Register pages
      • Post Assistance
    • Debugging both Frontend and Backend

  • Code-related Significant Issues:

    • #235 – Login & Register
    • #258 – Home Page
    • #261 – Post Assistance Feature
    • #290 – Volunteer a Task Feature
    • #303 – Visiting Profile Feature

  • Non-code-related Significant Issues:

    • #218 – Requirement Update
    • #264 – Schedule Customer Meeting
    • #287 – Update & Add Milestones

  • Pull Requests Created, Merged, and Reviewed:

  • Additional Information:

    • Thought thoroughly on what to do better than the previous semester.
    • Thought about the meeting agendas.
    • Thought about planning and how to optimize our work.

Abdullah Rüzgar

Yusuf Kaan Akçay

  • Responsibilities:

    • Contributor to planning, elicitation, and documentation processes
    • Actively involved in team coordination and customer communication
    • Supported both frontend and backend documentation and analysis efforts

  • Main Contributions:

    • Contributed to the elicitation process by preparing agendas and question sets for customer meetings
    • Helped refine and update Rate & Review and Post Assistance diagrams in collaboration with the team
    • Contributed to preparing backend and frontend implementation documentation for the first milestone
    • Participated in planning and review discussions to align tasks with milestone goals

  • Code-related Significant Issues:

    • #342 – Contributed to the Request Detail Page implementation, including edit and delete functionalities

  • Non-code-related Significant Issues:

    • #210 – Project Review and Planning
    • #226 – Updated Diagrams (Rate & Review, Post Assistance)
    • #263 – Organized Customer Alignment Meeting
    • #265 – Prepared Elicitation Questions
    • #266 – Drafted Customer Meeting Agenda
    • #268 – Supported Post-Meeting Update Implementation
    • #309 – Contributed to Backend Implementation Documentation
    • #310 – Contributed to Frontend Implementation Documentation
    • #370 – Prepared Web Scenarios

  • Pull Requests Created, Merged, and Reviewed:

    • Contributed: #342
    • Conflicts & Resolutions: No major conflicts encountered; minor syncs resolved collaboratively.

Salih Erdem Koçak

  • Responsibilities:

    • Developer in the Backend Team
    • Backend architecture maintenance and documentation from previous semester (CMPE 352)
    • Requirements engineering and W3C standards compliance
    • Customer meeting preparation and elicitation question development

  • Main Contributions:

    • Backend Foundation & Documentation: Successfully migrated and maintained the backend system developed in CMPE 352, ensuring its reliability for Milestone 1. Created PR #249, analyzed existing API documentation, and identified areas for improvement #232 together with Eray.

    • Customer Engagement & Elicitation: Joined customer alignment meeting #263, prepared comprehensive elicitation questions #265. Attended backend team meeting specifically for elicitation question preparation #275.

    • Bug Fix: Fixed the reload bug related to the backend not being correctly operated, opened the pr [#365] (https://github.com/bounswe/bounswe2025group8/pull/365), at the end the pr would not merged because same fix also applied on a parallel branch from a teammate.

  • Code-related Significant Issues:

    • #231 – Deployment
    • #232 – Backend Documentation

  • Non-code-related Significant Issues:

    • #223 – Diagram Update
    • #265 – Prepare Elicitation Questions
    • #285 – Requirement Update

  • Pull Requests Created:

    • Created/Contributed: #249, #365

    • Conflicts & Resolutions: No major conflicts occurred.

  • Additional Information:

    • Actively joined meetings and labs, discuss the project with my teammates.

Mustafa Batuhan Büber

  • Responsibilities:

    • Development of mobile
    • Deployment of mobile

  • Main contributions:

    • Collaborated implementation of Milestone 1 features within the mobile team
    • Tested the mobile features for bugs and fixed them with the mobile team
    • Created a mobile scenario for the Milestone Demo and participated in the mobile functionality demonstration

  • Code-related significant issues:

  • Non-code-related significant issues:

  • Pull requests that I have created and worked on:

    • PR #306 Fix IP and port settings, and fix web login issue

  • Pull requests that I have worked on:

    • PR #411 Bug about number of volunteered while selecting

  • Pull requests that I have reviewed:

    • PR #417 Fixed status message and errors
    • PR #418 Fixed phone number being displayed when user is not assigned
    • PR #421 Fixed errors in request details, configured deployed IP
    • PR #422 Fixed authentication logic
    • PR #423 Added mobile project folder from mobile/development branch

  • Additional Information:

    • Actively joined meetings and labs, and discussed the features with my teammates.
    • Took part in the demo presentation, handling the mobile scenario.
    • Maintained my efforts page regularly.

Additional Links to Design