Home
- 🛠️ Project #5 : ZERO WASTE CHALLENGE
- 👥 Team members
- 📅 Weekly Meetings
- 📚 Resources&Diagrams
- 🔧 Contribution Guidelines
The Zero Waste Challenge is an engaging, gamified platform created to empower individuals and communities in their journey toward sustainability. Through personalized goal-setting, friendly competitions, and collaborative efforts, users can actively track, reduce, and manage their waste. The platform fosters a sense of shared responsibility and motivation, making sustainable living both achievable and rewarding.
To effectively support our goals, the development of the Zero Waste Challenge platform requires a well-defined set of software requirements. In the Software Requirement Specification section, we outline the functional,non-functional and other requirements.
To better understand the needs of users and stakeholders, a set of targeted questions was developed. The questions in the Elicitation Questions part guide the requirement-gathering process and help ensure that the platform aligns with user expectations and goals.
The Definition of Users / Audience section outlines the primary user groups targeted by the Zero Waste Challenge platform. By understanding their goals, behaviors, and needs, the system can be tailored to deliver a more effective and engaging experience for each type of user.
- Eren Akçin
- Mustafa Ocak
- Samed Kızılhan
- Başar Temiz
- Umut Şendağ
- Ceyda İrem Irwin
- Bora Toprak Temir
- Berkay Ak's CV
- Ömer Faruk Çelik's CV
- Cenk Yilmaz
- Mert Kirman
Our team holds weekly meetings to discuss progress, address challenges, and plan next steps. These meetings ensure that everyone is aligned on project goals and responsibilities.
- The meeting agenda and summaries of previous meetings are recorded and stored here.
- The agenda is prepared by Başar Temiz, who is responsible for preparing and documenting meeting agendas before the meeting so we can all prepare beforehand.
- Project Updates: Each team member gives a brief update on their tasks.
- Issue Tracking & Discussion: Open issues, blockers, and challenges are reviewed.
- Task Assignment: New tasks and deadlines are set for the upcoming week.
- Code Reviews & Decisions: Major changes and PRs are discussed before merging.
- Planning Next Steps: The team aligns on upcoming milestones and sprint goals.
- Check the meeting agenda in advance and add discussion points if needed.
- Review your progress on assigned tasks and be ready to provide updates.
- Raise concerns or blockers during the meeting so the team can address them.
- Take notes if you are responsible for a specific update or presentation.
- Attendance is expected from all team members unless otherwise excused.
- Keep discussions concise and relevant to the agenda items.
- If you cannot attend, please inform the team in advance and provide updates asynchronously.
This section contains useful materials to help team members improve their skills and collaborate effectively. Currently, you can find a Git learning guide here:
More resources will be added in the future as resource issues are opened and addressed. Stay tuned for updates! 🚀
The Project Class Diagram section provides an overview of the system’s structure using a class diagram. It visualizes the main components, their attributes, methods, and relationships, offering a clear view of the platform’s object-oriented design.
In the Project Use Case Diagram part, the use case diagram illustrates how users interact with the system. It defines the primary actors and outlines key functionalities based on user goals and system behavior.
The Project Sequence Diagram section illustrates the system’s dynamic behavior over time using a sequence diagram. It visualizes the interactions between components as a series of time-ordered messages, providing a clear understanding of how specific scenarios unfold step by step.
Welcome to the bounswe2025group10 project! To ensure smooth collaboration, please follow our contribution guidelines.
- Follow the issue tracking system: Before starting any work, check existing issues or create a new one if necessary. Refer to our Issue Conventions.
- Use meaningful commit messages: Clearly describe changes in a concise yet informative way.
- Follow the branch naming convention: Use a descriptive name like feature/login-page or fix/api-endpoint.
- Pull requests (PRs) should be reviewed: Always request a review before merging to the main branch.
1. Fork the repository and clone it to your local machine.
2. Create a new branch for your feature or bug fix.
3. Implement changes and ensure your code follows project guidelines.
4. Test your changes before committing.
5. Push your branch and open a pull request.
6. Request a review and make necessary changes if suggested.
✅ Keep PRs small and focused. ✅ Write clear documentation and comments. ✅ Use consistent coding style as per project conventions. ✅ Discuss major changes before implementation.
By following these guidelines, we ensure a well-organized and maintainable project. Thanks for contributing! 🚀