Atlas SystemsSchedule / Resources / Budget
Capstone I timeline, lightweight resources, 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 — Crowdsourced POIs (MVP) | Submit-review-approve flow using lightweight JSON store; 10 seed POIs curated. |
| 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 | 4–6 sprints: MVP → Beta → Field Pilot → Release Candidate → Final handoff (spec & ops guide). |
Capstone II details will be posted as a sprint plan at the start of CS486 (targets: MVP, Beta, Pilot, RC, Final Demo & Handover).
Schedule — Capstone II (Spring)
Placeholder: Capstone II centers on implementation, testing, and delivery. A detailed sprint plan (2–3 weeks/sprint) will be posted at the start of CS486, including milestones for MVP, client feedback loops, integration testing, and final demo.
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)
We’ll keep the website lean; detailed team inventory lives in our internal docs.
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.