Computational Thinking in Engineering

Computational thinking is not about writing computer code; it is a structured way of thinking about a problem so that it can be solved systematically, whether by a human or a machine.

The Standard Model: Input $\rightarrow$ Process $\rightarrow$ Output

Every engineering calculation follows this flow:

1. INPUT (What goes in)

Inputs are the raw materials of calculation. They include:

• Given data: Measurements, forces, dimensions.
• Assumptions: Simplifying rules (e.g., "assume friction is zero").
• Constraints: Limits (e.g., "maximum temperature is 100°C"). Crucial Step: All inputs must have explicitly defined units before moving to the next step.

2. PROCESS / CALCULATION (What happens in the middle)

This is where the mathematical transformation occurs.

• Selecting the correct governing equations.
• Applying algebraic substitution.
• Running the calculation (by hand, spreadsheet, or software).

3. OUTPUT (What comes out)

The raw result produced by the process.

• A numerical answer is NOT an engineering answer. A calculator outputting 45.1234 is just a number. An engineering output includes the number, the correct unit, the appropriate significant figures, and a physical direction if it is a vector.

4. VALIDATION (The Engineering Filter)

A computer stops at the Output. An engineer does not.

• Plausibility Check: Does the output make physical sense? (The Sanity Check).
• Sensitivity: If I change the input by 10%, does the output change by a little, or does it explode? Understanding this prevents fragile designs.
• Reproducibility: Can another engineer take your Inputs, follow your Process, and get the exact same Output? If not, your work is invalid.