Schedule / Resources / Budget
Capstone I roadmap, Spring 2026 major events, and current budget stance.
Schedule — Outcome-Focused Roadmap
| Window | Milestone | External-Facing Outcome |
|---|---|---|
| Sept | M1 — Project Framing | One-page brief: problem, target users, success criteria, initial risks. |
| Late Sept | M2 — Tech Feasibility Spike | Working tech spike proving GPS + web map SDK integration (desktop & mobile browser). |
| Early Oct | M3 — Prototype A (Navigation) | Clickable prototype with live location, target pins, and route hints. Short demo video (≤90s). |
| Mid Oct | M4 — Prototype B (Accessible UI) | Refined UI components (contrast-safe, keyboard-navigable). 5-min usability smoke test notes. |
| Late Oct | M5 — Nationwide POIs (Overpass/Wikidata) | Automated ingestion pipeline syncing POIs from Overpass + Wikidata APIs and caching them for launch. |
| Early Nov | M6 — Alpha Demo | Alpha build walkthrough with 1 guided mission; feedback from at least 2 non-team users. |
| Mid Nov | M7 — Beta Readiness | Stabilized features, instrumented basic metrics (time-to-target); issue backlog triaged. |
| Late Nov | M8 — Public Tech Demo | Live demo + short video posted; risks & next-semester plan published on website. |
| Dec | M9 — Site V1 | Employer-ready website: overview, video, screenshots, tech notes, and contact. |
| Spring (Capstone II) | M10 — Build & Delivery | Alpha Demo I/II, Design Reviews 2/3, UGRADS poster/oral milestones, Acceptance Demo, Final Website, and final product handoff. |
Schedule — Capstone II (Spring 2026)
| Weeks | Major Event | Key Deliverables / Due Items |
|---|---|---|
| Weeks 1-2 | Capstone Kickoff | Alpha Demo I flight plan, and Communication Strategy Memo. |
| Weeks 3-4 | Software Design Prep | Design Document milestone and initial prep for the Design Review 2 presentation. |
| Week 5 | Alpha Demonstration I | Alpha Demo I plus Alpha Demo II flight-plan prep. |
| Week 6 | Design Review 2 Presentation | Design Review 2 Presentation and Peer Eval #1. UGRADS registration work begins and the team website continues evolving. |
| Weeks 7-8 | Testing & UGRADS Registration | Design Document Final, Software Testing Plan work, and UGRADS Registration Form. |
| Week 9 | Alpha Demonstration II | Alpha Demo II mentor deadline, Acceptance Demo flight plan, and Software Testing Plan. |
| Week 10 | Design Review 3 Presentation | Design Review 3 Presentation and Peer Eval #2. UGRADS Poster production starts. |
| Weeks 11-13 | UGRADS Poster & Oral Prep | UGRADS Poster, UGRADS Oral Presentation Dry Run |
| Week 14 | UGRADS Conference | UGRADS Oral Presentation schedule and Peer Eval #3. Final Report and Product Delivery ramp up. |
| Weeks 15-16 | Acceptance Demo & Final Delivery | Acceptance Demo, Final Website and Course Evaluation |
Heads up: After the Acceptance Demo, the client must sign the user manual and product check-off sheet before final product delivery closes out.
Resources (Minimal)
- Team: 4 developers (John Zeledon, Mitchell Morris, Hunter Beach, Tristen Calder)
- Tooling: GitHub (private repo, PR reviews), JetBrains IDEs, VS Code as needed
- Hosting: NAU Capstone archival server (static site)
- Devices: Personal computers as well as Android and iOS mobile phones for on-device testing
- Maps/API: Web map SDK (vendor TBD following cost/limits review)
Budget
No budget at this time. We plan to use free academic tiers and open-source tooling. Any future costs (e.g., commercial map SDK usage above free tier) will be reviewed with our sponsor before adoption.
Atlas Systems