OOAMS

OOAMS Public Release Traceability

This checklist defines the public GitHub release scope and confirms that the reviewer-facing deliverables remain traceable, reproducible, and honest about limitations. Private learning and preparation materials are intentionally excluded from the public repository.

Public deliverable coverage

Area	Public evidence	Status
Requirements	01-Requirements/	Present
Database	02-Database/	Present and regenerated
Synthetic data	03-Data/	Present and reproducible
SQL analytics	04-SQL/	Present and executable
Python pipeline	05-Python-Pipeline/	Present and executable
Power BI design	06-PowerBI/OOAMS-PBI-001.pdf	Present; PBIX manual
Agile planning	07-Agile/OOAMS-APM-001.pdf	Present as planning artefact
Testing and UAT	08-Testing/ and tests/	Present
Portfolio website	10-Portfolio-Case-Study/index.html	Present; live at https://ayushmaangangulywork-boop.github.io/OOAMS/10-Portfolio-Case-Study/
Release quality	This file and root README.md	Present

Consistency checks

• All required professional deliverables are organized under 01-Requirements through 08-Testing, plus 10-Portfolio-Case-Study.
• The root README provides a reviewer path: website → release traceability → reproducibility commands.
• No absolute /home/claude or /mnt/user-data paths remain in executable scripts.
• The generator and pipeline use portable pathlib defaults and CLI overrides.
• The fixed synthetic snapshot is 2025-09-12; the database stores it in ooams_metadata.
• SQL views and pipeline deadline calculations use the same snapshot basis.
• Baseline counts are consistent: 394 orders, 1,655 status-history rows, 611 tasks, 120 issues, and 305 comments.
• The pipeline contract is 14 Excel sheets; automated tests assert their names and KPI headers.
• The package labels data as synthetic and does not claim deployment or real business results.
• No PBIX, live Jira board, production environment, or real stakeholder sign-off is represented as included.
• All nine tracked professional DOCX deliverables have same-basename PDF mirrors; reviewer-facing documentation links to PDFs while DOCX sources remain available for editing.

Validation evidence

python -m py_compile 03-Data/OOAMS-Sample-Data-Generator.py 05-Python-Pipeline/OOAMS-Pipeline-001.py
python 03-Data/OOAMS-Sample-Data-Generator.py
python 05-Python-Pipeline/OOAMS-Pipeline-001.py
python -m pytest -q

Additional checks execute the full SQL query pack, SQLite integrity and foreign-key checks, both scripts from their own directories, the static website’s relative links, and byte-level reproducibility of two generated databases.

Remaining manual work

1. Build the Power BI report in Power BI Desktop from 05-Python-Pipeline/OOAMS-Analytics-Output.xlsx and 06-PowerBI/OOAMS-PBI-001.pdf.
2. Visually inspect filters, relationships, KPI labels, accessibility, and page layout.
3. Replace or extend the live case-study page only if the public presentation scope changes.

This site is open source. Improve this page.