-
Notifications
You must be signed in to change notification settings - Fork 0
Requirements
1. Functional Requirements
1.1 User Requirements
1.1.1 User Types
There shall be two types of users: Mentees and Mentors.
1.1.1.1 Mentees
1.1.1.1.1 Mentees shall be able to create and edit their profile.
1.1.1.1.2 Mentees shall be able to specify their goals, interests, and background information.
1.1.1.1.3 Mentees shall be able to view matched mentor profiles.
1.1.1.1.4 Mentees shall be able to send mentorship requests to mentors.
1.1.1.1.5 Mentees shall be able to communicate with mentors through the in-app messaging system.
1.1.1.1.6 Mentees shall be able to submit assignments or tasks assigned by their mentor.
1.1.1.1.7 Mentees shall be able to view feedback given by their mentor.
1.1.1.1.8 Mentees shall be able to view scheduled meetings.
1.1.1.2 Mentors
1.1.1.2.1 Mentors shall be able to create and edit their profile.
1.1.1.2.2 Mentors shall be able to define mentoring goals and preferred mentee criteria.
1.1.1.2.3 Mentors shall be able to define their availability schedule.
1.1.1.2.4 Mentors shall be notified when a candidate mentee match is found.
1.1.1.2.5 Mentors shall be able to view candidate mentee profiles (background, goals, interests).
1.1.1.2.6 Mentors shall be able to accept or reject mentorship requests.
1.1.1.2.7 Mentors shall be able to initiate and maintain communication with mentees through the in-app messaging system.
1.1.1.2.8 Mentors shall be able to schedule recurring weekly meetings.
1.1.1.2.9 Mentors shall be able to assign weekly tasks to mentees.
1.1.1.2.10 Mentors shall be able to review submitted work and provide feedback.
1.1.1.2.11 Mentors shall be able to manage multiple mentees simultaneously.
1.1.2 Matching System
1.1.2.1 The system shall match mentors and mentees based on interests, goals, availability, and background.
1.1.2.2 The system shall notify mentors when a potential mentee match is found.
1.1.2.3 The system shall notify mentees when a mentor accepts their request.
1.1.2.4 Mentors shall not be matched beyond their maximum mentee capacity.
1.1.3 Messaging & Communication
1.1.3.1 The platform shall provide an in-app messaging system.
1.1.3.2 Users shall receive notifications for new messages.
1.1.3.3 Users shall be able to maintain message history.
1.1.3.4 Users shall be able to attach documents or links in messages.
1.1.4 Scheduling
1.1.4.1 Mentors shall be able to define weekly availability.
1.1.4.2 Mentors shall be able to create recurring weekly meetings.
1.1.4.3 The system shall send meeting confirmation notifications.
1.1.4.4 The system shall send meeting reminders before scheduled meetings.
1.1.4.5 Mentees shall be able to request rescheduling of meetings.
1.1.5 Task & Progress Management
1.1.5.1 Mentors shall be able to assign tasks with deadlines.
1.1.5.2 Mentees shall be able to upload task submissions.
1.1.5.3 Mentors shall be able to provide structured feedback.
1.1.5.4 The system shall maintain task history for each mentorship relationship.
1.1.5.5 The system shall track mentorship progress over time.
1.2 System Requirements
1.2.1 Notifications
1.2.1.1 The system shall send push notifications for new matches.
1.2.1.2 The system shall send push notifications for new messages.
1.2.1.3 The system shall send notifications for meeting reminders.
1.2.1.4 Notifications shall only be sent to relevant users.
1.2.2 Profiles
1.2.2.1 User profiles shall include background, goals, skills, and interests.
1.2.2.2 Profiles shall display mentoring preferences.
1.2.2.3 Users shall be able to control profile visibility.
1.2.3 Sign-Up & Authentication
1.2.3.1 Users shall register with real name, email, and password.
1.2.3.2 Email addresses shall be unique.
1.2.3.3 Passwords shall meet defined security criteria.
1.2.3.4 Email addresses shall be verified before account activation.
2. Non-Functional Requirements
2.1 Availability
2.1.1 The system shall be available 24/7 except during maintenance periods.
2.1.2 The system shall support web and mobile access.
2.2 Security
2.2.1 User passwords shall be stored as hashed in the database.
2.2.2 Communication between users shall be encrypted.
2.2.3 The system shall comply with GDPR and KVKK regulations.
2.3 Performance
2.3.1 The system shall deliver notifications within 5 seconds of triggering events.
2.3.2 The system shall support concurrent mentor-mentee sessions without performance degradation.
Team Members
- Lab 1 Report (12/02/2026)
- Lab 2 Report (19/02/2026)
- Lab 3 Report (26/02/2026)
- Lab 4 Report (05/03/2026)
- Lab 5 Report (12/03/2026)
- Lab 6 Report (26/03/2026)
- Lab 7 Report (02/04/2026)
- Lab 8 Report (18/04/2026)
- Lab 9 Report (30/04/2026)
- Lab 10 Report (07/05/2026)
- Weekly Meeting Notes Template
- Lab Meeting 1 (12.02.2026)
- Weekly Meeting 1 (16.02.2026)
- Weekly Meeting 2 (24.02.2026)
- Weekly Meeting 3 (04.03.2026)
- Weekly Meeting 4 (11.03.2026)
- Weekly Meeting 5 (23.03.2026)
- Weekly Meeting 6 (29.03.2026)
- Weekly Meeting 7 (11.04.2026)
- Weekly Meeting 8 (28.04.2026)
- Weekly Meeting 9 (10.05.2026)
- Use Case Diagram 1 (New Mentor User for Mobile Scenario)
- Use Case Diagram 2 (Mentor-Mentee Matching Scenario)
- Use Case Diagram 3 (New Mentee User Scenario)
- Final Use Case Diagram
- MVP Use Case Diagram
- All Sequence Diagrams
- Sequence Diagram: Mentee Matching
- Sequence Diagram: Mentor Matching
- Sequence Diagram: Mentorship Management
- Sequence Diagram: Registration
- Sequence Diagram: Cancelling Mentorship Relationship and Auto Ban
- Sequence Diagram: Login-Logout
- Sequence Diagram: Reporting-User
- Sequence Diagram: Mentor Profile Management
- MVP Sequence Diagrams
- Test Plan & Coverage (MVP)
- Acceptance Testing Strategy
- Acceptance Tests
- Test Data Strategy
- Web Frontend Test Report
- Amin Abu-Hilga
- Övgü Su Afşar
- Muhammet Sami Çakmak
- Beratcan Doğan
- İbrahim Kayan
- Burak Ögüt
- Mehmet Bora Sarıoğlu
- Future Work (reference, not a deliverable)