Engineering deliverables
Purpose
Section titled “Purpose”This section groups industry-standard engineering artifacts for the leekimerp Frappe application: prioritized work, release rules, test strategy, non-functional targets, threat modeling, and Architecture Decision Records (ADRs). It complements Handover deliverables (commercial mapping), Documentation gap closure plan (phased execution and gap framing — docs-only scope), and Documentation upgrade roadmap (docs-site improvements).
Use this hub when you need one place to answer: What is our test policy? Where are SLOs recorded? How do we handle breaking API changes?
Deliverables map
Section titled “Deliverables map”| Topic | Page | Role |
|---|---|---|
| Prioritized roadmap | Below + linked tracks | P0/P1/P2 for governance artifacts |
| Release & compatibility | Release & compatibility | Versioning, breaking changes, ERPNext alignment |
| Test strategy | Test strategy | Test pyramid, coverage expectations, evidence |
| NFR & SLO | NFR & SLO | Availability, recovery, latency — template + ownership |
| Threat model | Threat model | Trust boundaries, STRIDE, guest APIs & webhooks |
| ADR practice | ADR practice | Numbering, splits, supersession — links to ADR index |
| ADR content | Architecture decisions | Decision log and template |
Prioritized roadmap (P0 → P2)
Section titled “Prioritized roadmap (P0 → P2)”Roadmap items are governance and policy work, not feature backlogs. Feature and docs work continues on Known issues & roadmap and Documentation upgrade roadmap.
| Priority | Theme | Outcome |
|---|---|---|
| P0 | Release & API safety | Teams can cite Release & compatibility for semver intent, migrations, and integrator notice. |
| P0 | Test evidence | Test strategy + Test evidence & CI define what “green” means for handover. |
| P1 | NFR / SLO clarity | NFR & SLO filled for your environment (values may live in an internal wiki; this site holds structure). |
| P1 | Threat model | Threat model reviewed with security owner; Security checklist stays the control checklist. |
| P1 | ADR hygiene | New decisions follow ADR practice; index stays current. |
| P2 | Diagrams & depth | Optional trust-boundary diagrams in Mermaid; align with Diagram roadmap. |
Related tracks (by concern)
Section titled “Related tracks (by concern)”| Concern | Where to look |
|---|---|
| End-to-end business paths | Critical paths (E2E) |
| Single architectural index (Arc42-style) | Architecture index (Arc42-style) |
| Docs site CI, DocType regen, inventory CSV | Test evidence & CI, Documentation inventory |
| Domain narrative depth (D1/D2/D3) | Domain documentation strategy |
| Operations procedures | Deployment & operations, Operational runbook |
| Handover sign-off | Handover completion checklist |
Related
Section titled “Related”- Documentation conventions — sidebar groups aligned with
astro.config.mjs - Documentation gap closure plan — phased rollout of governance artifacts; does not modify application code
- Handover deliverables
- Start guide — documentation map includes this hub
- Diagram roadmap — suggested diagram types per policy page
- Reference vs implementation