-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Welcome to the official documentation for the Neighborhood Accessibility Mapper. This wiki serves as the central hub for our project overview, technical specifications, and team coordination.
Neighborhood Accessibility Mapper is a crowdsourced platform dedicated to documenting the accessibility features of local businesses, transit stops, and sidewalks. By leveraging community-driven data and advanced geospatial routing algorithms, we aim to make urban spaces navigable for everyone, regardless of their mobility needs.
- Our Vision: To create a world where urban environments are universally accessible, documented in real-time, and easily navigable for individuals with mobility challenges.
- Our Goal: To provide a reliable, offline-capable, and community-moderated mapping tool that seamlessly integrates accessibility constraints into everyday route planning.
- The Bridging Effect: We act as the vital link connecting people with mobility challenges to accessible spaces, while simultaneously connecting businesses willing to improve their infrastructure with the citizens who need those accommodations.
We are a team of Computer Engineering students developing the Neighborhood Accessibility Mapper. Starting with a focus on our local environment, including the Boğaziçi University campuses, our goal is to apply our software engineering skills to a real-world problem: urban accessibility.
By building a platform that allows users to map physical obstacles—like broken ramps or narrow sidewalks—we hope to make daily navigation easier and more inclusive for individuals with mobility challenges.
To help you navigate our documentation, below is the structure of this Wiki. You can also use the Sidebar on the right for quick access to these pages.
- Home (You are here)
- Software Requirements Specification (SRS)
- Elicitation Questions
- Scenarios: Disabled User Route Planning | Municipality Resolution | Volunteer Accessibility Reporting
- Use Case Diagrams: Disabled User | Municipality | Volunteer | Final Diagram
- Class Diagram
- Sequence Diagrams
- Implementation Plan
- Test Plan & Coverage
-
Lab Report 1: Requirements Elicitation & Repository Setup
-
Lab Report 2: SRS Through Scenarios & Mock-ups
-
Lab Report 3: From Scenarios to Use Case Diagrams
-
Lab Report 4: Class Diagrams & Use-case Diagrams
-
Lab Report 5: Git Workflow, Stub Application, and Planning
-
Lab Report 6: Planning for Implementations & Tests
-
Lab Report 7: Finalizing Plan for MVP Milestone Demo
-
Meeting Note: 2026-02-18: Weekly Meeting #1
-
Meeting Note: 2026-02-18: Customer Meeting #1
-
Meeting Note: 2026-02-25: Customer Meeting #2
-
Meeting Note: 2026-02-25: Weekly Meeting #2
-
Meeting Note: 2026-03-04: Weekly Meeting #3
-
Meeting Note: 2026-03-11: Weekly Meeting #4
-
Meeting Note: 2026-04-01: Weekly Meeting #5
For code contributions, please refer to our main repository.
- Elicitation Questions
- Requirements
- Implementation Plan
- Test Plan & Coverage
- MVP Demo Plan
- Communication Plan
- Responsibility Assignment Matrix
- Use of Standards
- Project Retrospective
- Final Demo Plan
- Final Milestone Deliverables
- Report 1 - Requirements Elicitation & Repository Setup
- Report 2 - SRS Through Scenarios & Mock-ups
- Report 3 - From Scenarios to Use Case Diagrams
- Report 4 - Class Diagrams & Use-case Diagrams
- Report 5 - Git Workflow, Stub Application, and Planning
- Report 6 - Planning for Implementations & Tests
- Report 7 - Finalizing Plan for MVP Milestone Demo
- Report 8 - Standards & Plan Revision
- Report 9 - Requirements Review & Acceptance Testing
- Report 10 - Finalizing Plan for Final Milestone Demo
- 2026-02-18: Weekly Meeting #1
- 2026-02-18: Customer Meeting #1
- 2026-02-25: Stakeholder Meeting
- 2026-02-25: Weekly Meeting #2
- 2026-03-04: Weekly Meeting #3
- 2026-03-11: Weekly Meeting #4
- 2026-04-01: Weekly Meeting #5
- 2026-04-15: Weekly Meeting #6
- 2026-04-22: Weekly Meeting #7
- 2026-04-29: Weekly Meeting #8
- 2026-05-06: Weekly Meeting #9