Final Milestone: Deliverables Report

[mehmetborasarioglu]

📝 Description

The Final Milestone Deliverables for CMPE 354 Spring 2026 require a single wiki page named Final Milestone Deliverables containing the executive summary, requirements progress, API documentation with sample scenarios, UI/UX artefacts, utilised standards deep-dive, testing reports, demo reflections, individual contributions, and the production release information. The release artefact (web + mobile) is also due, with a final-milestone Git tag pointing to a commit on main. This issue is the umbrella tracker; each section has a dedicated sub-issue.

🎯 Goal

• Publish the Final Milestone Deliverables wiki page in full, populated with concrete artefact links.
• Cut the final-milestone release tag pointing to a commit on main, attach the mobile .apk, and surface the live deployment URL.
• Ensure every team member's individual contribution subsection is filled in (alphabetical by surname, AI prompts logged, top‑3 issues per category, individually attributable tests with commit IDs).

📦 Deliverables

Wiki page: Final Milestone Deliverables

• 📄 Single wiki page covering all sections from the official template.
• All references must point to artefacts inside the repo or the wiki — no external links (supplementary links permitted but not as substitutes).

Sub-issues (one per section)

• Final Milestone Report — §1–2: Meeting Notes & Project Documentation links #413 — §1–2: Meeting Notes link + Project Documentation links
• Final Milestone Report — §3: Executive Summary #414 — §3: Executive Summary (6 sub-points)
• Final Milestone Report — §4.1: Team Contribution Summary table #415 — §4.1: Team Contribution Summary (per-member table with PR/Issue links)
• Final Milestone Report — §4.2: Status of Requirements #416 — §4.2: Status of Requirements (Completed / In Progress / Not Started)
• Final Milestone Report — §4.3: API Endpoints + 4 Sample Scenarios #417 — §4.3: API Endpoints — live Swagger link + 4 sample scenarios (≥3 new functionality, 1 search-related)
• Final Milestone Report — §4.4: User Interface / User Experience #418 — §4.4: User Interface / User Experience — code links + screenshots of new/modified UIs
• Final Milestone Report — §4.5: Utilised Standards (Compliance Summary + Deep Dive) #419 — §4.5: Utilised Standards — Compliance Summary + per-standard Deep Dive (Evidence + Reasoning) with PR/code citations
• Final Milestone Report — §4.6: Testing & QA reports (HTML+XML × 3 layers) #420 — §4.6: Testing & Quality Assurance — HTML+XML reports for backend/web/mobile, new test evidence (Integration / E2E / UI), Impact Analysis
• Final Milestone Report — §4.7: Demo Reflections & Notes #421 — §4.7: Demo Reflections & Notes (two wiki pages — raw notes + reflections)
• Final Milestone Report — §5: Individual Contributions (per-member) #422 — §5: Individual Contributions (per-member subsection, alphabetical by surname; AI Prompts wiki page per member)
• Final Milestone Report — §6: Final Software Release & Setup #423 — §6: Final Software Release & Setup (final-milestone tag, live URL, README upgrade, docker-compose, mobile APK)

Hard deadlines

• Software release: 12.05.2026, 22:00
• All other deliverables (wiki page + linked artefacts): 16.05.2026, 22:00

✅ Acceptance Criteria

• Wiki page Final Milestone Deliverables exists and conforms to the official template (sections 1–6 with all sub-sections).
• final-milestone Git tag points to a commit on main (default branch).
• Release 1.0.0 published as a production release (not pre-release), with release notes that include the public live web app URL.
• Mobile .apk attached as a release asset.
• Every sub-issue above is closed.
• Every team member has filled in their Individual Contributions subsection (7 members, alphabetical by surname).
• Every team member has linked an AI Prompts wiki page in their subsection.
• HTML and XML test reports linked for all three layers (backend / web / mobile) and demonstrate all tests passing including regressions from prior milestones.
• At least two specific bugs/edge cases documented under "Bug Detection" in §4.6.
• No deprecated MVP-era endpoints surfaced in the API documentation (or clearly marked as deprecated).
• README walks a stranger through deploying the full project end-to-end (web + mobile) on a clean machine.

📌 Notes

• The official template (provided by the instructor) titles the wiki page Final Milestone Report of CMPE 354 Spring 2026 for the page header but the URL/page name must be Final Milestone Deliverables per the spec. Use the spec's name as the wiki slug.
• Top 3 issues per category in §5 is a hard rule — exceeding it is a grade penalty.
• README setup instructions should be tested in a clean environment (new VM or a teammate's machine) before submission — ease of setup is a graded component.
• Tag string: final-milestone (kebab-case, as shown in the template), not Final milestone.