Module 21
The computational engineer in practice
Sixteen steps from a brief to a recommendation, carried through on a real project — and the judgement that no step covers.
What this module covers
- Carry a project from a brief to a recommendation through a stated sequence
- Choose the analysis, the elements and the solver from the question rather than from habit
- Predict before analysing, and hold the prediction against the result
- Assemble a verification plan proportionate to the consequence
- Assess whether AI has a legitimate role on a given task
- Write a recommendation somebody can disagree with
Lessons
- 21.1
The sequence
Sixteen steps, and why the order is the point rather than the list.
Start lesson → One brief, sixteen steps, and the decisions at each — including two that changed the answer.
Start lesson →What none of the sixteen steps covers, and what this course has deliberately not taught.
Start lesson →
Module checkpoint
Check what you have taken in
3 questions
Question 1
A project team builds a detailed three-dimensional model in week one, then decides what question it should answer. What is the most likely consequence?
Question 2
A scheme comparison shows the lowest-carbon option at 447 tCO₂e and the client's original preference at 782. What percentage saving does the recommendation offer?
Question 3
Of sixteen project steps, eight are completed before any model is built and one more — the verification plan — before any result is read. What fraction of the sequence is complete before the first result is looked at? Give the percentage.