Follow requirements, tests and service operation through a small software workflow.
Free · No sign-in required3 lessonsWorked examples & practiceBeginner
0 of 3 lessons checked · Progress is saved in this browser.
01 / SYSTEM VIEWRequirement
02 / SYSTEM VIEWImplementation and tests
03 / SYSTEM VIEWOperation
This map connects the course ideas; it is not a detailed engineering schematic.
LESSON 1 / 3 · FREE
Inputs, outputs and contracts
Your goal: Define observable behavior before implementation.
Understand the idea
A useful requirement names valid inputs, expected outputs and failure behavior. Split the problem into small functions with explicit contracts. A program returning one expected result is not enough: empty, invalid and boundary inputs can reveal hidden assumptions.
Worked example
A function converting Celsius to Kelvin uses K = °C + 273.15. For 20 °C it returns 293.15 K. The function should also define how it handles nonnumeric input.
Try it yourself
Convert 25 °C to Kelvin using the supplied relation.
Your goal: Distinguish a test pass from proof of every behavior.
Understand the idea
Tests exercise specified cases and assertions. Select normal, edge and failure cases that challenge requirements. A regression test captures behavior that must remain true after changes. Test count alone says little about quality if all tests repeat the same easy path.
Worked example
A fictional suite runs 25 independent checks and 2 fail. Passing fraction is 23/25 = 92 percent, but either failure may block release if it affects an essential contract.
Try it yourself
Of 40 checks, 4 fail. Calculate passing percentage.
Your goal: Separate throughput estimates from response-time guarantees.
Understand the idea
A service processes work using finite resources. Throughput is completed work per time, while latency is delay per request. Simple capacity estimates assume the stated concurrency and service time; queues, shared dependencies and workload variation can invalidate a naive prediction.
Worked example
A strictly serial worker taking 0.2 seconds per job can ideally complete 5 jobs/s with no overhead. This is a simplified upper bound, not a production benchmark.
Try it yourself
A strictly serial worker takes 0.25 seconds per job. Find ideal jobs per second.
Explain each worked example in your own words, check the units and identify one assumption that could change the result. Then use the linked labs or roadmap to apply the ideas to a broader task.
Practice progress is a study aid, not a professional qualification or proof of field competence.
Continue in Software Engineering & Cloud
Apply these foundations in an available course, lab or roadmap. The linked resource’s access rules still apply.
These original lessons use simplified models and explicitly supplied practice values. Calculations teach concepts; they do not select real equipment, establish code compliance or authorize field work. Follow the linked references and advanced resources for deeper study.
Updated · Study progress stays in this browser. There is no certificate or paid gate for these lessons.