57 lines
2.7 KiB
Markdown
57 lines
2.7 KiB
Markdown
# SecureCam ideal project Gantt chart
|
|
|
|
```mermaid
|
|
gantt
|
|
title SecureCam Project Timeline
|
|
dateFormat YYYY-MM-DD
|
|
axisFormat %b
|
|
excludes weekends
|
|
|
|
section Initiation and Planning
|
|
Project scoping and proposal :done, a1, 2025-10-15, 10d
|
|
Requirements gathering and research :done, a2, after a1, 12d
|
|
Early architecture and feasibility :done, a3, after a1, 15d
|
|
|
|
section Initial Prototype
|
|
Core prototype implementation :done, b1, 2025-10-28, 18d
|
|
Basic camera-to-client workflow :done, b2, after b1, 10d
|
|
|
|
section Scope Change and Refactor
|
|
Major scope change identified :milestone, m1, 2025-11-12, 0d
|
|
Requirements redefinition :crit, c1, 2025-11-13, 8d
|
|
Architecture redesign :crit, c2, after c1, 10d
|
|
Backend refactor and model cleanup :crit, c3, after c2, 18d
|
|
Web and mobile flow realignment :crit, c4, after c2, 14d
|
|
|
|
section Platform Rebuild
|
|
Authentication and device model :d1, 2025-12-09, 12d
|
|
Realtime communication layer :d2, after d1, 14d
|
|
Stream control and recording pipeline :d3, after d2, 16d
|
|
Storage integration and signed media URLs :d4, after d1, 12d
|
|
Motion events and activity feed :d5, after d2, 10d
|
|
|
|
section Client Applications
|
|
Web app feature completion :e1, 2026-01-20, 18d
|
|
Mobile app implementation :e2, 2026-01-27, 24d
|
|
Push notifications and user feedback loop :e3, after d5, 12d
|
|
|
|
section Quality and Evaluation
|
|
Integration testing and bug fixing :f1, 2026-02-24, 18d
|
|
Performance tuning and resilience review :f2, after f1, 10d
|
|
Final validation and demo preparation :f3, after f2, 8d
|
|
|
|
section Dissertation and Delivery
|
|
Documentation and architecture diagrams :g1, 2026-03-17, 12d
|
|
Report writing and iteration :g2, 2026-03-10, 26d
|
|
Final edits and submission prep :g3, after g2, 8d
|
|
Project complete :milestone, m2, 2026-04-17, 0d
|
|
```
|
|
|
|
## Notes
|
|
|
|
- Start date assumed: `2025-10-15` to reflect a mid-October project start.
|
|
- Final deadline set to: `2026-04-17`.
|
|
- The chart assumes a major scope shift in mid-November that forced the team to revisit requirements and refactor the platform.
|
|
- The refactor is treated as a real disruption rather than a minor iteration, so the later phases are shown as a rebuild on firmer architecture rather than a straight continuation of the original prototype.
|
|
- This is an "idealised but realistic" plan for documentation purposes, not a claim that every task happened exactly in this order.
|