Computational Thinking in Engineering

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

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

Every engineering calculation follows this workflow:

1. Input

Inputs are the raw materials of the calculation, consisting of:

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

2. Process / Calculation (What happens in the middle)

This is where mathematical transformation occurs.

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

3. Output

The raw results produced by the process.

• Numeric Answer vs. Engineering Answer: A calculator displaying 45.1234 is just a number. An engineering output must include the number, correct units, appropriate significant figures, and physical direction if it is a vector.

4. Validation (The Engineering Filter)

Computers stop at the output, but engineers do not.

• Plausibility Check: Does the result make physical sense?
• Sensitivity: If I change an input by 10%, does the output change slightly, or does it blow up? 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.