How we build software
From approved requirements to working, reviewed code
Our pipeline turns a structured requirements package into a signed-off architecture, a test-first plan, implemented code, and a three-vendor code review. Each step reads and writes defined files, every design element traces back to a requirement, and a person makes the calls that need judgment.
One example, all the way through
Every file on this page is shown for the same worked example, so you can follow it from requirements to code.
Worked example
Expense Report Processing
Replace Acme's Oracle Forms, email, and shared-drive expense workflow with a single web application that covers creation, approval, finance review, and reimbursement recording. The business target is submission-to-reimbursement in under 3 business days for reports that need no correction; today it takes 2-3 weeks.
13 requirements, 38 acceptance criteria, 10 business rules, 8 data entities.
Reading the page
An AI model does the work; its output is checked by code.
Deterministic code, no AI.
The pipeline stops and a person decides.
Runs only when work is sent back.
Click any file to see the example. Each file is labeled with how it was produced.
The flow
Work moves forward through seven phases. Architecture approval and code review can each send work back for another round; the steps involved are marked where each loop starts.
Phase 0: Requirements elicitation
Before this pipeline starts, our elicitation process works with you to produce the structured requirements package: requirements, acceptance criteria, business rules and data entities. That package is the input to step C1.0. Elicitation is covered in a separate guide, which follows the same worked example.