-
Notifications
You must be signed in to change notification settings - Fork 0
Lab 2 Scenario – Municipality Resolution
The user is a municipal accessibility officer working in the urban infrastructure department of a local government.
The user is responsible for resolving reported accessibility problems in public spaces and documenting completed improvements in the system.
The user wants to:
- Review accessibility issues reported by citizens.
- Fix reported problems in public infrastructure.
- Upload official post-repair photos as proof of resolution.
- Publish verified updates so citizens can review and confirm the accuracy of the fix.
- The municipality user is registered and logged into the system.
- Accessibility issues have been reported by citizens and are visible on the map.
- The municipality user has authority to mark issues as resolved.
- Citizens have access to the system to review and rate resolved issues.
- The municipality user logs into the Neighborhood Accessibility Mapper system.
- The system displays a map containing accessibility issues reported by citizens.
- The municipality user selects a reported issue from the map.
- The system displays issue details, including location, description, and citizen-submitted photos.
- The municipality schedules and completes the required repair in the real world.
- After the repair is completed, the municipality user takes an official photo showing the fixed and accessible infrastructure.
- The municipality user uploads the post-repair photo to the system.
- The municipality user marks the issue status as “Resolved – Awaiting Validation.”
- The system publishes the updated issue and notifies citizens.
- Citizens review the municipality-uploaded photo and rate the accuracy of the fix.
- The system calculates a validation score based on citizen ratings.
- If the validation score meets the required threshold, the system marks the issue as “Confirmed Resolved.”
1.5.1: The system shall provide a dashboard for municipal officers to view all citizen-reported issues on a map.
1.3.3: The system shall allow users to upload a photo as visual evidence of the reported obstacle (to be viewed by the officer).
1.5.2: The system shall allow municipal officers to change the status of an issue to “Resolved – Awaiting Validation.”
1.5.3: The system shall require the officer to upload an official post-repair photo as proof before updating the status.
1.5.4: The system shall allow citizens to rate/validate the accuracy of the municipality’s fix based on the uploaded photo.
1.5.5: The system shall mark the issue as “Confirmed Resolved” and remove the warning marker only after the validation score meets a defined threshold.
- Map view showing issue status (Reported / Awaiting Validation / Confirmed).
- Issue detail page with before-and-after photos.
- Citizen rating interface (accuracy / confirmation score).
- 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