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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 05:45:20 UTC

SYSE.1:1 - Problem frame

Use this pattern when a project is already discussed through a familiar name—for example, a product, solution, tool, provider, organization, component, desired effect, or broad programme—but no defensible current decision yet identifies which System the project is intended to change or bring about. The choice matters because it changes later questions about use, boundary, architecture, realization Work, evidence, and specialist decisions.

The first result is a project-system choice account: claim-bearing project decision content that names the selected actual System or intended referent, the current reason for the choice, and what may reopen it.

First useful move: name one candidate actual System or intended referent, state the present use or change reason for choosing it, and write the main unresolved assumption. This small project-system choice account is enough to ask the next use-and-system concept question. Expand it only when disagreement, a valuable alternative, or a later answer can change the choice.

If the choice is missed, participants can work competently on different projects while using the same project name. A supplier optimizes a component, an integrator changes an operating assembly, and a client expects an outside effect, yet each assumes that the familiar noun names the same project system-of-interest.

The payoff is a shared and revisable project focus. The choice can stabilize current coordination while evidence from use, architecture, realization, or operation remains able to reopen it.

Use this pattern only when project coordination needs a System designation. If the decision already concerns another recognized subject—for example Work, a Method, a capability, a state, a material portion, a description, a collection, a structure, or a transformation—keep that subject under the pattern that defines or constrains its claim. If the issue is only whether a named entity is a System, use A.1.SCR. If the System has already been selected and the live question is how it participates in use, continue with SYSE.2.

At the first consequential use of source wording such as system of interest, target system, our system, product, or solution, ask one question: is the project choosing which actual System or intended referent it will change? If yes, state the candidate and its current use or change reason. Project system-of-interest names the designation made for this project; it is not another System kind.