Elicitation Questions Neighborhood Accessibility Mapper

1. User Personas & Target Audience

• Q1: Beyond wheelchair users, should the system specifically cater to other groups such as parents with strollers, elderly individuals with walkers, or visually impaired users? If so, how do the priority features differ for each group?
• Q2: Will there be different user roles in the system? For example, do we need a separate interface for "Expert Contributors" (e.g., NGO members) versus "Casual Users"?
• Q3: Should businesses (e.g., cafes, shops) have a special account type to update their own accessibility status, or will all data be strictly crowdsourced from the public?

2. Core Functionality & Routing Logic

• Q4: Regarding "accessibility features," how granular should the data be? Is a binary "Accessible/Not Accessible" tag sufficient, or does the system need detailed attributes like "Ramp width," "Door opening mechanism," or "Slope percentage"?
• Q5: How should the routing algorithm handle "unknown" or "missing" data? Should the system suggest a route that might be accessible but isn't verified, or only strictly verified paths?
• Q6: Is "Real-time Navigation" (turn-by-turn voice guidance) a must-have for the MVP (Minimum Viable Product), or is "Pre-trip Planning" (showing the map and route overview) the primary goal?
• Q7: How should the system handle temporary obstacles (e.g., construction work, broken elevators, parked cars on sidewalks)? Do these need a "time-to-live" (expiration duration)?

3. Data Contribution & Crowdsourcing Mechanics

• Q8: To ensure data reliability, should we implement a "Trust Score" or "Reputation System" for contributors? (e.g., A new user's edit requires approval, while a trusted user's edit goes live immediately).
• Q9: What is the primary incentive for users to contribute data? Should we include gamification elements (badges, leaderboards, points) to encourage participation?
• Q10: When a user reports an issue (e.g., "Steep Slope"), should they be required to upload a photo as proof, or is text description sufficient?

4. Usability & User Experience (UX)

• Q11: Considering the target audience might have motor impairments, are there specific interface constraints? (e.g., High contrast mode, large buttons, voice command support).
• Q12: Given that internet connection might be unstable outdoors, is Offline Mode (caching maps and routes) a critical requirement? If yes, should users be able to download specific neighborhoods?

5. Privacy & Safety (Non-Functional Requirements)

• Q13: Regarding image uploads, is the system required to automatically blur faces and license plates to comply with privacy regulations (KVKK/GDPR), or is manual moderation preferred?
• Q14: Should the system allow users to create "Private Routes" (e.g., Home to Work) that are not shared with the public database?

6. Project Scope & Scalability

• Q15: For the MVP (Minimum Viable Product), what is the geographical scope? Are we targeting a specific campus (e.g., Boğaziçi University), a single neighborhood (e.g., Hisarüstü), or the entire city?
• Q16: Should the system handle multi-floor mapping (e.g., inside shopping malls or metro stations), or is it strictly limited to outdoor street-level accessibility?

7. User Interaction & Reporting Mechanics

• Q17: Regarding the reporting interface: Should users manually drop a pin on the map to mark an obstacle, or should the system automatically capture their GPS coordinates when they take a photo?
• Q18: Will the map interface allow users to "draw" accessible routes (e.g., highlighting a safe path on a sidewalk), or is the data limited to specific point-based markers (POIs)?

8. Stakeholders & Municipal Integration

• Q19: Since accessibility issues often require fixing by local authorities, should the system generate automated reports or "Heat Maps" that can be sent to municipalities (e.g., "This street has 5 reported broken ramps")?
• Q20: Is there a plan to integrate with existing city data (e.g., Istanbul Metropolitan Municipality's open data portal) to import existing bus stop or sidewalk data?