Lab 2 Report

Wiki Pages for Scenarios & Mock-ups

• Scenario 1: Disabled User Route Planning
• Scenario 2: Volunteer Accessibility Reporting
• Scenario 3: Municipality Issue Resolution

---

Requirements

Link to Requirements Wiki Page: Requirements

---

Individual Contributions

(Note: Please provide links to the related issues/commits for each contribution as per Moodle directives.)

Ali Akkaya

• Contribution 1: Designed and created the whole mock-up for both mine and other team member's pages. #14
• Contribution 2: A scenario for a wheelchair user planning a static route from North Campus to Duatepe Park. #14
• Contribution 3: Designed the flow summary explaining the 4 steps. #25
• Contribution 4: Implemented a requirements table linking 4 requirements to the screens. #25
• Contribution 4: Updated the README.md file accordingly to the current lab.

Bora Aydemir

• Created and structured the official Lab 2 Software Requirements Specification (SRS) report on the Wiki. #20
• Designed the system workflow and planned the user interactions for the Volunteer Accessibility Reporting scenario. #15
• Consolidated evaluation criteria across all scenarios and enumerated the final system requirements on the shared Wiki page. #19
• Organized the lab session, delegated scenario drafting tasks to sub-teams, and managed the overarching Epic issue. #13

Ömer Belemir Delier

• Took primary responsibility for writing and documenting the Citizen Contributor scenario for Lab 2. This included defining a realistic user profile, clarifying user goals, specifying pre-conditions, and constructing a clear step-by-step interaction flow aligned with the project brief.#15
• Actively contributed to shaping the overall Lab 2 report by helping structure the document.#26

Arif Evren

• Helped conceptualizing and implementing the Disabled User Route Planning* scenario, clearly defining the user flow and expected system responses. #14
• Helped designing mock-up for the scenario.#14
• helped verifying requirement coverage by systematically mapping each defined requirement to corresponding actions within the three user scenarios. #14, #15, #16

Ekin Kılıç

• [Took primary responsibility for designing and documenting the Municipality Issue Resolution scenario for Lab 2. This contribution involved defining the municipality user role, outlining system preconditions, and detailing the step by step process through which reported accessibility issues are reviewed, prioritized, and resolved by local authorities. ] (#Issue_Link)
• [Supported the Lab 2 documentation by reviewing the Municipality Resolution scenario for consistency with the Software Requirements Specification (SRS).] (#Issue_Link)

Ulaş Sertan Kemeç

• I took primary responsibility for the design and documentation of the "Municipality Resolution" scenario, focusing on the integration of municipal officers into the system. I contributed to defining the user goals, pre-conditions, and the main flow, specifically establishing the functional criteria (1.5.1 - 1.5.5) for official proof uploads and citizen-based validation scores. #16

• I organized the team's workload for Lab 2 by creating and assigning relevant GitHub Issues to team members. This ensured that the project documentation and individual tasks were clearly defined and tracked according to the project requirements. #21

Baran Önder

• Contribution 1: Designed and created the Disabled User Route Planning scenario. #14
• Contribution 2: Created my personal wiki page. #3
• Contribution 3: Defined and enumerated all functional requirements using a hierarchical ID system ($1.x.x$) to ensure clarity, precision, and formal structure. #19
• Contribution 4: Validated functional coverage by mapping each enumerated requirement to specific actions within the three defined user scenarios. #14, #15, #16