fpf.tools
Library / Systems Engineering Principles Framework
Jump to passage
In this reading
Source · lines 1850–1867

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:40:20 UTC

SYSE.22:1 - Problem Frame

Engineering problems and System concepts develop together. For example, an architecture can expose a manufacturing constraint; a prototype can change what users consider possible; an operating failure can reveal an affected System absent from the original scope; a new component can make a previously unaffordable option feasible.

Five recurring confusions make that mutual development hard to manage:

  1. a problem situation is confused with its ProblemCard;
  2. a problem archive is confused with the finite portfolio receiving attention now;
  3. an actual System is confused with a possible-future specification;
  4. an exploration archive or Front is confused with the current decision’s OptionSet; and
  5. an experiment proposal is confused with authorized and performed experiment Work.

Keeping these distinctions lets the project preserve lineage while changing only the claims affected by a new observation.