Library / Systems Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 02:22:15 UTC · snapshot created 2026-10-03 03:38:22 UTC · last check 2026-10-03 04:45:20 UTC

SYSE.22:4 - Solution

Maintain a finite selected problem portfolio and a separately identified set of System-family options. Connect them through decision-bearing correspondence claims, compare them under the current use and evidence, and end the pass with one replayable choice or probe result. Observations from either side can then reopen the other without discarding archives and lineage. A supported current comparison can remain usable while its carrier ages; neither retention nor an unchanged receiving use requires a fresh trial or a separate renewal certificate.

SYSE.22:4.1 - Pattern-Use Unfolding

The Method uses eight recurring moves. They organize production of the account; problem-development, System-development, research, realization, integration, operation, and decision Work can overlap.

  1. Decision boundary. The Agent identifies the actual System or intended-system designator selected as the project system-of-interest, or the System family and its membership and effectivity rules; current use, environment, affected Systems, configuration, horizon, resources, DecisionSubject, and authority complete the boundary.
  2. Situation and problem records. The Agent separates the world-side occurrence or condition from assertions, observations, and evidence about it. Each selected ProblemCard states detection, problematic relation or unresolved claim, improvement check, constraints, affected Systems, evidence, receiving use, and the premises that make that evidence applicable. Include an expiry only where an actual qualification, right, resource or promised-use window ends; a review date alone does not invalidate the claim.
  3. Archive and portfolio. Alternative formulations and weak signals remain in the archive under retention rules. The selected portfolio is finite and states why each record receives current attention or resources and what removes or reopens it.
  4. System-family options. Actual Systems and configurations, candidate architectures, family membership and effectivity rules, and possible-future specifications are identified separately. Each option states what is realizable now and which builder or platform change it needs.
  5. Problem–option correspondences. Every relied-on pair states the changed admission, comparison coordinate, protected characteristic, affected-System consequence, evidence need, or next action. A pair with no supported decision-bearing difference remains an unresolved mismatch.
  6. Plural comparison. Archives, Fronts, and the decision OptionSet retain their own membership rules. The Agent compares several result and resource coordinates while retaining protected losses, uncertainty, and non-dominated alternatives. Do not force those coordinates into one scalar objective.
  7. Choice or probe. The current OptionSet is fixed. The deciding Agent performs comparison-and-choice Work, applies C.11.CRC when a finite configuration-relative contribution comparison is needed, and applies C.11 to produce a decision result: a choice, tie-set, rejection, named probe, or reroute. The Agent selects a probe only when its expected contribution warrants its full burden: participant and engineering effort, delay, foregone alternatives and displaced protective Work as well as direct expenditure. The performer, resources, access, authority and useful observation window must be available. An affordable discriminator is not by itself a worthwhile probe; a useful qualified result may stand without new observations.
  8. Later Work and selective reopening. Assigned Agents plan, authorize, perform, and interpret later Work through the applicable relations. New observations reopen only the problem records, correspondences, options, Fronts, configurations, or decisions that relied on the changed claim.

SYSE.22:4.2 - Record the Result

The joint problem–System-family account records these eight items:

Result positionRequired content
decision boundaryProject System or System family, membership and effectivity basis, current use, environment, affected Systems, configuration, horizon, resources, chooser, authority, and receiving decision.
situation and claim basisWorld-side occurrence, condition, or unresolved possibility; separate assertions, observations, evidence, source, interval, and uncertainty.
problem archive and portfolioRetained and selected problem records, their different membership rules, lineage, resources, applicable premises, stops and reopen conditions; actual expiry where a qualification, right, resource or promised-use window ends.
System-family optionsActual Systems and configurations, family identity, architecture, variant and effectivity rules, possible-future specifications, realizability, and builder dependencies.
plural-search resultsExploration archive and each Front with its candidate set, retention or admission rule, comparator, characteristics, date, and currentness.
correspondencesEvery decision-bearing problem–option claim, its source and uncertainty, plus unresolved mismatches.
choice or probeFixed OptionSet, shared comparison basis, choice rule, probe budget and value when relevant, result permitted by the choice rule, reason, and overturn conditions.
continuationRetained alternatives, planned and performed later Work when it occurs, receiving results, and selective reopen relations.

SYSE.22:4.3 - What Changes in Practice

The project stops treating backlog items and design variants as two fixed columns. It can say which world-side change reopened which problem–option pair, why a candidate remains in an archive but not the current decision, and why the choice rule permits a choice, rejection, probe, or reroute as the next result.