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

Customer Milestone 1 Report of CMPE 451 Fall 2025

Introduction

This is the milestone report for our group project, bounswe2025group5. We are a group of dedicated students, committed to building WasteLess, a comprehensive platform designed to empower users to track, manage, and reduce their environmental footprint through features like waste logging, community challenges, and a supportive forum. This report is written for primarly addressing the deliverables and current status of the project.

Team Members

Table of Contents

1. A Summary of The Project Status and Any Changes That Are Planned for Moving Forward

Project Status

For the milestone 1, the objective was to bring the application up again with enhanced requirements and new features. In defining the new features; W3C standards, smart environments, ethics and data protection, as well as feedback from the previous release of the project is taken into account. We decided to change the challenge system completely and to separate waste log mechanism from it by considering the feedback to the previous release. The SRS and design diagrams are updated considering these new features. We also decided to reimagine the frontend of the application, from scratch, to offer a better user experience and ensure more systematic development environment.

The main bottleneck of the implementation is the development in the frontend. The essential features such as presenting a main page, profile page, feed page, waste goal page, and challenges page are implemented with a consistent UI design. Users are able to see new posts in feed page, (or in feed section in the main page), like posts, comment to posts, save posts to see them later on their profile page, search for them, and post a new one through the feed page. Users can create waste goals, can add logs to achieve their goals, delete, and edit their goals through the goals page. Users are able to create challenges to accomplish a specific recycling goal in a limited time and a specified amount, join one, and see their position on the challenge's leaderboard. Users can customize their profile pages with a biography and profile picture, and view their shared and saved posts. The same features are implemented in the web application and the mobile application with a compatible user interface. Furthermore, a secure communication between the applications and the backend server can be made through the https protocol implemented by the backend team. For further detail, see the requirements section of the report.

The backend server is redesigned with REST API standards and has new endpoints to address new requests required for the new features such as the reimagined challenge system. The frontend side of the project is developed from scratch and it is brought to a stage where it can provide all essential features in a visually consistent and appealing manner in a short timeframe for the first milestone. The mobile app is made fully functional and optimized to implement the new features, maintaining a consistent interface and user experience across web and mobile platforms.

Status of the Apps

Status of the Release

Moving Forward

Even though main features are implemented and quite a number of requirements are met, there are still some improvements yet to be made and features to be implemented towards the milestone 2. As moving towards the second milestone, the features that will be prioritized are notifications, displaying waste goals as statistics, follow feature, admin/moderator roles, and accessibility features such as keyboard navigation. These features are part of the SRS as well, so it is necessary to move towards them. Additionally, considering the feedback from the customer, we decided to lean toward features that emphasize the impact of the application on the environment to better motivate the users. We planned to show statistics in the main page such as "X many plastic bottles is recycled with this application" or "Y many trees are saved". Another feature that is planned is that to enable moderators to show completed challenges in a section to emphasize the real impact of the application. Other than these, the customers were quite satisfied with the progress of the project, therefore there is no major changes required for the project plan. To summarize, we decided to stick with the project plan to achieve all the requirements with more emphasis on showing the impact of the application to the users.

2. A Summary of the Customer Feedback and Reflections

The Milestone 1 presentation proceeded smoothly and without any technical complications. Throughout the session, the client and their assistants appeared engaged and expressed visible satisfaction, as evidenced by their positive reactions and remarks. At the conclusion of the meeting, the client stated, “Great, nice. The scenarios are good as well,” which reflected overall approval of both the content and delivery of the presentation.

Customer Feedback

The client provided constructive and insightful feedback that will guide subsequent iterations of the project:

  • Challenge Creation Process: The client emphasized the importance of fostering user-driven challenge creation, suggesting that new challenges should naturally emerge from community interactions. For instance, a user observing an environmental issue in Kilyos could initiate a related cleanup challenge. This suggestion aligns with our existing forum feature, where users can post messages such as “This place needs cleaning,” allowing others to convert these posts into formal challenges. This mechanism supports organic, community-driven challenge proposals.

  • Impact Visibility: The client highlighted that users are more motivated when they can observe the tangible outcomes of their contributions. They expressed particular interest in how the system could present long-term impact metrics, such as quantifying “What difference did my challenge make?” In response, we demonstrated the Profile → Reduction Statistics (Mock) section, noting that this component could be expanded in future milestones to include richer visualizations that display cumulative outcomes.

  • Overall Assessment: The client concluded by stating that we “covered everything,” indicating that all primary expectations were met and that the demonstrated functionalities aligned well with the intended project objectives.

Team Reflections

Following the feedback session, the development team held an internal evaluation meeting to identify potential areas for improvement and refinement:

  • The Impact Visualization component will be enhanced through before-and-after comparisons and more engaging narrative-style progress indicators that visually convey the real-world outcomes of user efforts. This can be done with visualizations of total waste reduction, number of completed cleanups with charts and graphs or symbolic achievements that represent the broader impact of user actions (e.g., visual cues showing that collected bottle caps could contribute to a wheelchair donation initiative). This will help to strengthen motivation and sense of purpose for users.
  • The team reaffirmed the importance of bilingual support (Turkish and English) across interfaces. This requirement followed directly from our scenario, which features a teen user and his Turkish-speaking grandfather.
  • Performance-related aspects, particularly server RAM consumption and mobile application loading times, were identified as areas for optimization in upcoming milestones. Although these caused minor latency during the presentation, the client did not comment on them, suggesting that the overall user experience remained satisfactory.

In summary, the client’s feedback confirmed that the project is progressing in the right direction while providing valuable insights for improving usability, accessibility, and impact representation in future development phases.

3. List and Status of All the Project Deliverables

Deliverable Status Related Link
Requirements Done Requirements
Use Case Diagram Done Use Case Diagram
Class Diagram Done Class Diagram
Sequence Diagram Done Sequence Diagram
Project Plan Done RoadMap General Plan
Git Contribution Plan/Standards Done Contribution Guidelines
Communication Plan Done Communication Plan
Meeting Notes Done Lab Reports Meeting Notes Team Meeting Notes
Individual Contributions Done Individual Contributions
Pre-Release Of The Software Done 0.1.0-beta
(Extra) Deployment Milestone Done Link to Milestone
(Extra) Postman Collections Done Postman

4. Evaluation of the Status of Deliverables and Its Impact on Your Project Plan (reflection)

Revised Software Requirements Specification (SRS)

We have revised the requirements based on the new expectations on adhering to W3C Standards, Smart Environments and Ethics & Data Protection. We added requirements to make our application more accessible to users by adding multi-language support, adding color contrast & keyboard navigation etc. We have also made the application more engaging and community driven through challenges, leaderboards and social interaction features such as following other users. Lastly, for data protection, we configured HTTPS to keep the users' data secure, added account deletion to delete all user data, and as a principle, we started collecting less data overall.

While working on revising the requirements, we had new questions regarding them which needed customer feedback. Therefore, we had a customer meeting where we refined our requirements even more. After the meeting, we prepared our final requirements specification which serves as a solid foundation to our project.

Revised software design (UML diagrams)

Based on the revised requirements specification, we needed to update the UML diagrams to reflect the changes. After clearly defining the revised requirements, we have updated the Use Case, Class and Sequence diagrams. In their current state, they correctly reflect the requirements.

Team development policies: communication plan, Git development policies (e.g., branching, committing)

Before we started the development, we needed to have a solid planning regarding the methods we would use during development. Namely, we needed to clarify how we would communicate throughout the development phase, and we needed to define the policies we should follow during coding in order to stay coordinated and consistent. These plans helped us organize more efficiently which helped us throughout development.

Project plan

Before starting on developing the application, we needed to plan our steps carefully in order to not fall behind deadlines and get flooded with tasks. Therefore, we created the project plan where we specified the clearly defined tasks and milestones to come. However, after revising the requirements, we updated the project plan to reflect the new requirements and their planning. Moreover, while planning, we realized the need of our own milestones which would help us organize before the actual milestones. This planning helped us stay organized, and carefully manage the last days of the milestone without being flooded with work.

Weekly reports and any additional meeting notes

To stay organized and to prepare the deliverables, we had weekly meetings and lab sessions. During the lab sessions, we prepared and planned the deliverables, and we also documented our discussions during these sessions. During the weekly meetings, we shared tasks among us, discussed implementation details and planned our next steps. These sessions and meetings helped us get quickly organized and be aware of each other's tasks and progresses.

Milestone Review

For the milestone, we prepared the milestone review. While writing it we were able to reflect the progress we have made and the lessons we have learned. It has helped us to see how our planning in the early stages enabled us to finish the deliverables and the tasks in time.

A pre-release version of your software

Before the milestone, in order to show the current status of the project, we created its pre-release version. Before this release, we finished up the remaining functionalities needed for the milestone which helped each subteam get organized better. During the demo we showed this version of the application that worked as intended which showed us the benefits of meticulous planning and organization.

(Extra) Deployment Milestone

While creating the project plan, we saw the need for extra milestones in order to organize better and check our current status. Therefore, before the first milestone, we created the Deployment Milestone. We specified the deliverables as web deployment and mobile deployment. Even though the mobile deployment was 1 day late, it still helped us concentrate on these tasks and deal with them without being burdened with all of the tasks on the last day of the first milestone.

(Extra) Postman Collectibles

For testing the backend, we used Postman extensively. It helped us test the endpoints and be able to work on the backend as a team.

Evaluation

For the milestone, we were able to finish all deliverables in time thanks to planning beforehand. We were able to finish them without being burdened with too many tasks at the same time. Moreover, we didn't need to change the dates of the tasks we have created in the project plan which showed that we obeyed the plan and we were careful while creating it.

5. Evaluation of Tools and Processes You Have Used to Manage Your Team Project

  • Postman : An API platform for building, testing, and documenting RESTful APIs. It allows developers to send HTTP requests, inspect responses, and automate API testing workflows.
  • Figma : A collaborative web-based design tool used for UI/UX design. It enables teams to create wireframes, prototypes, and interface mockups in real time.
  • Docker : A containerization platform that packages applications and their dependencies into lightweight containers, ensuring consistent behavior across different environments.
  • Google-Cloud-SQL : A fully managed relational database service by Google Cloud that supports MySQL, PostgreSQL, and SQL Server. It simplifies database management tasks like backups, patching, and scaling.
  • DigitalOcean : A cloud infrastructure provider offering scalable virtual machines (droplets), managed databases, and other tools for deploying and managing applications.
  • Expo is a framework and platform for universal React applications. It helps you develop, build, and deploy React Native apps quickly, often without needing to touch native code.
  • Android-Studio is the official IDE for Android development, and it includes tools to test Android apps on virtual devices called emulators.
  • Cursor, Copilot are AI agents and helpers for coding.

6. The Requirements Addressed in This Milestone

Requirements Status

We classify the status of the requirements as follows:

  • ✅ Done: Requirements that we finished implementing.
  • 🔜 Milestone 2: Requirements that will be implemented in the next release (Milestone 2).
  • 3️⃣ Milestone 3: Requirements that will be implemented in the milestone 3.
Requirement Number Description Status
1.1 User Requirements
1.1.1 Account Requirements
1.1.1.1 Users shall be able to register for the system using an email, a username and a password. ✅ Done
1.1.1.2 Registered users shall be able to log in to the system with valid credentials. ✅ Done
1.1.1.3 Registered users shall be able to reset their passwords. 🔜 Milestone 3
1.1.1.4 Registered users shall be able to permanently delete their accounts... ✅ Done
1.1.1.5 Registered users shall be able to log out from the system. ✅ Done
1.1.1.6 Registered users shall be able to display their waste reduction statistics. 🔜 Milestone 2
1.1.1.7 Registered users shall be able to edit their profile, including username and goals. ✅ Done
1.1.1.8 Registered users shall be able to set and update their waste reduction goals... ✅ Done
1.1.1.9 Registered users shall be able to upload a profile picture up to 2MB in size. ✅ Done
1.1.1.10 Unregistered users shall have limited, read-only access to the application... ✅ Done
1.1.2 Waste Tracking Requirements
1.1.2.1 Registered users shall be able to log their daily waste generation in grams or kilograms. ✅ Done
1.1.2.2 Registered users shall be able to categorize waste into at least five predefined types... ✅ Done
1.1.2.3 Categorized waste shall be tracked using different units based on the type... ✅ Done
1.1.2.4 Registered users shall be able to view historical waste data for at least the past 12 months. 🔜 Milestone 2
1.1.2.5 Registered users shall be able to visualize historical waste data through charts and bar graphs. 🔜 Milestone 2
1.1.3 Gamification and Challenge Requirements
1.1.3.1 Registered users shall be able to join community sustainability challenges... ✅ Done
1.1.3.2 Registered users shall be able to earn points for logging recycling. 3️⃣ Milestone 3
1.1.4 Post Requirements
1.1.4.1 Registered users shall be able to create and share posts containing tips... ✅ Done
1.1.4.2 Registered users shall be able to delete their own posts. ✅ Done (🔜 Milestone 2 for Web)
1.1.4.3 Moderator shall be able to see reports that are sent by users about a post. 🔜 Milestone 2
1.1.4.4 Moderator shall be able to delete a post if it includes inappropriate words... 🔜 Milestone 2
1.1.4.5 Registered users shall be able to save posts. ✅ Done
1.1.4.6 Registered users shall be able to like posts. ✅ Done
1.1.4.7 Registered users shall be able to comment on posts. ✅ Done
1.1.4.8 Registered users shall be able to share posts. ✅ Done
1.1.5 Incentive ,Reward and Feedback Requirements
1.1.5.1 Registered users shall be able to view available badge that they receive... 3️⃣ Milestone 3
1.1.5.2 Registered users shall be able to take badges from the forum activities automatically. 3️⃣ Milestone 3
1.1.5.3 Users shall submit feedback, suggest improvements... 🔜 Milestone 2
1.2 System Requirements
1.2.1 Performance and Storage
1.2.1.1 The system shall store user data, including waste logs... for a minimum of 3 years. ✅ Done
1.2.1.2 The system shall process and update waste reduction analytics within 5 seconds... ✅ Done
1.2.2 Waste Tracking Requirements
1.2.2.1 The system shall generate weekly and monthly visual reports summarizing waste data. 🔜 Milestone 2
1.2.2.2 The system shall calculate and display the percentage reduction in waste over time. 🔜 Milestone 2
1.2.2.3 The system shall generate graphs and charts for visualizing waste data. 🔜 Milestone 2
1.2.3 Gamification and Incentive Requirements
1.2.3.1 The system shall maintain leaderboards displaying the top 10 users in each challenge... ✅ Done
1.2.3.2 The system shall assign achievement badges when users reach predefined milestones... 3️⃣ Milestone 3
1.2.3.3 The system shall provide a badge catalog where each badge is described. 3️⃣ Milestone 3
1.2.3.4 The system shall assign achievement badges when users are in the first three places... 3️⃣ Milestone 3
1.2.4 Notification System Requirements
1.2.4.1 The system shall send notification to people for their progress about the goals... 🔜 Milestone 2
1.2.4.2 The system shall send notification to people for the update of the leaderboard situation. 🔜 Milestone 2
1.2.4.3 The system shall send notifications for likes and comments to their posts. 🔜 Milestone 2
1.2.4.4 The system shall send notifications when users they follow share a post. 🔜 Milestone 2
1.2.5 Post Requirements
1.2.5.1 The system shall support text, image, and link attachments in shared posts. ✅ Done
1.2.5.2 The system shall include tagging and categorization features... 3️⃣ Milestone 3
1.2.5.3 System shall provide semantic search over forum page. 3️⃣ Milestone 3
1.2.5.4 The system shall display a reminder message encouraging kindness... 🔜 Milestone 2
1.2.6 Standardization Requirements
1.2.6.1 The system shall model user interactions... using standardized vocabularies... 🔜 Milestone 2
1.2.6.2 The system shall represent user actions following the W3C Activity Streams 2.0... 🔜 Milestone 2
1.2.7 Localization Requirements
1.2.7.1 The system shall provide locale support where users can switch between Turkish and English... ✅ Done
1.2.7.2 The system shall have a default locale set to English... ✅ Done
2 Non-Functional Requirements
2.1 User Experience Requirements
2.1.1 Performance Requirements
2.1.1.1 The system shall provide a response time of under 2 seconds for 95% of user actions... ✅ Done
2.1.2 Usability and Accessibility Requirements
2.1.2.1 The platform shall support multilingual functionality... ✅ Done
2.1.2.2 The system shall provide tooltips, tutorials, or onboarding guides... 🔜 Milestone 2
2.1.2.3 All form inputs shall include inline validation to prevent errors before submission. 🔜 Milestone 2
2.1.2.4 The system shall require users to confirm critical, irreversible actions... 🔜 Milestone 2
2.1.2.5 All non-text content (images, icons, charts) shall have meaningful text alternative... 🔜 Milestone 2
2.1.2.6 Minimum color contrast ratio of 4.5:1 for text... 🔜 Milestone 2
2.1.2.7 Interactive elements shall be fully operable via keyboard. 🔜 Milestone 2
2.1.2.8 Visible focus indicators for all interactive elements... 🔜 Milestone 2
2.1.2.9 Navigational components shall be placed consistently through web pages. 🔜 Milestone 2
2.1.3 Waste Tracking Requirements
2.1.3.1 The system shall ensure waste tracking data is updated in real-time... 🔜 Milestone 2
2.1.3.2 The waste tracking module shall support batch data entry... 🔜 Milestone 2
2.2 Scalability Requirements
2.2.1 The platform should be designed for horizontal scalability... 🔜 Milestone 2
2.3 Security Requirements
2.3.1 User data shall be encrypted to prevent unauthorized access and data breaches. ✅ Done
2.3.2 The system shall enforce strong password policies that new passwords must be at least 8 characters long... 🔜 Milestone 2
2.3.3 The platform should comply with Turkish KVKK... ✅ Done
2.3.4 System shall ask user for KVKK approval to register. ✅ Done
2.3.5 During registration, the system shall only require the minimum data necessary... ✅ Done
2.3.6 System shall enable HTTPS access to the server... ✅ Done
2.4 Portability & Compatibility Requirements
2.4.1 The platform shall function correctly on modern web browsers... ✅ Done
2.4.2 The platform shall be responsive and function correctly on mobile devices... 🔜 Milestone 2
2.4.3 The platform shall support at least one screen reader... 3️⃣ Milestone 3
2.4.4 The platform shall support text resizing up to 200%... ✅ Done
2.5 Eco-Requirements
2.5.1 The platform shall prioritize hosting providers with certified renewable energy usage... 🔜 Milestone 2

7. Individual Contributions

7.1 Abdurrahman Arslan

Member

Abdurrahman Arslan, Group 5, Frontend Team

Responsibilities

Frontend Developer, Documenter, UI Designer

  • I was primarily responsible for the frontend implementation, UI/UX design and consistency, standardization across the project. My work involves developing major pages such as the feed, homepage, and post interaction features, while ensuring API integrations and reusable component design.

  • Main contributions: For this milestone, I focused on implementing user-facing functionalities (feed, post, comment, search, like/save systems) and ensuring consistent UI design with outputs like assets and color palette to share with people. I also contributed to frontend structure initialization and project documentation. In addition, I played an active role in reviewing PRs, resolving conflicts, and maintaining cross-team collaboration and design uniformity.

  • I contributed to frontend architecture planning, cross-platform coordination with the mobile team, and documentation efforts including technical research and adaptation of web standards (Activity Streams 2.0 and WCAG 2.1 AA).

Issues

Code-Related Significant Issues
Issue Explanation Issue Link
Conducted research about frontend testing tools with Eren #353
Planned and initialized frontend folder structure #354
Prepared and shared "copilot-instructions.md" file #355
Fixed backend-related error with Eren during integration #401
Implemented homepage and navbar components #420, #421
Implemented feed page with post viewing and pagination #443
Implemented post creation and editing functionality #500
Added comment functionality to posts #502
Worked on UI consistency and color palette creation #501
Fixed post schema errors for correct API usage #412
Added search functionality to feed page #512
Fixed disappearing “Hide Comments” button bug #517
Documentation and Management Related Significant Issues
Issue Explanation Issue Link
Took meeting notes and documented results Meeting 2
Researched “Activity Streams 2.0” and documented adaptation plan #336
Revised requirements according to Activity Streams 2.0 section #350
Reviewed and approved WCAG 2.1 AA standard revision #348
Reviewed and approved smart environments standards revision #347
Reviewed and closed resolved issues #434, #447, #448
Reviewed and commented on pending issue #428

Pull Requests

Created by Me

PR Explanation PR Link
Initialized frontend folder structure and development tools #369
Implemented homepage, floating navbar, and carousel UI #419
Added feed page with post creation, edit, comment, like/unlike, and save/unsave functionalities. Included animations, color palette, and consistent UI standards #487
Added search functionality to feed page and fixed UI bugs including disappearing “Hide Comments” button. Updated challenge page visuals #519

Reviewed / Modified / Merged by Me

PR Explanation PR Link
Reviewed Arda’s PR, resolved merge conflicts, and finalized merge. There were challenge card and challenge page ui code conflicts since i was on another branch fixing and updating ui aspect of those. I manually edited them to comply with my changes while accepting Arda's merge. #520

7.2 Serdar Bahar

7.3 ABDÜLKERİM KASAR

Member

Abdülkerim Kasar, Group 5, Mobile (React Native/Expo).

Responsibilities

Group Communicator, Mobile Developer, Mobile Communicator, Documenter.

Main Contributions

Mobile Development

  • Unarchived and reactivated the mobile codebase, restoring DB connections and removing legacy modules: #361, #362, PR #375
  • Updated API integrations to match new backend REST schema for milestone scope: #395, PR #442
  • Implemented UI and functional improvements for platform consistency: #450, #457.
  • Added zoomable image viewer, publish timestamps, and stabilized language switch: #480
  • Reworked bio preview and update flow for proper visibility and sync: #452
  • Enabled async loading for profile posts to improve perceived performance: #481
  • Restored Waste Goals add–edit–delete–log after backend changes: #454, #466
  • Introduced mock “Report” actions and groundwork for profile progress insights: #472
  • Fixed comment edit/delete verification and deletion flows to align with backend params: #452, #462.
  • Restored unsave flow for Saved Posts: #453.
  • Delivered consolidated Milestone-1 mobile work: PR #473.
  • Produced signed APK for demo and milestone handoff: #322, PR #504.
  • Generated authentic mock data for realistic demo population: #505

Project Management & Documentation

  • Created and updated the Communication Plan after team syncs: #310]
  • Initialized and maintained the Meeting Notes page: #309]
  • Organized the 352 wiki sidebar and improved navigation.
  • Led onboarding for newcomers to the mobile branch.
  • Scheduled and organized the first customer meeting as communicator: #359]
  • Revised last year’s requirements and categorized by status and scope changes: #314]
  • Uploaded Milestone-1 Customer Observer notes: #527]
  • Published Mobile × Web joint meeting notes: #458]
  • Contributed to elicitation materials: #377], #383]
  • Closed the mobile preparation issue once dev-ready: #360
  • Participated in Lab 2–4 sessions, summarizing customer meeting outcomes and demo planning.
  • Assigned and distributed mobile issues across the team for balanced workload.

Code-Related Significant Issues

  • #361 Unarchive project and reactivate mobile workspace
  • #362 DB connection review and cleanup
  • #395 Mobile API integration with new endpoints
  • #454 Waste Goals restoration
  • #480 Zoomable image viewer and UI polish
  • #481 Async profile feed loading
  • #472 Mock report actions and stats groundwork
  • #453 Restore unsave flow
  • #488 Custom waste logging button handling
  • #505Mock data generation

Management-Related Significant Issues

  • #309 Meeting Notes page initialization
  • #310 Communication Plan creation
  • #314 Requirements revision and classification
  • #359 Customer meeting organization
  • #458 Cross-team meeting documentation
  • #527 Milestone-1 customer observer notes

Pull Requests

Created by Me

  • PR #375 Reactivate mobile project and remove legacy modules
  • PR #414 Merge mobile developments into develop
  • PR #442 Update API layer for new endpoint schema
  • PR #473 Comprehensive Milestone-1 mobile delivery
  • PR #489 Fix custom waste logging button flow
  • PR #504 Signed APK for demo deployment

Reviewed / Merged by Me

  • PR #427 Review: mobile fixes and cleanups
  • PR #463 Mobile bug fixes and UI improvements
  • PR #469 Post management flow review
  • PR #490 Milestone-1 final reviews Part 1
  • PR #492 Milestone-1 final reviews Part 2
  • PR #503 Code review and merge approval

Non-Issue Tasks

  • Set up emulator configs and ensured smooth runs on both Web and Android VM for demos.
  • Welcomed newcomers to the mobile branch and helped with local environment setup.
  • Assisted Lab 4 demo-scenario planning and next week's presentation flow discussions.
  • Monitored mobile team updates and coordinated scope for Milestone-1 delivery.
  • Assigned mobile tasks to balance workload and tracked progress to develop.
  • Prepared and presented customer meeting summaries from personal notes (Lab 3 follow-up).

This page is just a summary and extraction of the main parts of my contribution. For a detailed log of weekly contributions and time spent, please see my detailed weekly contribution pages.
Week 1
Week 2
Week 3
Week 4
Week 5

7.4 Emre Kılıç

Responsibilities

Mobile Developer, Documenter

I was primarily responsible for the Mobile Implementation and Deployment. I implemented the end-to-end Challenge page, this includes creation, progress visualization, attending/leaving challenges, leaderboard, logging challenge contributions. I also ensured i18n coverage for Turkish and English. I coordinated APK generation, publishing the release.

Besides the main contributions, I also contributed the design part of the project. I documented design criteria article, proposed inclusive design ideas for all and REST API standardization for the backend, reviewed the modernizations implemented by the backend developers. I also found critical bugs in various contexts. I followed and reviewed these bugs to gracefully resolve.

Code-related significant issues

Task name Issue Related PR
Implement Challenge Page for Mobile #406 #469
Delete account button missing #506 #514
Unexpected text in the success box after registration #507 #514
Add tr/en locales to the challenge page buttons #474 #469
Create a pipeline for deployment (CI/CD) #370 #372
Deployment with Docker file is not working for backend #380 #381
mobile/ leaderboard in challenges do not show statistics #455 #484

Non-code-related significant issues

Task name Issue
Publish the release #526
Generate the APK file after the new revisions #525
Cleanup closed branches #371
Research and documentation about RESTful APIs #357
Revise the requirements for “design criteria for smart environments standards” #347
Make a research about design criteria for smart environments #337
Create git development policies #389

PRs I created

Task name PR
fix/resolve mobile #514
fix(mobile): leaderboard show statistics #484
feature: challenge page mobile #469
feature: added CI/CD pipeline for the deployment (draft) #372

PRs I reviewed or merged

Task name PR
Turkish translation consistency #497
Delete account button and its functionalities are added #483
refactor(backend): give the password at body #485
feature: mobile initial additions for i18n standards #427
merge mobile-develop into develop to unify branches and integrate mobile work #414
extract mobile to development branch and remove unnecessary features #375
Dependency problems for deployment #381

7.5 Ali Bartu Konca

Responsibilities

I was generally responsible for the backend related tasks, namely adding functionality and reviewing/testing code. I also worked on security related aspects of the backend such as writing reports and researching. Lastly, I was responsible for the Project Plan, opening issues related to it and setting the correct times for the issues. I also created 2 milestones in addition to the ones given to structure the Project Plan better.

Main Contributions

  • Adding functionality to the backend
  • Reviewing code related to backend development
  • Helping with domain and https related tasks
  • Demo presentation
  • Project Plan Creation, Issue Scheduling for the Project Plan, Opening Milestones.
  • Milestone 1 Documentation

Code-related significant issues

Issues PRs and Commits 
 arrange back-end side for new development of the CMPE451 #342 PR
modify the endpoints to obey "REST API URI Naming Conventions and Standards" #373 PR Commit-1, Commit-2, Commit-3, Commit-4
add jwt token authentication to the application #374 PR
deployment with docker file is not working for backend #380 PR
 implement account deletion functionality #393 PR
 improve the waste goal and waste log logic at the database and backend #413 PR
determine api requests that do not require authentication #423 PR
 triggers of the waste goal and waste log relationship #436 PR
 challenge implementation for backend #439 PR
[Bug] "hide the comments" button disappearing #517 PR

Non Code Related significant issues

Pull Requests

Additional Information

I have also helped Cengiz Bilal Sarı while setting up https and arranging a domain. I planned the Project Plan and created many issues regarding those tasks. I presented the application during the 1st demo. Lastly, I worked on Logging User activities however I haven't made any commits yet.

7.6 Yusuf Onur Öksüz

Responsibilities

Mobile Developer, Documenter, Presenter

I was primarily responsible for the Mobile Implementation, Documentation and Presenter. I implemented the Delete account functionality and its necessary features. I also ensured i18n coverage for Turkish and English. I was a tester for the mobile development PR's. I reviewed most of my teammate's codes and gave feedback through "pr reviews" on existing problems. I was one of the main diagram creators, i handled the UML diagrams with Yüksel Eren Şen. I also was responsible for the demo for the milestone 1 as a main performer alongside with Ali Bartu Konca and I also created the scenario for the demo. Besides the main contributions, I also contributed the design part of the project and task distribution. I proposed inclusive design ideas for all and proposed several solutions to our existing problems/new features, especially in the lab sessions. I was also the responsible team member for helping our new teammates, via teaching them our notations, standarts we have in the team and the documentations; helping them navigating in our repository; teaching them our already existing code, what we did, how we did, and why we followed specific design choices last semester.

Code-related significant issues

Task name Issue Related PR
Remove custom waste logging until backend support #488 #489
leaderboard in challenges do not show statistics #455 #484
Delete account and challenge log entry api integration #459 #469 #483
Version Upgrade #482 for milestone 2

Non-code-related significant issues

Task name Issue
Weekly report template #331
Meeting notes template #328
Creating a scenario for the milestone 1 #425
Updating sequence diagrams #388
mobile app codebase setup and cleanup #360
Revise the requirements for “design criteria for smart environments standards” #347
Make a research about design criteria for smart environments #337
UML Diagrams #316

PRs I created

Task name PR
Delete account button and its functionalities #483

PRs I reviewed or merged

Task name PR
feature: challenge page mobile #469
mobile consistency and other improvements #473
fix(mobile): leaderboard show statistics #484
remove custom waste logging until backend support #489
frontend language switcher and page translation #498

7.7 Cengiz Bilal Sarı

Member

Cengiz Bilal Sarı, Group 5, Backend Team

Responsibilities

Backend Engineer, Devops Engineer, DB Manager, Documenter.

  • I was primarily responsible for the Backend Development, Database Management, DevOps and project documentation. My work focused on ensuring the all features of the milestone 1 (waste goal, waste log, authentication, challenge, login ,register, RestAPI standards, posts,forum, profile ) are working as desired and implementing them. Some part of the implementation comes from the CMPE352 (like login, register, post). I am also responsible for database management and deployment of the application. I worked with the machines for deployment of both code and database.

  • Main contributions: For this milestone, my primary contributions involved end-to-end backend development, deployment and DB management. I architected and implemented core services like JWT authentication, the challenge feature, waste goal and log feature , while also standardizing all API endpoints and resolving numerous bugs. I was fully responsible for the infrastructure, setting up the virtual machine, deploying the application, and securing our domain with Nginx and HTTPS. Additionally, I handled CI/CD tasks by creating GitHub Actions for Slack notifications and contributed to key project documentation.

Issues

Code-Related Significant Issues
Issue Explanation Issue Link
add pr-to-slack github action ( creation of yaml file) #325
add issue-to-slack github action (creation of yaml file) #327
arrange back-end side for new development of the CMPE451 #342
modify the endpoints to obey "REST API URI Naming Conventions and Standards" #373
add jwt token authentication to the application #374
update postman collections of the new endpoints and test each one of them #379
improve the waste goal and waste log logic at the database and backend #413
review the problem of sending request to backend #418
modify the api requests that do not require authentication #423
implement the challenge feature for backend #439
solve the bug about the parameters of the endpoints of profile #449
solve the bug about the parameters of the endpoints of post and comment #462

Deployment Related Significant Issues

Issue Explanation Issue Link
create vm in digital ocean #332
research how to use https for deployment #339
implement nginx and https with a domain, deploy the application with it #486
publish the release #526
review dockerfile of frontend for deployment #467

Database Related Significant Issues

Issue Explanation Issue Link
deploy tables to db #333
write the triggers of the waste goal and waste log relationship #436
review the problem about challenge types at db #493

Documentation and Management Related Significant Issues

Issue Explanation Issue Link/Documentation Link
add description to milestone 1 and 2 #319
add the session structure and rules for documentation and usage of github to communication plan #324
review lab reports update #326
write a report on the ethics and data protection status of the backend #329
revise and write the requirements for "principles of ethics and data protection standards" #346
write elicitation questions for the upcoming customer meeting #377
writing meeting notes for 22.10.2025 #531
write " List and status of all the project deliverables " part of milestone 1 #533
write " Evaluation of tools and processes you have used to manage your team project" part of milestone 1 #534
write " The requirements addressed in this milestone" part of milestone 1 #535
review use case diagram and suggest necessary changes #378
review and update class diagram #382
review the sequence diagram and suggest necessary changes #388

Pull Requests

Created by Me

PR Explanation PR Link
merge backend which is configured in develop to main #343
jwt token imlpementation #376
Dependency problems for deployment #381
merge develop to main for tested features #399 #407 #461 #476 #510 #524
endpoint changes for REST standards #404
improve the endpoints and service functions with new logic of waste goal and log #416
add the triggers for waste goal and waste log #437
addition of the endpoints to non-jwt list #438
backend challenge implementation #441
bug(backend) an issue at the parameters about profile endpoints #450
bug(backend) an issue at the path of endpoints about comme… #463
feature(backend) endpoint for getting waste items for specific waste goal #468
refactor(backend)/give the password at body #485
configuration(frontend/backend): the files are configured for the deployment #490
feature(backend) modify implementation of search #508

Reviewed-Modified/Merged By Me

PR Explanation PR Link
user deletion feature #417
main frontend branch changes #460
cors config at backend and dockerfile of frontend #464
develop to main for configurations and waste goal #465
adjustments for VM deployment #475

7.8 Yüksel Eren Şen

Member

Yüksel Eren Şen, Group 5, Frontend Team

Responsibilities

Frontend Developer, Documenter

  • I was responsible for the general leadership of the frontend team. I have been guiding our new member towards our standards and goals, developing cooperated tasks with backend like authentication system. Contributing to decisions via meetings and developing frontend with other team members, backend and DevOps integrations have been part of my responsibilites.

  • Main Contributions: For this milestone, my key contributions involved initializing the frontend architecture, implementing core pages (main page, profile page, authentication, protected routes), and ensuring backend integration through secure token management. I also improved DevOps integration by preparing Dockerfiles, adjusting project settings for deployment on the VM, and handling API updates. Furthermore, I played an active role in team communication, research, and documentation efforts.

Issues

Code-Related Significant Issues
Issue Explanation Issue Link
Fixed frontend layout bug #410
Fixed backend integration issue on frontend #401
Fixed gitignore configuration bug for the team #402
Created and updated API folder for modular structure #411
Updated API handling according to new backend changes #447
Implemented scroll panel component for main page #435
Added shadcn component library for unified UI design #412
Deployment and Configuration Related Significant Issues
Issue Explanation Issue Link
Created VM for deployment #332
Deployed backend on VM #334
Created another VM for database #333
Created whitelist in deployed DB for team members #364
Deployed full application in VM #315
Documentation and Management Related Significant Issues
Issue Explanation Issue Link
Created Slack workspace for team communication #311
Changed wiki sidebar to include team meetings #351
Documented internalization (i18n) process #349
Conducted research about frontend testing tools #353
Wrote and submitted lab report #431
Reviewed and updated use-case diagram according to new requirements #378

Pull Requests

Created by Me

PR Explanation PR Link
Initialized frontend project with routing, layout, API setup, and CSS library #409
Planned and implemented frontend folder structure #365, #368, #369
Implemented profile page and protected routes #430
Implemented main page with scroll panel #432
Added Dockerfile and updated docker-compose for frontend deployment #464
Implemented delete and edit account functionality #460
Fixed deployment configuration for VM #461

Reviewed / Modified / Merged by Me

PR Explanation PR Link
Reviewed frontend structure and implementations by Arslan -
Reviewed and explained internalization system to teammates -
Led and documented frontend team meetings Meeting Notes

7.9 Osman Yusuf Tosun

7.10 Arda Yalçındağ

Member

Arda Yalçındağ, Group 5, Frontend Team

Responsibilities

I am part of the frontend team and I am responsible for the development of the frontend side of the project. Additionally, I am responsible for attending weekly and non-routine meetings, being part of the planning of the project, making necessary research and writing reports and documentations.

Main Contributions

For milestone 1, my main contribution was for the development of the frontend. In particular, I have coded the components related to challenges such as challenge card, create challenge, and leaderboard in addition to challenges page itself. Additionally, i18n implementation, existing page translations, and implementing language switch button were among my contributions. Since I am a newcomer to the team and a complete beginner to frontend development, a significant amount of my time was spent on learning frontend development and tools we use such as React, JavaScript, HTML etc. In addition to my contributions in the frontend team, I contributed significantly on designing and planning process of the project by being proactive in the discussions and meetings. I researched WCAG 2.1 AA, written a report about it and added new requirements to better conform to these guidelines. I also contributed to important documentations such as milestone 1 report and meeting notes.

Code-Related Significant Issues

  • #411: Reviewed Yüksel Eren Şen's frontend implementation for api requests and new api folder in frontend
  • #422: Researched the implementation of i18n for the frontend and implemented it.
  • #429: Reviewed Yüksel Eren Şen's PR on implementation authorization protection, and merged it.
  • #445: Implemented challenge card, create challenge, and challenge page.
  • #495: Finished translation of remaining frontend pages and added a language switch button.
  • #516: Implemented leaderboards for challenge cards.

Non-Code-Related Significant Issues

  • #313: Reviewed the tasks of lab 1 and ensured they are done properly.
  • #320: Reviewed the milestone 3 description.
  • #326: Created a lab report template according to the new format, created the Lab 1 Page, and revised Wiki sidebar accordingly.
  • #329: Reviewed the report about the ethics and data protection principles.
  • #330: Researched WCAG 2.1 AA standards and written a report about how we can improve our project complying with the standards.
  • #331: Created Weekly Report Template and organized wiki accordingly.
  • #348: Added new requirements complying with the WCAG 2.1 AA to our project requirements page.
  • #377: Added elicitation questions for the upcoming customer meeting.
  • #405: Written meeting notes for meeting 6.
  • #527: Taken notes during customer meeting and documented the notes.
  • #529: Written first section of the milestone report.

Pull Requests

Created

  • #426: Implenented the i18n for English-Turkish translation and translated the login page.
  • #477: Implemented challenge cards, challenge page, and started create challenge modal.
  • #491: Finished implementing challenge page, create challenge, and enhanced challenge cards.
  • #498: Implemented language switcher button and translated remaining pages and components.
  • #520: Implemented leaderboard feature in challenge cards.

Reviewed and Merged

  • #430: Reviewed Yüksel Eren Şen's initial profile page and protection implementation and merged it (no conflict).
  • #433: Reviewed Yüksel Eren Şen's scroll-panel implementation and merged it (no conflict).

Additional Information

  • I studied frontend development from scratch by learning frameworks, tools, and languages such as React, JavaScript, HTML, CSS etc.
  • Taken notes during the meeting 6 and documented the meeting notes.
  • Attended mobile-frontend common meeting for consistency in UI/UX.
  • Attended customer meeting.
  • Attended customer presentation for milestone 1 and taken notes during the presentations.
  • Attended all of the weekly meetings and actively contributed to the discussion topics and taken responsibility.
  • I was proactive during the discussion on our communication channels such as Slack, supported any team member who needed help, and expressed my opinions about the all processes of the project.