Skip to content
Queensferry

Module 17

Multi-objective design and Pareto decisions

What to do when the objectives compete — and why the tool must present the trade-off rather than announce a winner.

What this module covers

  • Test whether one design dominates another, and say what the definition requires
  • Build a Pareto front and read what it does and does not tell you
  • Explain why a weighted sum cannot reach a design in a concave dip
  • Use crowding and the knee as prompts for discussion, not as decisions
  • Show that changing the axes changes the front
  • Write a decision record that survives being read six months later

Lessons

  1. One comparison, applied everywhere — and what it leaves for the engineer to do.

    Start lesson →
  2. The demonstration that a single score is not merely a simplification — it makes some good designs unreachable.

    Start lesson →
  3. Knee points, crowding, changing the axes — and the decision record that outlives the decision.

    Start lesson →

Module checkpoint

Check what you have taken in

3 questions

  1. Question 1

    Why can a weighted sum never select a design that sits in a concave dip of the Pareto front?

  2. Question 2

    Five designs are assessed. One violates a hard constraint, two are dominated, and the rest are on the front. How many designs are on the front?

  3. Question 3

    Two schemes: A at 447 tCO₂e and 465 mm deep, B at 666 tCO₂e and 374 mm deep, both minimised. By what percentage is B's carbon higher than A's?