Track project · 17

Model an Enterprise Procurement Workflow

Transfer the course architecture into a business workflow with approvals, auditability, background work, and tenant boundaries.

Build plan

Work through it one observable step at a time

01
Write the procurement lifecycle as explicit states/transitions before designing tables.
02
List invariants such as received quantity not exceeding ordered quantity.
03
Model requisition, approval, purchase order, goods receipt, and invoice relationships.
04
Define approval authority and record every decision as audit evidence.
05
Use effective dates where business truth is time-dependent.
06
Design inventory movement as an append-oriented business event instead of silently overwriting stock history.
07
Use a database transaction plus outbox row for one reliable integration event.
08
Process the outbox with a retryable background worker and make the handler idempotent.
09
Add tenant keys and authorization rules to every query path.
10
Create a reporting read model without moving core invariants into reporting code.
11
Explain where you deliberately did not introduce microservices or extra infrastructure yet.

Evidence

Do not rely on “it seems to work”

Evidence to collect

A clean Git diff or file-tree changeCommands used and their exit/resultBrowser, HTTP, database, test, container, or CI evidence that proves the behaviorOne deliberate failure, the evidence you used, and the root-cause fixA short explanation of why the final responsibility lives in the chosen layer

Project exit ticket

Close the project only when these are true

Completion

I can demonstrate every deliverable.I can reproduce one key part without the walkthrough.I can explain one trade-off I deliberately chose.I can show one failure that my tests, constraints, or runbook now protects against.