IDEF0 A0 — fulfil customer order
An IDEF0 A0 function decomposition with all four ICOM arrow types. Inputs, controls, mechanisms and outputs each pin to a fixed box edge, so the model is correct by construction per FIPS PUB 183.
For the business / systems analyst
What this shows
An IDEF0 A0 diagram — the top-level functional decomposition of an order-fulfilment system — showing all four ICOM arrow roles. Reading the box edges by convention: Inputs enter on the left (the customer order, inventory), Controls govern from the top (credit policy, picking rules, carrier contract), Mechanisms supply resources from the bottom (the order system, warehouse staff, carrier), and Outputs leave on the right (delivered order, invoice). The box-to-box flows (A1 -> A2 "Validated order") chain the three activities.
The differentiator is that the model is correct by construction, not just drawn. Because the arrow keyword is the box edge it attaches to, the engine enforces ICOM placement — you cannot accidentally draw a control as an input. It resolves every box reference, assigns decomposition numbers (A0 → A1..A3), codes the boundary arrows down each edge (I1/C1/O1/M1…), and applies the FIPS 3-to-6-box guideline. A flow that tried to enter a box via its .output edge would be rejected, because an output leaves a box — the standard is enforced, not suggested.