Courses / Programming and software engineering / Build, test and operate a small data tool / Implement and test a fictional order-processing tool Build and defend your work Implement and test a fictional order-processing tool Write a small program that joins customer IDs to orders, calculates a contract-defined price and reports unmatched inputs. Add independent tests and a local retry simulation that never double-applies the same operation. Work only with invented records.
Choose an audience, investigate alternatives, copy evidence from your experiments, and produce an artifact. You can open this project at any time. Reports, numerical transfer checks and human review are separate outcomes.
Your project workspace Choose the kind of work you want to produce School investigation College investigation Workplace application Build the calculation and ID join in the bounded editor. Explain every loop and include a missing-ID case plus a boundary test.
1. Collect and compare evidence Required experiment sources:
Include every source above and at least one pair with different inputs from the same experiment. Explain confounding changes yourself; the presence check does not judge your interpretation.
Open an experiment and change an input or capture a trial to make evidence available here.
2. Write and revise your report Inputs, outputs and invariants Specify units, allowed quantities, key uniqueness and behavior for missing or unmatched data.
Runnable implementation and example Paste or describe where your saved runnable code lives, explain the core loop/function, and show a fresh example output.
Independent tests and repaired failure List expected answers calculated before running. Include positive, zero, negative or missing cases and the defect each exposes.
Retry state and receipts Show a lost-response case, a persistent failure case, the attempt ceiling and how duplicate effects are prevented.
Limitations and review request Identify what the local prototype does not test, including persistence or concurrency. State which evidence a reviewer should inspect before operational use.
Your artifact: code, analysis, prototype or decision brief This field stores up to 12,000 characters of inert text. Code runs only through the explicit bounded editor in the relevant lessons; project attachments never execute.
Load a text artifact Review your work against the rubric Actual learner-authored runnable code is supplied for implementation claims; model selectors alone are insufficient. The join uses entity identity and explicitly reports missing matches. Expected outputs come from a stated contract, not merely from repeating implementation expressions. Retry logic respects a finite attempt budget and separates calls, effects and confirmations. No real service effects, security boundary or production readiness is implied by the local simulation. 11 evidence requirements remain Capture evidence from build a price tool. Capture evidence from join records by identity. Capture evidence from test input partitions. Capture evidence from retries and idempotency. Include two different input configurations from the same experiment to compare. Write your inputs, outputs and invariants. Write your runnable implementation and example. Write your independent tests and repaired failure. Write your retry state and receipts. Write your limitations and review request. Add your project artifact: code, analysis, prototype or decision brief. Record my report Download report and evidence Editing the report or evidence returns it to draft. Recording verifies field presence and input comparisons, not correctness of your reasoning or code.
3. Check transfer to unfamiliar cases These authored cases use different numbers or conditions from the lesson practice. They are public local checks, not secure certification. Each case permits three submissions. Opening, first responses and attempt counts survive imports; no reset creates fresh evidence.
Case program-cost-independent Open case program-cost-independent Case program-search-independent Open case program-search-independent Case program-retry-independent Open case program-retry-independent
Return to the course · My Work and backups
