- Documentation
- /
- Erpam
- /
- 01 — Quick Reference
01 — Quick Reference
Menu map
| Group | Models |
|---|---|
| Project & Scope | Entity · ERPProject · LegacySystem · BusinessProcess · Requirement |
| Design & Data Migration | SolutionDesign · DataObject · MigrationRule · MigrationBatch · Reconciliation · Interface |
| Testing & Defects | TestCycle · TestCase · Defect · RemediationAction |
| Evidence & Readiness | EvidenceRequirement · EvidenceSubmission · ReadinessArea · GoLiveDecision |
| Closure | ClosureRequest · ClosureApproval · StatusHistory |
Every model (22) — one line each
| Model | It records | Key foreign keys |
|---|---|---|
| Entity | An audited organisation | — |
| ERPProject | The replacement programme | Entity |
| LegacySystem | A system being replaced | ERPProject |
| BusinessProcess | An in-scope process | ERPProject |
| Requirement | A scoped requirement | ERPProject, BusinessProcess |
| SolutionDesign | A design meeting a requirement | ERPProject, Requirement |
| DataObject | A data set to migrate | ERPProject |
| MigrationRule | A transformation/validation rule | ERPProject, DataObject |
| MigrationBatch | An ETL run with control totals | ERPProject, DataObject |
| Reconciliation | A source-vs-target metric check | MigrationBatch |
| Interface | An integration to/from the ERP | ERPProject |
| TestCycle | A testing cycle | ERPProject |
| TestCase | A test with expected/actual | ERPProject, TestCycle, Requirement, Interface, MigrationBatch |
| Defect | A defect (maybe go-live-blocking) | ERPProject, TestCase, Requirement, Interface, MigrationBatch |
| RemediationAction | A fix for a defect | ERPProject, Defect |
| EvidenceRequirement | Required evidence | ERPProject, Requirement, Defect |
| EvidenceSubmission | Evidence provided | ERPProject, EvidenceRequirement, (self: supersedes) |
| ReadinessArea | A go-live readiness area | ERPProject |
| GoLiveDecision | The authorised go-live decision | ERPProject |
| ClosureRequest | A request to close | ERPProject |
| ClosureApproval | The closure outcome | ClosureRequest |
| StatusHistory | A project state transition | ERPProject |
Status vocabularies
- Project status: PLANNED → INITIATED → IN_PROGRESS → AT_RISK / BLOCKED → READY_FOR_GO_LIVE → LIVE → CLOSED · plus CANCELLED
- Requirement type / status: BUSINESS·FUNCTIONAL·NON_FUNCTIONAL·CONTROL·REPORTING·DATA·INTEGRATION·SECURITY / DRAFT·APPROVED·IMPLEMENTED·PARTIAL·DEFERRED·REJECTED
- Design status: DRAFT · UNDER_REVIEW · APPROVED · REJECTED · SUPERSEDED
- Migration status: PLANNED · EXTRACTED · TRANSFORMED · LOADED · RECONCILING · RECONCILED · FAILED · ACCEPTED
- Interface status: PLANNED · BUILDING · TESTING · READY · FAILED · LIVE · RETIRED
- Test-case status: NOT_RUN · IN_PROGRESS · PASSED · PARTIAL · FAILED · BLOCKED · NOT_APPLICABLE
- Defect status: OPEN · TRIAGED · IN_PROGRESS · READY_FOR_RETEST · RETESTING · RESOLVED · CLOSED · DEFERRED · ACCEPTED
- Readiness status: NOT_ASSESSED · NOT_READY · PARTIALLY_READY · READY · CONDITIONALLY_READY
- Go-live outcome: APPROVED · REJECTED · DEFERRED · CONDITIONAL
- Priority / criticality / severity: LOW · MEDIUM · HIGH · CRITICAL
Demo data set (45 rows)
Entity 1 · ERPProject 1 · LegacySystem 2 · BusinessProcess 2 · Requirement 3 · SolutionDesign 1 · DataObject 2 · MigrationRule 2 · MigrationBatch 2 · Reconciliation 2 · Interface 2 · TestCycle 2 · TestCase 3 · Defect 2 · RemediationAction 2 · EvidenceRequirement 2 · EvidenceSubmission 2 · ReadinessArea 4 · GoLiveDecision 1 · ClosureRequest 1 · ClosureApproval 1 · StatusHistory 5.
Reseed from empty: python apps/erpam/scripts/seed_data.py (skips if data already present).
Local run
python server/run.py erpam # http://localhost:5074