Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-16 21:18:08 UTC · snapshot created 2026-11-16 21:19:40 UTC · last check 2026-11-17 19:15:10 UTC

Part I - Project Focus, Environment, Consequences, and Problem/System-Family Development

SYSE.1 - Choose and Reopen the Project System-of-Interest

Status: Stable

SYSE.1:1 - Problem frame

Use this pattern when participants use a familiar project name but cannot say which system’s intended use gives their joint work its purpose. A product, tool, provider, organization, component or desired effect can occupy the discussion while referring to different subjects. The choice matters to use, architecture, realization, evidence and resource decisions.

The first useful result is a project-system choice account: the actual System or intended referent selected as the system-of-interest (SoI), its intended use, the grounds for the choice and what would reopen it. When the immediate engineering subject differs, identify that subject and its bounded result alongside the product it serves.

Recover the intended use and any assumption that could change the choice. A.1.STM explains why receiving use and encompassing functioning ground construction and provision decisions. A contributor can use a provisional answer for the next concept question. Before joint work relies on it, compare the participants’ referents and contribution connections through §4.4.1. Reuse an adequate existing account.

A manufacturer may need to improve its planning organization while a vendor supplies a software product. Naming both projects does not settle their SoIs. The manufacturer’s product remains the common reference for work on its creator; the vendor’s independently supplied software can be its own SoI. Both the organizational work and the software supply can have finite results and acceptance conditions.

Use this pattern when a System designation is needed for the current coordination. Keep another recognized subject—such as Work, a Method, capability, state, material portion, description or research question—under its direct pattern when that answers the decision. Use A.1.SCR for unresolved System recognition. A System already identified for engineering can proceed to SYSE.2 without first being renamed the SoI.

At a consequential use of system of interest, our system, product, solution or the source phrase target system, ask which system’s useful functioning grounds the cooperation and which subject the local work changes. SoI is a relative project role; system-in-hand names the immediate System being worked on. Explain what “our” refers to and who is responsible for the local result. Several named products or classes of future use may jointly ground a shared creator’s development. Their differences and competing demands remain visible.

SYSE.1:2 - Problem

Project names are chosen early, often before outside use, engineering boundaries, and realization constraints are understood. The first plausible referent then becomes an unstated premise in later decisions. A purchased tool can displace the product it serves; an organization can become the proposed SoI merely because the current project changes it; or a desired state can be forced into a System because the project is organized around achieving it.

The opposite error is also common: a useful tool, software product, or component is categorically excluded even when its own product project legitimately selects it. Compare referents for the current project and keep the choice revisable as understanding of the problem and solution changes together.

SYSE.1:3 - Forces

ForceTension
Coordination and revisionContributors need shared product grounds now, while new evidence may change them.
Outside use and technical discoveryOutside use justifies the choice, while architecture and realization discoveries can revise the use and boundary.
Actual and intended SystemsBrownfield work can concern an existing System, while new development may only have an intended referent in decision or plan content.
Products and local projectsSeveral projects can serve the same product; independently supplied products can have different SoIs while their contributions and commitments remain connected.
Candidate breadth and decision costA single familiar candidate hides alternatives, while an exhaustive catalogue delays the next useful question.
Stable language and ontic precisionA shared designation aids communication, while agreement on a name alone can leave the referent and contribution connections unresolved.

SYSE.1:4 - Solution

SYSE.1:4.1 - State the current project decision

Begin with the cooperation and decision that need a shared reference. Recover:

  1. the product or products and the intended use that justify the work;
  2. the System or other subject the local work must create, change or investigate;
  3. the contribution needed from that work and the conditions for accepting or stopping it; and
  4. the plan or decision that needs the SoI designation now.

For work that creates or develops an organization as a creator, retain the SoI on the product side. Name the organization as the creator being engineered. Its use, functions, structure, characteristics, realization and own creators can all require full engineering. The SoI name is not a prerequisite for those operations. The product and creator retain those roles when the organization is given a new label or the work is assigned to an external consultant under a new contract.

The local project can finish when its agreed contribution has been established. For example, a planning-system project can establish the ability to produce usable plans under specified order changes before the corresponding products enter service. Product usefulness, organizational capability, software installation and acceptance of a limited supplier contribution have different evidence. Preserve the responsibility and limits of each undertaking.

For a shared creator, retain the products or classes of future use that govern its capability, including differences that compete for the same resources. Do not select one convenient product to hide that competition. An unsettled future use can require research into concrete possibilities; do not invent a finished product to complete the account. Research retains its own epistemic result and stopping conditions.

A supplier can have a different product. A machine can be its maker’s SoI and a creator at the customer’s factory; an engine can be its maker’s SoI and an aircraft component. Recover the usable supply, recipient or class of applications, substantive decision boundaries and acceptance obligations. The customer may specify the design and use. The supplier need not control the whole product strategy or accept responsibility for every larger system. These facts inform the judgement; the existence of a separate contract alone does not make the same servicing or organizational work a different product.

Keep each local project, commitment and result identifiable. A programme or portfolio can coordinate priority, resources, investment, risk or evidence without becoming one acting System. Use A.1.STM when the product purpose or its relation to the creator remains unresolved.

SYSE.1:4.2 - Recover the direct subject before forcing a System choice

Use A.15.6 when project, process, or case wording hides whether the current subject is performed Work, a reusable Method, a selected structure, a transformation-flow structure, a changed referent, or another claim. If that direct subject answers the decision, stop this pattern use and keep the subject under its own FPF pattern.

When the decision does need a System, distinguish two cases:

  • For an actual System, use A.1.SCR when recognition is unresolved. Its constructive criterion supplies the tested System identity and boundary used in the comparison.
  • For a System that does not yet exist, keep the intended referent in the current plan, decision, or description. Do not describe it as an already acting System.

Recognition, choice of an engineering subject and SoI designation remain different claims. Recognizing an actual System does not determine its project role; selecting an intended referent does not make it physically present. An organization can be the immediate engineering subject while remaining a creator of the product SoI.

SYSE.1:4.3 - Generate and criticize materially different referents

Generate materially different product referents from the working situation using the existence and recognition conditions in §4.2. A product, component, tool or operating System can be a candidate when its intended use supplies the product grounds for the cooperation. Apply §4.1 to distinguish a supplier’s own product from work on the same creator under another project name.

For each candidate, compare the claims that matter now:

  • the intended useful functioning and the receiving situation;
  • the product boundary and its relation to the participants’ contributions;
  • the participating and affected Systems;
  • the part, interaction, containment, ownership, authority or other relations that can change the decision;
  • characteristics, constraints, feasibility, evidence and uncertainty; and
  • the assumption or observation that would defeat the candidate.

Alternatives for an organization, platform or production arrangement remain full engineering alternatives. Compare their functions, construction, obtaining ways and capability against the products or future uses they must serve. Choosing among those creators does not by itself change the product SoI.

Payment, delivery, ownership, organizational boundaries and local acceptance can inform the judgement. None alone establishes the SoI. A firm’s sale or valuation is an economic question; work on that firm’s productive capability engineers a creator. Preserve the economic question and its own evidence.

Retain several product candidates when learning can change their order or when they preserve valuable options. For several products served together, retain their common demands and consequential differences. Let the current decision, available resources and useful stop determine the comparison effort. Stop when you can ask the next engineering question and the reopening condition is clear.

SYSE.1:4.4 - Record a sufficient choice account

Start with the following content in any readable form:

Project-system choice account:
  cooperation and current decision:
  product SoI or intended referent, and intended use:
  immediate engineering subject and bounded result, when different:
  current grounds and any main unresolved assumption:
  local acceptance and receiving obligations that matter now:
  reopen condition:

Include several products or classes of use where the creator must serve them together. Add alternatives, participation, authority, realization or evidence only when they change the choice or its use. A short existing explanation can suffice.

Stop when the project can ask the next concrete engineering question about the identified subject for the stated purpose. Supply SYSE.2 with that subject’s use, the product grounds it serves, the boundary question, alternatives and reopening condition. Engineering the creator does not require designating it as another SoI.

SYSE.1:4.4.1 - Establish enough common focus for the current coordination

When a decision depends on several contributors, compare their understanding through one concrete use or change. Include the participants whose contribution, receiving use or limits can change that decision. Existing compatible exchanges may supply the answer.

Establish from each contributor which products the joint work serves, what their work concerns, what they supply, to whom and under what conditions and limits. For each consequential connection, establish from the receiver what they expect and how they will use the contribution. A conversation, annotated case, asynchronous exchange or existing work that shows what the participants supply and expect can provide these answers.

For example, “install the planning software” and “produce a feasible production plan” can share a project name. Follow one order moved to an earlier date. Determine whether installation, current stock information, capacity decisions and the planner’s use connect to feasible commitments for the manufacturer’s products. A missing contribution can leave the planning capability unavailable even when installation is complete.

Use the available contributions to resolve a material mismatch with the party authorized to decide. Explain the selected product grounds and local engineering subject, then ask the affected contributors to use them on the same case. Enough common focus exists for this decision when those relying on it can identify these subjects, connect the contributions needed by their next action and identify any unresolved condition that limits it. They may retain different interests and preferred alternatives. Obtain permission and commitments separately where the next action needs them.

If participants still mean different subjects or cannot connect a needed contribution, retain the individual account as provisional and hold only the joint claim that relies on the unresolved connection. Name the missing answer; independently supported work can continue. Separate projects retain their own boundaries and acceptance. They can share a product SoI. When an independently supplied product has its own SoI, coordinate the receiving contribution between them; use SYSE.8 for provision or SYSE.9 for a specialist return where needed.

Keep the account aligned with the result: a provisional individual choice, sufficient common focus for a named decision, an unresolved mismatch or coordination between distinct product undertakings.

SYSE.1:4.5 - Reopen the choice from the answer that failed

Reopen the account when one of these changes the comparison:

  • observed or expected use crosses the assumed boundary;
  • authority or permission makes the intended change unavailable;
  • an architecture candidate moves important functioning to another System;
  • no feasible realization branch supports the selected referent;
  • operating or assurance evidence defeats the reason for the choice; or
  • a changed product or intended use materially changes the grounds of the cooperation.

A project split, new contract or changed performer can reopen local scope, provision or authority without changing the product SoI. Reconsider that designation only when its product and use grounds change.

An observed mismatch between contributors reopens the common-focus claim in §4.4.1 even when the individual choice remains defensible. Repeat only the exchange affected by that mismatch; reconsider the SoI designation if its product or intended-use grounds have changed.

Return to the failed claim or linked claims that affect the next move. A changed use assumption may require SYSE.2 before the project focus changes. A failed bearer or architecture candidate may return through C.30 or C.32. Reopen the SoI designation only when the evidence changes which product or intended use should orient the cooperation. Reopen the local engineering subject or acceptance separately when those are the affected claims.

SYSE.1:5 - Archetypal Grounding

SYSE.1:5.1 - Pumping station under flood risk

A flood-reduction project starts with the phrase “new pump”. The engineer compares the pump unit, the pumping station, the drainage-control System, and a provider arrangement. Flood-control use crosses the pump-unit boundary: positioning, power, control, discharge conditions, and downstream exposure belong to the station’s current use question. The engineer selects the pumping station and records:

selected referent: intended pumping station
current reason: move water under the selected flood load as part of flood-control use
main unresolved assumption: downstream exposure remains acceptable
reopen: use, architecture, realization, or operating evidence changes that assumption or boundary

SYSE.2 can now link the flood-load use claim to a station concept. Later discovery that the proposed station increases downstream harm changes the linked use claim. It reopens the project-system choice only when that changed claim defeats the reason or boundary used by the choice account.

SYSE.1:5.2 - Manufacturer and ERP vendor

A manufacturer supplies pump installations for water supply and seasonal irrigation. Its “new ERP” project begins because production plans repeatedly fail. The engineering lead compares software installation, a changed planning organization and an integrated planning arrangement. These are alternatives for improving the creator. The product grounds remain the two lines’ installations and their intended uses; their different configurations, delivery commitments and resource demands must fit the plans.

The lead selects the deployed planning arrangement as the immediate engineering subject. Its proposed local result is the ability to produce feasible production commitments from current orders, stock and capacity under specified changes. Current-information availability is the main unresolved assumption. This is enough to begin concept work without naming the planning organization a new SoI.

Before assigning joint work, she asks the contributors to follow one order moved to an earlier date. IT means the installed ERP runtime by “our system” and can supply software installation and data interfaces. The planner needs current stock and capacity information and a way to resolve conflicts between the two product lines. The stock controller expects the overnight update to remain sufficient. The independent software vendor supplies a standard ERP product and needs to preserve a supportable configuration.

The exchange exposes a missing contribution: rescheduling can use stock information that predates the moved order. Installation and software delivery alone cannot establish the planning capability. The manufacturer’s authorized decision holder retains the planning arrangement as the local engineering subject. The stock controller and planner investigate current-information and confirmation alternatives; IT identifies the required interfaces. Each contributor explains what the planner would receive, and the planner states what is still needed before issuing a production commitment. SYSE.2 can compare these arrangements while retaining the product obligations they serve.

If that information cannot be obtained, the joint planning-capability claim remains open. An independently supported interface investigation can continue. If the authorized scope covers only software deployment, acceptance can close that bounded contribution against its own criteria. It leaves the planning capability and product consequences unestablished. The smaller contract does not change the manufacturer’s product SoIs.

Now transfer the same planning-change work to an external consultant with a separate budget and completion date. The consultant may design the organization, its functions, responsibilities, tools and supporting work. Acceptance can establish its agreed capability under representative order changes and operating conditions before the resulting pumps enter service. The consultant’s responsibility remains limited to the accepted scope. The external contract creates neither another product purpose for this work nor a requirement to wait for every downstream product outcome before closing it.

The ERP vendor’s own product undertaking has different grounds: a usable software product supplied to customers under identified decision and acceptance boundaries. That software can be its SoI while it is a means in the manufacturer’s planning arrangement. The parties coordinate their contributions and commitments without merging their projects or interests. A vendor label or a deployment contract by itself would not establish this independent product case.

SYSE.1:5.3 - Continuing building through several projects

For example, design, construction, operating retrofit, and heritage-restoration Work can concern one continuing building while using different plans, transformer Systems, access arrangements, and evidence. In an occupied retrofit, the engineer selects the continuing building because its occupied performance is being changed and records access during use as the main unresolved assumption.

Different descriptions of the same building can serve one project or several. One programme overseeing several projects does not become the performer of all Work. Each project account states its own reason for selecting the building and can reopen that choice when its reason or conditions change.

SYSE.1:6 - Biases to Watch

Two recurring biases matter in this decision. System inflation forces every important project subject into U.System; use A.1.SCR and the direct-subject exit before choosing. First-candidate lock-in turns the first plausible referent into permanent project scope; retain material alternatives and state the reopen condition.

SYSE.1:7 - Conformance Checklist

IDRequirement
CC-SYSE1-1A conforming use SHALL name the current project and the decision that needs a project-system choice.
CC-SYSE1-2It SHALL retain a direct non-System subject when System designation is not needed, and SHALL use A.1.SCR when actual System recognition remains load-bearing.
CC-SYSE1-3It SHALL distinguish an actual System from an intended referent in plan, decision, or description content.
CC-SYSE1-4The first useful account SHALL name the product SoI or intended referent, intended use, any main unresolved assumption and reopen condition; when the local engineering subject differs, it SHALL preserve that subject and the bounded result needed from it.
CC-SYSE1-5When materially different actual Systems or intended System referents remain plausible, the account SHALL compare their decision-relevant claims and SHALL keep every non-System subject under its direct pattern rather than admit it as a candidate referent for the project system-of-interest.
CC-SYSE1-6Additional account content SHALL be added only when it changes the current choice or a downstream use.
CC-SYSE1-7A stop SHALL make the next use-and-system concept question askable; a reopen SHALL name evidence or a changed project condition that can alter the choice.
CC-SYSE1-8Related projects SHALL retain their own work boundaries and acceptance while preserving a common product SoI where they serve the same product. A different contract or performer SHALL NOT alone justify another SoI for organizational work; an independent supplier product needs its own use, decision and acceptance grounds.
CC-SYSE1-9Before coordinated Work relies on a shared focus, the relevant contributors SHALL establish a common referent and the contribution connections needed for that decision, or identify the unresolved mismatch and limit the dependent coordination. A written account alone SHALL NOT establish this result.

SYSE.1:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWorking symptomRepair
Project-name shortcutThe noun in a charter or backlog is used as the selected System without a use or change reason.State the current project decision, generate plausible referents, and compare how each changes the next question.
Tool or provider substitutionThe immediate engineering subject replaces the product that justifies work on its creator.Keep the product SoI, creator and local result distinct. Engineer the creator fully and accept its bounded contribution; establish separate product grounds before selecting a supplier product as another SoI.
Account-as-agreementA clear choice recorded by one contributor is treated as the participants’ shared project focus.Follow a concrete use through contributors and receivers; resolve the material mismatch or limit the coordination that depends on it.
First-candidate freezeWork has started, so later use or feasibility evidence is treated as irrelevant to project focus.Record the grounds and reopen condition with the first choice, including any main unresolved assumption; return evidence to that claim when it changes.
Important-subject inflationA desired state, Work result, description, collection, capability, or transformation is called a System because the project centres on it.Keep the direct subject and use its FPF pattern. Open SYSE.1 only if a System designation is required for the current project decision.
Programme-as-performerShared resources or one programme plan are treated as proof of one composite acting System.Use the programme or portfolio grouping for its coordination decision and establish any System composition separately.

SYSE.1:9 - Consequences

The cooperation gains defensible product grounds and an explicit local engineering subject. Contributors can compare what each must supply without treating a local completion as the final product result. Several projects can retain one product SoI; independent product undertakings can retain different SoIs and connected commitments. Architecture and realization evidence can reopen the claim it defeats.

The cost is visible uncertainty and, for a shared claim, comparison of participants’ understanding. Several candidates may remain open. Spend that effort where an unresolved difference can redirect architecture, provision or acceptance; reuse compatible established results.

SYSE.1:10 - Rationale

Engineering decisions need an identified subject. The system being engineered and the product whose use justifies the cooperation can be different Systems. Keeping both makes it possible to develop a creator’s full functioning and construction while using product requirements to judge its capability, priorities and shared resources.

SoI designation remains a choice under uncertainty. System recognition, a project name and a local contract do not settle it. Actual identity, intended reference, the project role and the account describing the choice have different grounds. Local acceptance establishes only the contribution it tests and can precede the product’s later use.

Outside use supplies the grounds of the comparison rather than a fixed calendar order. Problem framing, concepts, architecture, realization and evidence can develop together. Reopen the product choice, local subject or provision arrangement according to which premise changed.

SYSE.1:11 - SoTA-Echoing

The practice question is how to establish a defensible, shared and revisable project focus for the next engineering decision. The selected answer combines explicit framing and valuable alternatives with the contribution comparison in §4.4.1. The following research lines support parts of that synthesis; they do not establish its comparative effectiveness as a whole. The work titles, primary identifiers and evidence limits are in the public project-focus research sources.

Current practice lineWhat changes in this patternSource and useAdoption status
Design framing treats what matters to a design problem as revisable while problem and solution understanding develop together.The Solution makes the project-system choice revisable and requires the use, assumptions, and contextual relations behind it.Kelly and Gero (2022), Litster, Cardoso, and Hurst (2024), and Nickel, Hurst, and Duimering (2024). These conceptual and small empirical studies support explicit framing and revision, not one framing ontology or universal Method.Adopt and bound. Adopt co-development and contextual comparison; let the project decision select the focus and establish actual System identity separately.
Set-based design retains alternatives while learning can change feasibility or trade-offs.The Solution asks for materially different referents and preserves valuable alternatives when the decision needs them.Toche, Pellerin, and Fortin (2020) review the set-based line; Al Handawi et al. (2024) demonstrate margin-based exploration in one aeroengine-component case.Adapt. Retain alternatives and narrow them by evidence; let the receiving project determine candidate count and decision choreography.
Decision making under deep uncertainty uses robust alternatives, staged commitments, monitoring, and revision rather than prediction alone.Record what would warrant reconsidering the first choice. If that choice depends on a materially uncertain assumption, identify it so later evidence can be brought to bear on it.Haasnoot et al. (2013), Marchau et al. (2019), Lempert et al. (2024), and Akse (2024), mainly in climate, infrastructure, policy, and sociotechnical-transition settings.Adapt. Use staged commitment and explicit reopening; let the receiving project establish its scenarios, thresholds, triggers, and decision Method.
Entrepreneurial-action research treats available means, commitments, contingencies, prediction, and judgement as context-dependent complements.Candidate generation may use available Systems and commitments without treating them as proof of the project referent or of success.Chen, Liu, and Chen (2021), Zhang et al. (2023), and Rapp, Olbrich, and Packard (2026). Meta-analytic associations and conceptual synthesis do not establish one causal engineering Method.Adapt narrowly. Keep contingent action and revision as candidate pressure; leave business and Strategy decisions with their practices.

The serious practice alternative is the NASA handbook’s Stakeholder Expectations Definition. Its iterative treatment uses operating scenarios to refine expectations, develop mutual understanding and obtain commitments. Those operations are useful here; its broader programme baseline is not required for every provisional choice.

Compare both ways on the ERP case at the same effort: the same contributors examine one moved order and its receiving use. A bounded expectations-and-scenario discussion can expose the stale-information gap. The §4.4.1 contribution comparison can expose it too. SYSE makes the designation question explicit alongside that discovery: which product use grounds the cooperation, which System is being engineered, and which contributions have separate acceptance boundaries? Its direct-subject exit remains available in §4.2.

For this next concept decision, the selected result is a revisable focus and the unresolved connection. A complete expectations set and broader commitments remain open. When the receiving decision needs those results, obtain them through the expectations treatment. When an existing scenario exchange already establishes the needed focus and connections, reuse it. A shorter account does not reduce the work participants need to establish a common focus. This comparison does not establish a general time or outcome advantage.

Reopen this methodological choice when contributors can repeat the designation but apply incompatible contribution paths, or when a bounded scenario or facilitated framing treatment resolves the same mismatch with less reconstruction. Repair the failed connection or use the better-suited treatment. Reconsider the retained research contribution when its evidence or transfer conditions no longer support the receiving use; keep the affected project’s assumptions and return in view.

These sources support comparing and revising project focus. Actual System recognition uses the FPF U.System criterion. FPF A.1.STM supplies the Library convention that organizational engineering retains the product SoI while fully engineering the creator. The research lines above do not establish that convention or its human effects. The pump, ERP and building cases apply it to their stated product, use and acceptance grounds.

SYSE.1:12 - Relations

  • A.15.6 distinguishes project Work, process, case, Method, transformation, selected structure, and project system-of-interest wording before the practitioner uses this pattern to make a System choice.
  • A.1.SCR supplies the constructive recognition result when the comparison depends on whether a candidate is an actual acting or changed System. It also supplies the direct-subject exit when systemhood is not load-bearing.
  • SYSE.16, SYSE.17, SYSE.2, and SYSE.8 may use the project-system choice account when their question concerns compatible subjects, configuration, decision and evidence. Supply the immediate engineering subject and its relation to the product SoI separately when they differ; this imposes no temporal order.
  • An engineer uses SYSE.2 to develop linked use and concept claims whose failure may revise the choice. The resulting linked proposal helps frame the architecture question. C.30 defines that question and C.32 guides candidate synthesis; infeasibility or harm returns through the affected linked claims and reopens this pattern only when project focus changes.
  • A.1.STM provides the wider systems-mantra traversal when a practitioner must reconnect this local choice to intended product use, architecture, realization, change and recursive creators. It supplies the product/creator distinction while leaving the case-specific designation and actual Work order to their grounds.
  • The applicable FPF decision, authority, evidence, value, harm, temporal, and direct-relation patterns define or constrain those claims when the engineering question calls for them.

SYSE.1:End

SYSE.16 - Recover the Systems and Conditions Needed for a Use Decision

Status: Stable

SYSE.16:0 - Use This When

Use this pattern when an engineering decision concerns an actual System or intended System referent selected for engineering, but everything outside it has been reduced to one box called environment, stakeholders, users, the business, or the platform. The decision needs to know which larger Systems contain it, which other Systems interact with it, which transformation flows and interfaces matter, and which outside conditions can change the result.

Begin with one use situation and one receiving engineering decision. Recover only the Systems, direct relations, selected structures, conditions, evidence, and assumptions that can change that decision.

The first useful result is a bounded engineering-use account. It describes how an actual System participates, or how an intended System is expected to participate, in one named use situation. The account is an episteme used by those making the decision. The situation, actual Systems, containing wholes, and other obtaining relations remain its world-side subjects.

Stop with the relations that answer the use decision. Use the governing FPF pattern directly when one known relation—such as parthood, interface, interaction, flow, or an architecture relation—answers the question. Use SYSE.1 when the relation between that engineering subject and the product SoI is unclear. A creator retains its own engineering-use question while serving the product use.

SYSE.16:0.1 - Terms and Distinctions

Name in this patternWhat it denotes
engineering subject and product SoIThe actual System or intended referent examined here can be the product, a component or a creator. For a creator, retain the products and intended uses that ground its required capability. Engineering subject, product role, identity and existence are separate claims.
use situationA bounded actual situation in which the System participates, or a described possible-future situation in which the intended referent would participate. A scenario or diagram is a description of that situation.
containing wholeAn actual System of which the selected System is a proper part under a stated relation, or a possible-future whole in a proposed proper-part claim. One System can belong to several relevant wholes under different relations.
suprasystemOptional source wording for a containing whole. Use it only when the proper-part claim is stated.
other System in the use situationAn actual System, or intended referent, connected by a named non-part relation that matters to the decision. Examples include an interaction or transfer between named Systems; observation of one System by another; access granted by a provider System to a receiving System; supply of a named result from provider to receiver; receipt or use of that result; a commitment between named Agents; or a consequence relation.
operating conditionA decision-relevant condition—for example, temperature, load, connectivity, price, an applicable regulation, or an available resource. A condition is a System only when it independently meets the System criteria.
functional organizationSelected transformation flows, interactions, and contributions, with the actual Systems that bear or participate in them.
constructive organizationSelected actual or proposed parts, bearers, modules, interfaces, and connections. Establish its parthood and connection relations independently of functional contribution.
engineering-use accountThe episteme returned here: selected Systems, relations, structures, conditions, evidence, unsupported assumptions, and reopen conditions for one use decision.

SYSE.16:1 - Problem Frame

Engineering choices—such as choices about System functions, architecture, interfaces, offerings, assurance, or change—depend on larger working situations. Teams nevertheless often begin with an inside representation, such as a product boundary, organization chart, component list, requirement set, or model repository. Outside Systems appear only as labels around a box.

Distinguish the functional transformation and interaction, constructive parts and interfaces, boundary relations, operating conditions and possible changes that matter to the decision. Use representations that keep these distinctions usable.

SYSE.16:2 - Problem

A generic environment box hides incompatible claims. A customer can own a System without operating it. An operator can interact with it without containing it. A building can spatially contain a device while another System whole receives the result of its functioning. A cloud service can sit outside a product boundary while remaining part of an offering arrangement. A regulator can constrain Work without being part of the operational System.

When those relations remain implicit, a plausible concept can fail in use, an interface can be assigned to the wrong bearer, a provider can promise a result no arrangement can deliver, or later evidence can have no clear decision to reopen.

SYSE.16:3 - Forces

Recurring tensions include:

  • An account must be broad enough for the decision while affordable to obtain and maintain.
  • Project boundaries simplify Work, while outside Systems and conditions can still change the engineering choice.
  • One System can participate in several wholes and selected structures at once.
  • Functional transformation and constructive structure must correspond without being collapsed.
  • Design choices concern possible futures; claims about actual participation or observed conditions concern what has happened or currently holds.
  • Relevant surroundings continue to change—for example, providers, users, infrastructure, rules, competing offerings, or operating conditions.
  • Existing vocabulary helps communication but can import ownership, lifecycle, or stakeholder assumptions that do not match the current relation.

SYSE.16:4 - Solution

Recover the Systems, structures, relations and conditions needed to ground one use decision. Begin with the actual System or intended System referent selected for engineering and its named use situation; stop when the account supports the receiving decision or identifies the condition that prevents it.

Reuse an adequate existing account or direct relation result for the same decision and conditions. Use the bounded recovery below when a missing connection prevents that answer. If the operating situations themselves need development or agreement, use a suitable scenario or concept-of-operations Method; obtain any missing specialist result from its domain before relying on it.

SYSE.16:4.1 - Perform the Move

  1. Bound the use and decision. State the actual System or intended System referent selected for engineering, its use situation, configuration or variant, decision, relevant place, horizon and description sources. When it is a creator, retain the products or classes of use that ground the required contribution and local acceptance. Keep the descriptions separate from the Systems and situation.
  2. Find containing and receiving Systems. Identify every larger System that matters because the selected System is, or would be, its proper part, and every System that receives or would receive a result of its functioning. State each direct relation and whether it is actual or proposed; retain several wholes when the decision depends on them.
  3. Recover functional organization. Identify the transformation flows, interactions, and contributions in which the System participates, including the changed or receiving Systems and conditions. Use A.6.F for function-like claims and E.18.NET when a transformation-flow network is needed.
  4. Recover constructive organization. Identify the structures that matter to this use—for example, parts, bearers, modules, interfaces, or connections. Use A.22 for each selected structure and A.6.M only when module or interface claims obtain. Do not infer constructive parthood from a functional contribution.
  5. Add other Systems and conditions. Include only a System or condition whose named relation can alter the use result or engineering choice. State that relation and its participants or state the relevant condition. Examples include a transfer from a named supplier System to a named receiver, access granted by a provider System, a permission or commitment between named participants, an available resource, or an operating constraint. When performed provider Work matters, identify the dated Work occurrence, performer Agent, and applied Method separately. For proposed provider Work, identify the intended Work, performer and Method, and the commitment or capability evidence available. Then name only the direct relations used by the decision: Agent participation in the Work, result production, supply or access from provider to receiver, receipt or use of the result, a commitment, or another governed provision relation. Distinguish obtaining relations from proposed ones. A commitment does not establish that Work or delivery occurred.
  6. Separate future choices from present facts. Mark descriptions as observations, predictions, design choices, commitments, or unsupported assumptions. A proposed interface or whole does not obtain merely because a model contains it.
  7. Test outside change. Ask which relevant outside factors—for example, Systems, conditions, interfaces, providers, uses, or regulations—can change during the relevant horizon and which change would reopen the concept, architecture, offering, assurance, or configuration decision.
  8. Return the result needed by the decision. Supply the supported relations and conditions, or the material mismatch, alternative, evidence need or unresolved assumption, to the receiving engineering Work.

The numbered steps explain the Method. Determine Work order from the dependencies and conditions of the work. Observation, concept development, architecture development and trials can overlap and recur while outside Systems change.

SYSE.16:4.2 - Record the Result

FieldRequired content
focus and decisionActual System or intended referent being engineered, its use, receiving decision, configuration, relevant place and horizon; for a creator, the product uses and contribution that ground its capability and local acceptance.
containing and receiving SystemsEach larger or receiving System and the proper-part, transfer, interaction, or other direct relation that matters.
functional organizationSelected transformations, flows, interactions, contributions, changed or receiving Systems, and operating conditions.
constructive organizationSelected parts, bearers, interfaces, modules, and connections needed by the use.
other Systems and conditionsProviders, users, resources, constraints, and their stated obtaining or possible-future relations.
epistemic statusObservation, evidence-backed claim, prediction, design choice, commitment, or unsupported assumption.
co-change and returnOutside changes that reopen the decision, evidence that would reveal them, and the supported result, mismatch, alternative, or missing result supplied to receiving Work.

For a bounded first result, one decision-changing containing or neighbouring System, one named relation or condition, its epistemic status and one result for that decision may suffice. For an unknown that can change the result, state which decision it blocks. Use several representations when needed, keeping them distinct from the use situation and System whole they describe.

SYSE.16:4.3 - What Changes in Practice

The engineer identifies the Systems, structures, direct relations, and conditions that make this use work. Functional transformation and constructive structure stay separate, outside change becomes an engineering input, and the account identifies any assumptions that remain unsupported.

SYSE.16:5 - Worked Case: Upgrading an Occupied Building’s Heat-Pump Plant

An engineering team is deciding whether to add a new controller configuration to an existing heat-pump plant for the next heating season. The decision asks whether occupied rooms can remain within the selected thermal range while the plant responds to grid signals.

The engineering-use account distinguishes these structures and relations:

  • Actual System and containing whole. The heat-pump plant is an actual System and a proper part of the building heating System. The proposed controller is an intended referent. The occupied building and its heating System are not assumed to be the same whole.
  • Functional transformation and transfers. An electricity-distribution System transfers electrical energy through the feeder. A signal channel transmits demand-response information. The plant transfers thermal energy to the hydronic loop, and the loop and radiators transfer it to room air. Envelope heat transfer and occupant control actions also change room temperature.
  • Constructive organization. The feeder, sensors and controller cabinet are physical bearers. The account also identifies the hydronic connections, proposed controller interface and signal channel. Required clearance around the cabinet is a spatial condition on its location and maintenance access. Establish the part and connection relations independently of the functional-flow description.
  • Maintenance supply, access, and Work. Under MaintenanceCommitment-14, maintenance company HeatCare-7 commits to supply ControllerInspectionResult-14 to building operator BuildingOperator-1 before the controller-configuration decision. The building operator grants HeatCare-7 plant-room access during stated windows. Technician T-4 is the intended Agent for ControllerInspectionWork-14; that Work has not occurred. The plan calls for the Work to produce the inspection result, for HeatCare-7 to supply the result to BuildingOperator-1, and for the operator to receive it for the controller-configuration decision. Establish which of these events have occurred when the decision depends on them.
  • Systems that may bear consequences. Residents in a nearby building may experience increased low-frequency noise during night cycling. A model supports this possible consequence; no night measurement has established an observed effect.
  • Unsupported assumptions. Sensor latency and occupant override behaviour are unknown at the required load. A planned insulation change may alter the thermal model. Cabinet clearance is supported by a drawing but has not been checked in the plant room.

For the cabinet-location choice, the next result is confirmation of the required and available clearance under the installation and access conditions. If those conditions already determine the required clearance, the team can answer that spatial question directly. If occupant and grid-control behaviour leave the operating situation unsettled, develop the relevant scenarios before relying on that use.

The account changes three next decisions. The Agent applying SYSE.17 uses the possible acoustic-exposure and maintenance-access consequences. The Agent applying SYSE.8 uses the maintenance commitment, provider and access relations, and the need for the inspection result. The Agent applying SYSE.2 uses the revised use claims and low-noise and cabinet-location alternatives. If the team also considers remote monitoring, that is a proposed offering: this account establishes neither its provider commitment nor its authority. The remote monitoring claim remains conditional. The team can act on the supported inputs.

When the full pattern is unnecessary. If the current question is only whether one already identified sensor is a proper part of one known controller under an admitted relation, use the direct System and parthood patterns. A broader engineering-use account adds no value.

SYSE.16:6 - Bias Annotation

A source or representation—such as an official context diagram, stakeholder list, standard, or organization chart—does not by itself establish that a relation obtains or a Method is effective. Any capable and authorized Agent may develop the account. Capability and authority require grounds appropriate to that Work; a professional title, substrate or organization label is not sufficient on its own. Specialist Methods and evidence remain with their domains—for example, electrical, building, safety, legal, environmental, or financial practice. Agents with the relevant authority make the corresponding decisions.

SYSE.16:7 - Conformance Checklist

  • The actual System or intended System referent selected for engineering, use situation, receiving decision, configuration and horizon are stated; a creator retains its product-use grounds and bounded acceptance.
  • Actual Systems and intended referents remain distinct from accounts, models, scenarios, and diagrams.
  • Suprasystem is used only with a stated actual or possible-future proper-part relation.
  • Functional transformation remains separate from constructive parts, bearers, and interfaces.
  • Other Systems and conditions appear only when a named relation can change the decision.
  • Observations, predictions, design choices, commitments, and unsupported assumptions remain distinct.
  • Outside changes and evidence that reopen the decision are stated.
  • The account supplies the relations and conditions sufficient for the receiving decision, or identifies a material mismatch, alternative, evidence need or unresolved assumption.

SYSE.16:8 - Common Failures and Repairs

These recurring abstractions hide a relation that changes the engineering decision:

FailureRepair
Everything outside becomes one environment boxRecover only the wholes, other Systems, conditions, and direct relations used by the decision.
Stakeholders stand for operational structureIdentify actual Systems and relations; use SYSE.17 for consequence-bearing Systems.
Every larger or influential object is called suprasystemRequire a proper-part claim or use the actual relation.
Function is treated as a componentKeep transformation flows and constructive structures separate and state their correspondence.
Diagram is treated as realityKeep the representation, subject, currentness, and evidence distinct.
Outside Systems are held constantRecord co-change and reopen evidence for the relevant horizon.
Environment analysis becomes an early phaseRevisit the account when concepts, architecture, evidence, configuration, or outside Systems change.
The team models surroundings that cannot change the decisionStop when the bounded account sufficiently supports the receiving decision or identifies the missing result.

SYSE.16:9 - Consequences

Engineering alternatives become comparable in the use that gives them meaning. Interface choices expose their bearers and receiving Systems, outside changes gain reopen conditions, and System or offering concepts no longer rely on an unexplained environment label.

The cost is maintaining the selected structures, conditions and their correspondence. A bounded account accepts incomplete coverage of other uses; broaden the work when an omitted situation can change the decision.

SYSE.16:10 - Rationale

Systems matter through part, interaction, transformation, interface, transfer, and consequence relations under conditions. FPF supplies the general ontology for those claims. The engineering specialization is the repeatable move from one use decision to the outside relations and conditions that can change concept, architecture, offering, assurance, configuration, or continuing development.

SYSE.16:11 - SoTA and Source Use

Working question: Which Method should an engineer use when different relations hidden inside an “environment” label prevent one use decision?

The selected answer depends on what is missing. Use an adequate existing account or the direct relation Method when it settles the question. Use this bounded recovery when the needed result depends on connecting several Systems, relations and conditions. A developed concept-of-operations (ConOps) Method is an alternative when operational situations or agreement about intended use still need to be constructed. It develops and challenges scenarios; identifying a few relations cannot supply that broader result.

The bounded connection accepts limited coverage in exchange for concentrating the account on one decision. It needs the applicable evidence and specialist contributions. Section :4 makes this choice at entry; steps 1–6 recover the missing connections, and steps 7–8 return changed conditions to the affected decision. The bounded result in :4.2 is sufficient only within that use. In :5, cabinet location returns a spatial-evidence question, whereas unsettled occupant/grid behaviour returns scenario development. An adequate earlier answer can be reused in either branch.

Source answer and comparison roleDisposition, operative contribution and limit
Current FPF A.22:4.1, with the direct subject patterns named in :12: a supplying Method and a direct-use alternativeAdopt independent constituent, relation, constraint and use identification. Adapt that selection to the engineering decision in steps 1–6 and the :4.2 account. A spatial condition keeps its own meaning even when the same decision also needs a bearer or interface. The engineering-use account connects these selections to the receiving decision.
NASA Systems Engineering Handbook, §4.1.1.2.2–4.1.1.2.5: a developed professional alternativeAdapt elicitation, operational scenarios and agreement about use when those results are missing at :4’s entry. Follow significant nominal and off-nominal situations into interfaces and operator/support contributions. The handbook’s mission-specific organization is not imposed on every thin account.

Reopen the Method choice when a sufficient account becomes available, an omitted condition defeats the receiving use, the question expands to other scenarios, or a supported alternative offers a preferable combination of coverage and effort. Retain qualified evidence for unaffected claims while revising the dependent conclusions.

SYSE.16:12 - Relations

  • SYSE.1 can supply the engineering subject and its product-use grounds, decision, boundary question, alternatives and reopening evidence. A creator is usable as the engineering subject without another SoI designation. These result dependencies do not prescribe when to do the work.
  • A.1.SCR distinguishes an actual acting or changed System from a designation, role word, description, process, or organization label.
  • A.22 governs each selected structure. A.6.F restores function, bearer, capability, Work, and MethodDescription distinctions; A.6.M applies only to an obtaining module or interface claim.
  • E.18.NET applies when the use needs a network of transformation-flow structures. It identifies the selected structure; use E.18.2 for its graph or other mathematical description. Neither the network nor its description is the containing whole or a lifecycle.
  • Agents applying SYSE.17, SYSE.8, or SYSE.2 can use the account’s consequence, provider, or concept results. Each Agent rechecks subject, configuration, horizon, evidence, and compatibility for the receiving use.
  • Application profiles retain domain Methods and evidence—for example, Methods and results for operating physics, safety, legal compliance, medical use, finance, software, electrical systems, buildings, or ships.

SYSE.16:End

SYSE.17 - Find Systems That May Bear Engineering Consequences

Status: Stable

SYSE.17:0 - Use This When

Use this pattern when a decision about a proposed System, configuration, or use change names some participants—for example, users, owners, operators, or interacting Systems—but may omit bearers of consequences. Their states or decision-relevant characteristics could change through Work or events such as realization, operation, maintenance, misuse, failure, recovery, retirement, or later modification. Retain existing bearers even when their identities are only partly known. Qualify not-yet-present bearers as intended System referents in modal claims.

Begin with one proposed engineering alternative or change and the decision that can alter it. If an existing account covers the material consequences at the needed scope and evidence strength, use that answer. Otherwise trace possible consequences beyond the current contractual, organizational, and technical-interface boundaries. Keep obtaining relations, modal path claims, observed changes, value judgements, and specialist decisions separate. When the missing result is a person’s preference, an agreement, or an account of how a proposed operation would work, use a corresponding elicitation or scenario result, or return that missing input to the decision. Tracing consequences alone cannot supply it.

The first useful result is a bounded engineering consequence account. It identifies material consequence bearers as far as the evidence permits, preserves unresolved identity or existence questions, qualifies each consequence, and connects it to an action or unresolved need in the receiving decision—for example, a constraint, alternative, probe, safeguard, specialist question, monitoring condition, or explicit gap. The account is an episteme; the Systems and changes it describes remain world-side. Add a value or representation claim only when the receiving decision uses it and its own grounding is available. A.1.CSD supplies the general discovery move. This pattern specializes it for engineering choices: start from a proposed System, configuration, or use change and connect qualified consequences to the named engineering decision. Use C.28 when one identified causal claim is the whole question. Obtain a result from the applicable specialist practice whenever the decision relies on authority outside Systems Engineering.

SYSE.17:0.1 - Terms and Distinctions

Name in this patternWhat it denotes
focus of inquiryA proposed engineering alternative or change, together with the actual System or intended System referent and configuration to which it applies. If an observed result prompts the inquiry, use it as evidence for a newly stated change question.
consequence-bearing SystemAn actual System whose state or decision-relevant characteristic may change under the proposed alternative or change. Its identity may be only partly known. A not-yet-present bearer remains an intended System referent inside a modal claim.
unresolved bearer referenceA reference whose identity, boundary, or existence is not established to the extent needed by the decision. State which question is unknown. Unknown personal identity does not erase evidence that someone was present.
supported obtaining relation occurrenceAn actual relation occurrence under stated conditions, supported by evidence about its participants and predicate. Preserve any limits on participant identification: an observed encounter can be supported while personal identities remain unknown. A line in a diagram is only a representation.
modal consequence-path claimAn episteme describing relations and changes that may connect the proposed alternative or change to a bearer, with candidate participants, conditions, evidence, uncertainty, and the limit that matters to the receiving decision. A probe is conditional on its selected contribution. Support each relation claimed to have occurred with evidence of that occurrence.
consequence claimA claim about a possible or observed change, bearer, conditions, direction, time, evidence, uncertainty, and causal status. The claim and its world-side change have separate identities.
value-qualified consequence claimA descriptive consequence plus a stated value judgement—for example, benefit, harm, burden, or opportunity—under a named value frame, bearer, scope, and evidence.
affected-System claimA consequence claim that identifies the System bearing the possible or observed change. It supports that bearer–consequence statement; establish any project assignment, authority, or other relation separately when the decision needs it.
unresolved decision needAn episteme naming a result or relation that the receiving decision needs but does not yet have—for example, additional evidence, a specialist result, an authority relation, an authorized representative, or a safeguard.
engineering consequence accountThe episteme returned here: focus, examined situations, bearer references, supported obtaining relations, modal path claims, consequence claims, evidence, uncertainty, decision contributions, unresolved needs, and reopen conditions.

Test System identity when the claim relies on treating a bearer as one System—for example, when attributing a consequence to a population as a whole. Candidate bearers include people, organizations, technical Systems, and ecological Systems. Preserve evidence of an actual bearer even when its name or full boundary is unknown. Use an intended System referent for a not-yet-present bearer, and state when the bearer’s existence is unestablished. A project assignment or decision authority requires its own grounding.

SYSE.17:1 - Problem Frame

Engineering decisions and descriptions guide realization, operation, maintenance, and modernization Work. The resulting changes can reach Systems outside the project’s influence and formal organization—for example, a downstream resident, future operator, maintenance provider, ecological System, supplier, bystander, competing resource user, or later user. Discover such a bearer from the consequence claim rather than from a stakeholder label.

The engineering problem is to discover enough consequence-bearing Systems, qualify the claims about them, and return unresolved consequences while the receiving engineering decision can still be altered.

SYSE.17:2 - Problem

Stakeholder lists are commonly built from cues such as visibility, power, contracts, interfaces, or organization charts. Those cues can miss, for example, quiet, weakly represented, future, indirect, non-human, or cross-boundary consequence bearers. The opposite error is to call every mentioned party affected without naming a change, evidence basis, or decision use.

A plausible arrow from a proposed change to a possible bearer can be mistaken for an actual relation or causal effect. Treat the arrow as a representation and ground the represented relation’s participants and predicate separately. Scale words such as person, team, organization, society, and ecosystem provide candidate scopes; recover actual Systems, whole–part relations, causal relations, and observed changes from their own evidence.

Too little discovery can leave material cost or harm outside the decision. Unbounded inquiry can consume the resources needed to act, especially when possible consequences are treated as equally established.

SYSE.17:3 - Forces

Recurring tensions include:

  • Consequences can cross boundaries of contract, ownership, organization, interface or project.
  • Early choices need expert judgement; exhaustive measurement is often unavailable or uneconomic.
  • A weakly supported possibility can justify a cheap probe or reversible design, but not an observed-effect claim.
  • A descriptive consequence claim, a value judgement, and a deontic or governance claim use different predicates and evidence.
  • Constituent, containing, neighbouring, and later reidentified Systems can change differently; aggregates can hide those distributions.
  • Specialist safeguards must inform the engineering decision without Systems Engineering claiming authority it does not have.

SYSE.17:4 - Solution

Apply the general affected-System discovery move to one proposed engineering alternative or change. First compare the available account with the receiving decision: does it cover the material bearers, consequences, conditions, and evidence needed now? Reuse a sufficient answer. If a missing consequence or bearer could change the choice, perform the bounded discovery below. If the choice instead needs preferences, agreement, or developed operating situations, use an available elicitation or scenario result, or assess its acquisition under step 8. Return a needed but unavailable result as an explicit gap.

Retain consequence claims that support, change or hold open the named engineering decision, and state what supports each. A bounded account can support a choice when it states any material uncertainty. Use separate grounds for preferences, representation or operating scenarios when the choice depends on them.

SYSE.17:4.1 - Perform the Move

  1. Name the focus and receiving decision. State the proposed alternative or change, the actual System or intended System referent and configuration to which it applies, the use situation, relevant scope and horizon, and the engineering decision that can use the result.

  2. Generate consequence-producing situations. Consider Work and events that may expose the alternative’s consequences—for example, realization, intended use, maintenance, plausible misuse, failure, recovery, retirement, or later modification. Retain situations whose consequences bear on the receiving decision.

  3. Trace outward without promoting hypotheses to facts. Follow supported obtaining relation occurrences separately from modal consequence-path claims. For each modal path, name candidate participants and proposed relation kinds—for example, material transfer, energy transfer, information transfer, exposure, access, resource use, an economic relation, or an institutional relation—together with conditions, evidence, uncertainty, and the useful consequence or limit for this decision. A modal path does not itself select a probe.

  4. Identify the bearer to the extent needed by the claim. Keep an observed participant actual even if its name or full identity is unknown; refer to the observation, place, and time that support the claim. Keep a not-yet-present bearer as an intended System referent in a modal claim. If existence itself is uncertain, retain that uncertainty. Test System identity and boundary when the consequence claim depends on that classification, especially for a collection treated as one whole. A role label or an appointment to represent a group does not establish the group’s identity or boundary. Return any unresolved recognition question that matters to the decision.

  5. Qualify the consequence. State the characteristic or condition that may change, bearer, configuration, conditions, direction or magnitude cue when known, interval, and uncertainty. Distinguish an observed occurrence from a modal claim. State the evidence basis—for example, observation, measurement, simulation, model-based prediction, or a bounded expert estimate—and its limits. Use C.28 when reliance depends on a causal, intervention, or counterfactual claim.

  6. Add value and specialist claims only when needed. Name the bearer and value frame for a value-qualified consequence—for example, a claimed benefit, harm, burden, opportunity, or accepted loss. Preserve conflicts and distributions. Select any specialist acquisition through A.15.9 and C.11.DUA before sending the question with its System, claim, evidence, and receiving decision; keep the returned authority boundary visible.

  7. Connect consequences to the engineering choice. Add or revise a decision contribution—for example, a constraint, alternative, probe, safeguard, monitoring condition, reversible step, refusal, or escalation. When that contribution relies on permission, authority, responsibility, or representation, establish the required relation separately.

  8. Finish with the useful answer and its material uncertainty. A qualified consequence account, constraint, alternative, or explicit unknown can complete this use. Select a further discovery action through C.11.DUA only when its obtainable contribution warrants the full preparation, access, performer, interpretation, delay, displacement, and downside. Compare what each proposed observation and the combined inquiry could contribute with the resources they would require in the available decision window. Retain the residual and reopen condition that matter to the receiver. Reopen the account when a new bearer, changed configuration or use, conflicting value claim, failed premise, or required missing authority could change the decision. If discovery reveals that the operating situation or the requirements of those affected are insufficiently understood, reconsider broader elicitation or scenario work against that missing result and its attainable contribution.

Discovery, design, trial, specialist inquiry, and consequence observation can overlap and reopen one another. A receiving decision needs the claims and evidence on which it relies. An observed encounter can support an account before personal identities are known; a claimed future consequence remains conditional on its path and conditions. Select any further inquiry separately from identifying that possible consequence.

SYSE.17:4.2 - Record the Result

FieldRequired content
focus and receiverProposed alternative or change; actual System or intended System referent and configuration to which it applies; use, scope, horizon, and receiving engineering decision.
examined situationsWork or events whose consequences bear on the decision.
bearer referencesActual bearers with the evidence and limits of identification; intended System referents for not-yet-present bearers; explicit unknowns where identity, boundary, or existence remains unresolved. Include a System-recognition basis when the consequence claim relies on that classification.
relations and modal pathsSupported obtaining relation occurrences; separately stated modal consequence-path claims; conditions, evidence, uncertainty, any selected probes, and missing-relation blockers.
consequence claimsChanged characteristic or condition, bearer, configuration, time, direction or magnitude cue, observed-or-modal status, evidence basis, uncertainty, and causal status.
value and specialist resultsWhen the decision uses a value judgement, state the grounds for the judgement, the value frame and its source, and any conflict. When it needs a specialist result, give that result and the limits of the specialist’s authority, or identify what is missing.
engineering decision contributionWhat supports, changes or holds open the receiving decision—for example, a constraint, alternative, probe, safeguard, monitoring condition, reversible step, refusal, escalation, an authorized representative or the need for one, or protection result.
residual and reopenMissing bearer references or modal paths and the concrete change that matters to a later receiving use. Include a further action only when its obtainable contribution warrants the complete inquiry burden.

An initial account can contain one qualified consequence and one named uncertainty—for example, an unidentified bearer, unsupported relation, or missing specialist result—when they matter to the choice. A bounded expert estimate can be usable when better evidence is not affordable, provided it meets the receiving decision’s evidence requirements. Label it as judgement with its basis and uncertainty rather than measurement or prevalence evidence.

SYSE.17:4.3 - What Changes in Practice

Visibility, influence, contracts and project roles can help identify possible bearers. When the decision may omit a material consequence, engineers trace the proposed alternative or change to the Systems that bear or could bear it, including bearers the existing list overlooks. They retain supported occurrences even when identities remain partly unknown. They distinguish obtaining relations from modal path claims and feed uncertain but material consequences back into decisions while change remains affordable.

SYSE.17:5 - Worked Cases

SYSE.17:5.1 - Quiet Consequence Bearers of a Heat-Pump Upgrade

The engineering-use account from SYSE.16 describes an existing heat-pump plant, a proposed controller, the next heating season, and the architecture decision. The team examines consequences of the proposed controller for Systems not captured by the original user-and-owner list:

Possible bearer and changeClaim and evidence statusEngineering decision contribution
Heat-pump plant: increased compressor cycling and wearThe current command relation obtains. Manufacturer data support a conditional wear estimate; the proposed configuration has not run for a heating season.Add a cycle-rate constraint and monitored-service condition.
Maintenance-provider organization: higher expected inspection workload and less remaining recovery capacityService records and the current agreement identify the provider organization and the maintenance Work it performs. The additional workload remains an estimate, and no current commitment covers it.Keep remote monitoring conditional; use SYSE.8 or SYSE.24 to settle provider capacity and commitment.
Maintenance technician: reduced cabinet clearance and greater exposure during inspectionCurrent geometry is described by drawings; the reduction under the proposed cabinet position remains unmeasured.Hold the cabinet-location choice open pending a plant-room measurement and specialist safety result.
Individual residents in a nearby building: increased low-frequency night noiseAn acoustic model supports a possible increase; no night measurement establishes an observed effect or its distribution among residents.Retain a low-noise alternative and the conditional noise/distribution claim; a stronger release claim needs its applicable acoustic basis. The model settles neither legal compliance nor ethical acceptability.
Individual building occupants: room-temperature deviation during grid load shiftingCurrent thermal relations are supported, but sensor latency, override behaviour, and the distribution of deviations among occupants remain unresolved.Retain an override-safe concept branch and the latency limit; select a trial when its obtainable result warrants the burden for the decision.
Electricity-distribution System: changed peak-load contributionMeter history supports the baseline; the proposed controller effect is simulated.Keep the grid-response claim conditional; commission measurement only when its obtainable contribution warrants the work.

Each row links a possible or observed change to a named System and supports only the stated consequence and decision contribution. Ground any authority or representation used later with separate evidence. The team can make a bounded architecture choice using these qualified contributions while keeping measurement gaps explicit. For example, suppose a plant-room measurement and competent safety interpretation are available before layout freeze; their combined result could rule out an unsafe irreversible placement at a burden justified by that gain. Select that acquisition. An unavailable seasonal noise study is a different proposal: retain the low-noise alternative and the conditional noise claim without making the study a condition of this narrower return. The account does not authorize release or establish that the proposed change has produced an improvement.

SYSE.17:5.2 - Observed Pedestrians and a Not-Yet-Installed Locker

A team must decide tomorrow whether to fix the geometry of an east-side delivery-cart route across an existing public footpath. Its participant list names the operator, supplier, and customer. Video shows people crossing between 07:30 and 08:00, but their names are unknown. A maintenance log records a van using the loading bay at 07:45. The proposed locker has not been built or installed, and the carts have not operated there. A simulation predicts short cart queues near the proposed locker; a west-side route is only a sketch.

The people and van were actual participants in the recorded events. Their presence identifies a footpath and access use that the engineering decision must retain, without requiring personal names. Possible obstruction or delay from future carts remains a modal consequence. For the not-yet-built locker, retain an intended System referent: a claim that queues could impede its replenishment depends on its eventual position and operation. Neither the observations nor the simulation establish that future interaction as an obtaining relation. No claim here depends on recognizing the pedestrians as one collective System.

The account now connects two missing consequences to the layout decision: preserve pedestrian and maintenance access, and examine the proposed replenishment access. It returns the observations, the conditional queue claim, and the unresolved geometry. These inputs do not yet rank the east and west alternatives or establish physical clearance. The team can compare a layout that preserves room for later access correction, if feasible, with deferring the irreversible geometry choice; operating approval remains a separate decision.

Suppose the only qualified engineer has 45 minutes before the decision. A proposed 30-minute geometry walkthrough is attainable only if access, preparation, and interpretation also fit that window. If entry requires a 70-minute induction, withdraw that proposal and return the qualified account already available. A larger inquiry is warranted only for a result the receiving decision needs: for example, elicitation if footpath-priority requirements remain unsettled, or scenario development if replenishment and crossing arrangements are not yet defined. Those results may expose further bearers and revise the layout alternatives; they do not replace the missing physical-clearance evidence. If an existing qualified geometry and access account settles the narrow choice, use it directly.

When the full pattern is unnecessary. If the available account answers the decision at its required scope and strength, return that answer. If one identified causal claim about one identified System is the whole question, use C.28 and the direct subject pattern.

SYSE.17:6 - Bias Annotation

Trace consequences from proposed engineering alternatives and changes rather than institutional visibility. Quiet or unidentified people can bear consequences. Preserve their supported involvement without inventing preferences, representatives, or agreement.

Use affordable evidence. A bounded expert estimate, simulation, or modal path claim can justify a reversible probe; an observed-effect claim needs observation. Include any actual System or intended System referent whose qualified consequence can change the decision; specialist authority remains with the applicable practice.

SYSE.17:7 - Conformance Checklist

  • One proposed alternative or change, its actual System or intended System referent, configuration, use, horizon, and receiving decision are stated.
  • Bearers are found by tracing the proposed alternative or change. Observed participants remain actual when personal identity is unknown; not-yet-present bearers remain intended referents in modal claims.
  • Unknown identity, boundary, or existence is explicit where it matters. System recognition is performed when the consequence claim relies on that classification.
  • Supported obtaining relation occurrences remain distinct from modal consequence-path claims and missing-relation blockers.
  • Every affected-System claim states the qualified consequence and bearer; every further relation used by the decision is grounded separately.
  • Every material claim states bearer, changed characteristic or condition, configuration, time, evidence, uncertainty, and causal status.
  • Every value-qualified consequence names its bearer and value frame, and any conflict remains explicit.
  • Each retained consequence supports, changes or holds open an engineering choice through a named decision contribution.
  • The account retains the residual uncertainty and reopen condition needed by its recipient. Further inquiry is selected for attainable value against its whole burden, including the combined programme.

SYSE.17:8 - Common Failures and Repairs

These recurring failures hide a bearer, relation, claim status, or decision contribution:

FailureRepair
Only purchasers, owners, formal roles, or influential participants appearTrace the proposed alternative or change outward and challenge the current boundary.
An affected-System claim is read as a project roleState the System and consequence; add a role or assignment only when that separate relation obtains.
A System is ignored because it cannot objectDiscover bearers from possible consequences, whether or not they can object or are represented in project governance.
A diagram arrow becomes an actual relationKeep the represented relation conditional until its occurrences and conditions are supported.
Scale labels become a System hierarchyRecover actual Systems and the relations used to organize them; a scale label is only a search cue.
Every mentioned party is called affectedRequire a decision-relevant possible or observed change under stated conditions.
Consequence list becomes an ethical verdictSend actual value conflicts and authority questions to their governing practices.
Simulation becomes causal proofUse C.28 and retain the narrower supported claim.
Inquiry produces no usable result until definitive research existsUse a bounded expert estimate or uncertainty claim when it improves a reversible choice.
An unidentified observed person becomes an intended future bearerPreserve the observed occurrence and the identity gap; qualify the possible future consequence separately.

SYSE.17:9 - Consequences

Engineers can compare benefits to visible participants with consequences borne elsewhere. Quiet and future bearers enter through qualified consequence claims. Those claims can change the decision through, for example, a probe, safeguard, specialist result, monitoring condition, or unresolved decision need.

Examining possible consequences and maintaining an account of uncertain claims take time and resources. Retain a bearer or possible path if its consequence supports or could change the decision, affects what evidence or probe is needed, or changes when to reconsider the choice.

SYSE.17:10 - Rationale

A.1.CSD supplies the transdisciplinary discovery action. Systems Engineering adds a recurring subject-specific move: start from a proposed System, configuration, or use change, examine physical and operational consequences, and connect qualified claims to the engineering decision that can still change the choice.

Questions that need specialist authority remain with the applicable practice.

SYSE.17:11 - SoTA and Source Use

The practice question is how much consequence discovery an engineering choice needs when the visible participant list may omit those who bear its effects. Three approaches answer different missing questions:

ApproachUse whenResult and tradeoff
Use an adequate existing accountIts bearers, configuration, use, horizon, and evidence answer the current decision.Reuse the qualified answer. Its scope must still fit the choice; a familiar participant list alone is insufficient.
Bounded consequence discovery in this patternA possible omitted bearer or consequence could change a named engineering choice, while enough is known about the alternative and use to trace that consequence.Return supported occurrences, modal paths, and a decision contribution or explicit gap. Accept residual uncertainty without claiming complete preferences, representation, or operating scenarios.
Broader stakeholder elicitation and operational-scenario developmentRequirements, conflicting expectations, agreement, or the way an operation would work are themselves missing inputs.Develop those inputs and revisit the consequence account. The broader work can expose alternatives and consequences that a narrow trace misses; its access, participant effort, and delay must be justified for the receiving decision.

NASA’s Stakeholder Expectations Definition, especially §§4.1.1.2.1–4.1.1.2.4, connects stakeholder identification and elicitation with expectations, agreement, and nominal and off-nominal operational scenarios. Adopt its attention to affected participants and operating situations. Adapt that broader practice to the present question: stop with a sufficient bounded answer when it settles the engineering use, and request elicitation or scenario development when that is the missing result. Consequence tracing cannot establish someone’s preference or agreement.

A.1.CSD supplies the discovery and claim distinctions: actual occurrences, intended future referents, and unresolved recognition questions remain separate from modal consequences. This pattern adapts that move to configuration choices and physical and operational situations. A.15.9 and C.11.DUA govern acquiring further results: compare attainable decision contributions with the complete burden, including competing use of the same resources and decision window.

The research contributions qualify how the account is used. Volden and Welde distinguish delivery performance from outcomes and wider effects, with context-dependent indicators and valuations. Carry relevant valuation differences into step 6 before any aggregation selected for the decision. Williams et al. examine changing interpretations and continuing benefits in three public projects; use that contribution to reconsider beneficiaries and consequences when use changes, without assuming the same evolution in every project. Thabit, Sancino, and Mora synthesize public-administration work on representation and benefit distribution. Preserve those as distinct questions in step 6 and in any later authority claim; that review does not supply a complete engineering-harm discovery method.

Apply the comparison at entry and when deciding whether to continue discovery: a sufficient direct account can finish the use, a material bearer gap opens bounded discovery, and an unsettled operating situation can require broader work. In the cart case, the observations already restore omitted access uses; the unavailable walkthrough supplies no further result. Reopen only the affected claims when a new bearer, changed use, conflicting concern, required authority, or failed premise changes what the decision needs.

SYSE.17:12 - Relations

  • A.1.CSD supplies the general discovery move and bounded consequence account. This pattern adds engineering alternatives, configuration, physical and operational situations, decision contributions, and specialist interfaces.
  • SYSE.1 supplies the System and candidate boundary; SYSE.16 supplies use structures, other Systems, conditions, and unsupported assumptions. Equivalent qualified direct sources can be used without implying a temporal order.
  • A.1, A.14, B.1, B.1.2, and C.13 govern Systems, wholes, collections, delimitation, crossings, and constructive facts. Treat a scale word only as a cue until those objects and relations are grounded.
  • C.28 qualifies a causal-use claim. The Agent performing consequence-discovery Work applies this pattern to identify the Systems that may bear consequences and supplies the resulting account to the receiving engineering decision.
  • D.1–D.5 govern value frames, actual conflicts, mediation, and audits when those questions arise. An affected-System claim states the qualified consequence and bearer.
  • A compatible consequence account can inform SYSE.2, SYSE.8, SYSE.4, SYSE.6, SYSE.10, SYSE.14, and specialist practices. Each receiver rechecks focus, configuration, use, horizon, evidence, and authority.
  • Application profiles retain their own consequence-discovery Methods—for example, safety, security, medical, ecological, legal, economic, software, electrical, building, or transport specializations.

SYSE.17:End

SYSE.2 - Develop Linked Use and System Concepts

Status: Stable

SYSE.2:1 - Problem frame

Use this pattern when a project has selected an actual System, retained an intended System referent, or bounded another engineering subject, but the proposed concept cannot yet be defended through concrete use. The team may have, for example, an internal block diagram, requirement set, component list, product concept, or preferred technical solution while phrases such as environment, suprasystem, using system, Concept of Operations, use case, scenario, requirement, or user story stand in for several Systems, intended System referents, conditions, relations, and effects. A compatible SYSE.16 use-context account supplies decision-relevant operational structures, neighbours, conditions, and outside changes. A compatible SYSE.17 affected-system account supplies qualified consequence claims and identifies any bearers whose identity or existence remains unresolved. Use the claims that apply to this decision.

The result is a linked use-and-system concept proposal: bounded claim content that connects a concrete use situation with a candidate System concept and states any main uncertainty. One or more descriptions may carry the claims; no document form is required.

Link one concrete use claim to one candidate system-concept claim and state any main uncertainty. This is enough to expose a grounded architecture question. Add further content—for example, another use situation, structure, participant, failure, effect, or representation—only when it can change the candidate or its boundary.

If this link is missing, internal elegance can substitute for usefulness. A pump passes a component test but worsens downstream flooding; planning software is installed but cannot support production decisions with the available data; a retrofit design works in an empty building but cannot be realized while the building is occupied.

The payoff is a revisable account that keeps outside use connected to the concept for the selected subject. Evidence about use can change that concept, while architecture and realization findings can change the use, boundary, or affected-System claims.

Use this pattern while a concrete use claim and a candidate System concept need to be developed together. Use C.30 and C.32 when the current question is grounded architecture and candidate synthesis, A.3.4 when the question is whether one actual bounded change occurred, and the applicable Operations Management pattern for continuing Work. Return to SYSE.1 when evidence changes which System should orient the project.

At the first consequential use of source wording, ask: does this claim connect the concept for the selected subject with a concrete use situation, participating or affected Systems, conditions, and outside effects? If yes, name those subjects and relations and use this pattern. A representation—for example, a ConOps, use case, scenario, requirement, user story, diagram, or model—presents some of these claims. Its form establishes neither their truth nor the required form for the proposal.

When the concrete use itself is disputed across participants, SYSE.54 supplies collaborative event modelling to recover behaviour and its consequential alternatives. Bring its compatible account back to the linked concept here. Reuse a sufficient scenario directly.

SYSE.2:2 - Problem

A project-system choice does not determine the useful boundary or organization of the selected actual System or intended referent. The same desired effect can be achieved through different actual or proposed changes—for example, changes to the designated System, an external System, an interface, a Work arrangement, or several sides together. A containing System may matter, but parthood must be established directly. Use, interaction, placement, ownership, authority, affectedness, and shared environment are other relation kinds and require their own grounds.

One-way handoffs make this worse. A supposedly complete use description is handed to concept development, then architecture or realization discovers that the use cannot be supported. Conversely, one attractive technical concept narrows the use description until only its successes remain visible. The recurring engineering problem is to develop the use claims and system concepts together while preserving the distinctions needed to return a failed claim.

SYSE.2:3 - Forces

ForceTension
Outside effect and project boundaryUse justifies the System concept, while the useful change may cross the assumed boundary.
Several environment Systems and one simple storyA compact scenario helps reasoning, while one hierarchy can hide non-nested participants and affected Systems.
Function and feasible bearerRequired functioning guides concept development, while a function word or diagram does not supply a bearer.
Working descriptions and physical groundingModels and scenarios keep claims inspectable, while their form does not establish use, transformation, architecture, or evidence.
Early usefulness and completenessOne linked claim can expose the next question, while a comprehensive form can add work that does not change that question.
Continuing revision and decision stabilityUse and concept claims must change with evidence, while each downstream architecture question needs a stated current basis.

SYSE.2:4 - Solution

SYSE.2:4.1 - Start with one decision-changing use situation

Take the immediate engineering subject and its receiving purpose from the project-system choice account, or identify that bounded subject directly when no SoI question remains. For a creator, retain the product-use grounds while developing the creator’s own use and System concepts. If that choice is needed but no compatible SYSE.1 account is available for the same subject and decision, use a qualified direct source for the focus claim or record the missing project-focus result and stop only the linked claim it blocks. A contributor can explore a linked proposal from a provisional focus. When its use depends on joint action, use SYSE.1:4.4.1 to establish the common referent and contribution connections for that action, or retain the unresolved coordination condition. For an actual System, describe an actual or possible-future situation in which it participates. For a not-yet-present referent, keep the intended participation in modal plan, decision or description content; do not report the intended System or participation as actual. State:

  1. the subject that relies on, uses, changes, or is affected by the proposal;
  2. the direct relation by which that subject enters the use;
  3. the condition or change expected;
  4. the outside effect that matters to the current decision; and
  5. any uncertainty that could change the concept.

Name the relying subject under the kind that applies to it. People and technical systems are familiar examples, and other kinds are admissible. State the direct relation by which it enters the use—for example, reliance, participation, performance of Work, or affectedness. Include affected Systems or intended System referents whenever their qualified consequence claims can change the decision; participation in or ownership of the designated System is not required.

SYSE.2:4.2 - Name the subjects and direct relations hidden by environment language

Start from compatible current SYSE.16 and SYSE.17 results for the same subject, configuration, use, horizon, and decision. If either result is unavailable, recover only the subjects and direct relations needed for the first linked claim. Use SYSE.16 when the decision needs several operational structures or a co-change boundary, and SYSE.17 when it needs active discovery of consequence-bearing Systems. A neighbouring System may matter, for example, through constructive parthood, placement, interface, interaction, causal participation, use, transformation, collection membership, assignment, ownership, permission, authority, or affectedness. Distinguish supported actual relations from those proposed for this use. Apply the FPF pattern that defines or constrains each claim.

Use A.1.SCR when the System status of a proposed participant or containing whole is unresolved. Use A.22 when the current question selects an organization among independently identified constituents and obtaining relations for a named use. Keep several non-nested structures when one decomposition would hide a relevant claim—for example, an interaction, control relation, affected System, or source-return condition.

Authority constrains who may change a System; it does not draw the System boundary. Ownership can matter to a decision without establishing containment. A containing whole matters when its actual or proposed proper-part relations and whole-level consequences change the use or concept. Distinguish supported actual relations from proposed relations and qualified predictions; a future whole need not already exist for its proposed arrangement to affect the concept.

SYSE.2:4.3 - Develop the use claim and candidate system concept together

Write one outside-facing use claim and one inside-facing concept claim:

Linked use-and-system concept proposal:
  concrete use claim:
  candidate system-concept claim:
  main uncertainty, if any:
  architecture question exposed:
  reopen condition:

Use any readable form for this content. The use claim names participating or affected Systems, conditions, expected transformations or behavior, and outside effects only as far as the current decision needs. The system-concept claim names what the proposed concept needs—for example, a boundary, functioning, interface, resource, constraint, or placement—while leaving full architecture selection open.

When an available construction starts the inquiry, ask who could use it, in what situation, and for what outside effect. Follow one consequential behaviour path from the triggering change through the participating Systems to that effect. Try the condition most likely to defeat the proposal. Use the resulting success or failure to revise the functioning, bearer, interface or use claim that made the difference. Expand the path only when another condition could change the concept.

Use A.6.F when function-like wording carries a claim. Name the required functioning and its proposed bearer. Any remaining question—for example, about function, capability, Method, Work, module, interface, evidence, or architecture—stays under the pattern that defines or constrains it. Use A.6.M only when a module or interface claim is current. If no feasible bearer can support required functioning, revise the concept or use claim before admitting an architecture candidate.

Use A.3.4 for an actual observed transformation only after the continuing subject, boundaries, before/during/after facts, and continuity rule are available. A required, intended, or simulated transformation remains modal claim content; its description does not establish that the change occurred.

A functional or transformation-flow description of relevant environment structure can support the linked proposal by showing selected functioning or flow relations for a named use. The proposal also states which use situation matters, which Systems participate or are affected, which outside effect changes the decision, which candidate System concept is being considered, and any uncertainty that matters to the decision. Model only the environment structure needed by those claims.

SYSE.2:4.4 - Compare changes on either side of the boundary

Develop alternatives when changing a different subject would change the engineering answer. Compare, for example:

  • an actual or proposed change to the designated System;
  • a change to an external System or operating arrangement;
  • a changed interface, placement, or resource relation; or
  • coordinated changes on several sides.

Use a compatible SYSE.8 provider-arrangement account when its supported claims or design constraints change the use, candidate System or intended referent, boundary, interfaces, realization needs, or evidence. Without a compatible current SYSE.8 account, use a qualified direct source for the needed provider-arrangement claim or record the missing result and stop only the linked claim it blocks. Either account may need revision when a shared claim changes; that dependency does not prescribe the order of engineering Work. Obtain other decision-changing results from the specialist practice that owns them—for example, organization change, Operations Management, Platform Engineering, Governance, safety, security, ethics, law, or finance. Keep each result claim linked to the use or concept claim that depends on it.

For example, when source material names a product-service system, digital twin, digital thread, MBSE, PDM, PLM, eXperience platform, or Multi-D arrangement, recover the actual contribution before using the umbrella term. A concrete contribution—for example, a maintained model, configuration relation, simulation, observation return, integration capability, or change decision—can enter the linked proposal through its direct claim. The umbrella name alone does not decide whether this pattern, architecturing, realization, assurance, or a specialist practice is the next use.

SYSE.2:4.5 - Expand only when another claim can change the candidate

The first result is one linked use claim, one candidate concept claim, and any main uncertainty. Reuse an adequate scenario or use-case slice as the proposal: retain its compatible use and concept claims and add only the missing relation, consequence or uncertainty needed for this decision. The progressive-slice comparison in §11 helps choose when to continue toward implemented, tested behaviour.

Expand when further content could change the candidate. Examples include another use situation, load, failure, participant, affected System, harm, benefit or representation. Add the relevant:

  • environment structures and obtaining relations;
  • transformations, interactions, conditions, and effects;
  • functioning, interface, placement, resource, and constraint claims;
  • correspondence between a representation and the represented claims;
  • alternatives, assumptions, evidence limits, and specialist returns.

If source words such as operational system, system in operation, operations, or operational flow are current, distinguish two questions. Use this pattern for a System’s participation in use and the concept that supports it. Use Operations Management when the difficulty is managing continuing Work, queues, policies, or flows.

SYSE.2:4.6 - Stop at a grounded architecture question and reopen from failed support

Stop when the current use claim and candidate concept expose a grounded architecture question and any uncertainty carried into it. The linked proposal supplies required functioning, operating conditions, outside effects, decision-relevant environment structures, assumptions, and evidence limits to C.30 and C.32.

Use C.30.ASV only when a structural description and its adequacy for a selected architecture use are current.

Reopen the affected linked claims when:

  • the use claim and concept claim no longer support each other;
  • a candidate architecture lacks a feasible bearer or hides a harmful effect;
  • realization evidence defeats an interface, resource, placement, or capability assumption;
  • operating observation changes a condition or effect; or
  • a specialist result changes permission, feasibility, harm, value, or the participating Work arrangement.

Return to SYSE.1 when the failed claim changes the immediate engineering subject or the product and use grounds. Distinguish those returns: a changed local scope can preserve the product SoI.

SYSE.2:5 - Archetypal Grounding

SYSE.2:5.1 - Pumping station under flood risk

In the preceding SYSE.1 use, the engineer retains the intended referent PumpingStation-P1 in decision content and records downstream exposure as unresolved. No actual PumpingStation-P1 exists yet. The first linked proposal says:

use claim: the intended referent would move water under the selected flood load without unacceptable downstream harm
system-concept claim: the description assigns pumping, positioning, power, control, and discharge functioning to the intended station referent
main uncertainty: downstream conditions may make the proposed discharge harmful
architecture question: which selected structures and possible bearers could support the claim

This is enough to use C.30 and C.32. A component pump test can contribute evidence about an actual bearer, but it establishes neither the not-yet-present station nor its outside effect. The engineer uses downstream-harm evidence to revise the use claim. The project-system choice reopens only if the station referent no longer supports the project decision.

SYSE.2:5.2 - Manufacturer’s ERP-enabled planning change

An available construction starts this concept question: deployed ERP-Runtime-E3 offers automatic rescheduling when an order date changes. The manufacturer considers using that facility to revise production commitments. Its usefulness depends on what the planners would receive and could act on.

The manufacturer keeps PlanningSystem-P1 as the intended creator being engineered; actual System identity remains unestablished. As in SYSE.1:5.2, the product SoIs remain the water-supply and irrigation installations in their intended uses. The planning capability must support their different orders and commitments with shared production resources. Actual person Systems Planner-A and Planner-B perform PlanningWork-PW1. They use ERP-Runtime-E3 and demand, capacity, material, and production-order records as resources and evidence. The records are epistemes; PlanningAPI-PA2 and the user interface are separately identified interfaces. The common-focus exchange in SYSE.1:5.2 has made the missing stock-information contribution visible.

The first linked proposal lets the software reschedule a moved order and release the revised production commitment. Its use claim is that the planners could promise the earlier date from the resulting plan; its main assumption is that the runtime’s material and capacity information supports that commitment.

Follow the proposed behaviour. When an order needs six units, ten are recorded and available, and the needed capacity is available, the proposed schedule has support for those constraints. Now try a failure path: the imported record still shows ten unreserved units, but eight have since been allocated elsewhere. The moved order needs six, while only two remain unreserved. A successful date recalculation leaves the proposed commitment unsupported. The plan can still serve as a proposal while the planners seek current stock information.

Revise the linked concept. Required functioning becomes proposing a schedule, obtaining current material and capacity confirmation and any needed reservation, and holding commitment when that support is missing. One proposed allocation gives ERP-Runtime-E3 schedule proposal and an explicit unconfirmed state; Planner-A obtains the needed confirmation and reservations, and Planner-B makes the commitment decision under the applicable authority. This changes the bearer proposal from software alone to a coordinated use of the runtime and people. Their proposed organization has to satisfy the System criterion for PlanningSystem-P1; a list of participants and records does not establish that composite.

The resulting C.32 question is which arrangement can support that functioning before the required commitment time. Use SYSE.5 to develop and compare event-fed information with reservation interfaces against provisional software plans with human confirmation and a hold on unsupported commitments. Compare latency, available contributions and the burden of exceptions as well as normal use. The concept now gives that comparison a specific function, possible bearers, failure path and uncertainty; it does not select a finished architecture.

If confirmation cannot arrive in time, return to the timing claim or proposed allocation. If the required stock-control contribution or authority cannot be obtained, hold the commitment relying on it and revisit the affected concept claims or choice of the immediate engineering subject. Reopen the product SoI designation only when its product or use grounds change; a failed local arrangement or new contract alone does not make the planning creator the SoI.

The independent ERP supplier can select its software product as its own SoI on the usable supply, decision and acceptance grounds in SYSE.1:5.2. The manufacturer’s planning project can close its agreed capability result through representative order changes and operating conditions. Software installation or an organization chart alone does not establish that capability or the existence of the composite PlanningSystem-P1. Its System identity, qualified capability and later product consequences require their respective evidence; local acceptance need not wait for every later product outcome.

SYSE.2:5.3 - Occupied building heat-pump control

For HeatPumpPlant-HP1, ControllerConfig-C2, the next heating season, and ArchitectureDecision-AD1, the three compatible input accounts use the same subject, configuration, use, horizon, evidence window, and receiving decision:

  • the SYSE.16 use-context account states the BuildingHeatingSystem-BH1 proper-part claim, energy and information transfers, plant-room access permission, and unsupported latency, override, insulation, and clearance assumptions;
  • the SYSE.17 affected-system account supplies the qualified AcousticResult-AR4, SafetyResult-SR7, ThermalResult-TR5, and their authority boundaries, including the unmeasured neighbour-noise and cabinet- clearance branches; and
  • the SYSE.8 provider-arrangement account supplies only the supported provider claims and design constraints: actual provider System MaintenanceTeam-MT4, the current access permission, expected diagnostic Work, the communications bearer, and the missing commitment and authority result for remote monitoring.

The three accounts change the linked proposal as follows:

use claim: occupied rooms remain within the selected thermal range while qualified neighbour-noise and maintenance-access constraints hold
system-concept claim: ControllerConfig-C2 includes a cycle-rate limit, a low-noise branch, a measurable cabinet-location alternative, and a latency-tested override-safe branch
main uncertainty: night acoustic measurement and plant-room clearance are unavailable; remote-monitoring authority and commitment are unresolved
architecture question: which controller, sensor, cabinet, communications, and operating structures support those qualified claims
reopen condition: a specialist result, measurement, provider result, or operating observation defeats one of the linked claims

The remote-monitoring branch remains conditional because the provider-authority and commitment result is unavailable. Realization and WorkPlan descriptions may include cabinet relocation, access preparation, and test Work. Keep those realization and WorkPlan descriptions distinct from the System concept. If no feasible architecture supports the linked claims, revise this proposal. Reopen SYSE.1 only if the failure changes the project focus.

SYSE.2:6 - Biases to Watch

Two recurring biases matter here. Representation lock-in treats a familiar use-model form as the use itself; recover the represented Systems, relations, conditions, and effects. Concept lock-in narrows use until the preferred concept always succeeds; keep the use claim open to revision and return evidence to whichever use or concept claim it challenges.

SYSE.2:7 - Conformance Checklist

IDRequirement
CC-SYSE2-1A conforming use SHALL name one concrete use situation, one candidate system-concept claim, and any main uncertainty before requesting fuller documentation.
CC-SYSE2-2It SHALL name the participating and affected subjects and SHALL state each decision-changing relation through the applicable FPF pattern.
CC-SYSE2-3It SHALL distinguish parthood, placement, interaction, use, ownership, authority, and affectedness when more than one is current.
CC-SYSE2-4Function-like wording SHALL identify the required functioning and proposed bearer through A.6.F before architecture use relies on it.
CC-SYSE2-5Required or intended transformations SHALL remain modal claims; an actual transformation claim SHALL satisfy A.3.4.
CC-SYSE2-6A ConOps, use case, scenario, requirement, model, diagram, or other representation SHALL remain distinct from the linked claims it presents.
CC-SYSE2-7Conditional expansion SHALL add only information that can change the current concept, architecture question, evidence use, or return.
CC-SYSE2-8The stop SHALL expose a grounded C.30 or C.32 question and any uncertainty carried into it.
CC-SYSE2-9When architecture, realization, observation, or specialist evidence challenges a claim, that evidence SHALL return to the use, concept, or project-focus claims it can change.

SYSE.2:8 - Common Anti-Patterns and How to Avoid Them

Anti-patternWorking symptomRepair
Environment-as-containerOne box called environment, owner, or suprasystem is assumed to contain every relevant System.Name the participating and affected Systems and the direct relation by which each changes the decision.
Representation lock-inA ConOps, use-case, SysML, FAS, requirements, or story format is required before the working question is known.Start from one linked claim and choose representations only for the use they improve.
Concept-as-finished-architectureAn internal concept diagram is treated as the selected architecture and other structures disappear.Stop this pattern at the grounded architecture question; use C.30 and C.32 for architecture relations, selected structures, and candidates.
Fixed outside worldExternal Systems and Work arrangements are treated as fixed while only the designated System or its intended design may change.Compare actual or proposed changes to the designated System, an external System, their relations, or several subjects; obtain specialist results where needed.
Test-as-benefitOne component or integration test is used as proof of outside use, benefit, acceptance, or complete assurance.State which claim the evidence can support, its conditions, and which use or concept claim remains open.

SYSE.2:9 - Consequences

The project can ask architecture questions from a concrete outside-use basis without waiting for a complete requirements package. It can compare changes across the assumed boundary, preserve non-nested environment structures, and return evidence to the claim it can change.

The cost is ongoing concept maintenance. A use claim, System concept and representation can diverge as new evidence arrives. Keep each description connected to the use or concept it represents, and revise or retire it when that connection no longer holds.

SYSE.2:10 - Rationale

A System concept becomes useful to an engineering decision through concrete relations with other Systems and conditions, while a chosen containing whole or representation can omit a consequential relation. Linking use and System concepts makes the outside reason and inside proposal inspectable while leaving architecture selection to the applicable FPF patterns.

One use claim linked to one concept claim can reveal a missing bearer, harmful effect, or misplaced boundary. Fuller descriptions are justified by decisions they can change, not by a prescribed documentation sequence.

SYSE.2:11 - SoTA-Echoing

The practice question is how much use description is needed to change the concept or expose the next architecture question. The selected approach develops a small linked proposal with progressive behavioural detail. Existing scenarios and slices can supply that content directly.

Current practice lineWhat changes in this patternSource and useAdoption status
Current use-case practice starts from user goals, admits human and nonhuman participants and failure paths, and revises end-to-end slices as work proceeds. Model-based system-architecture practice connects use cases to candidate functional groupings and interfaces.Start from a concrete use situation. As the use and the candidate System concept change, show how participants’ behaviour on success and failure paths connects the proposed use to the candidate concept.Jacobson et al., Use-Case 3.0: The Definitive Guide — Refreshed (2024); Weilkiens et al., Model-Based System Architecture, 2nd ed. (2022). These are provider and textbook Methods, not comparative proof of one universal sequence.Adopt and adapt. Use revisable slices and explicit links to candidate functioning; choose the representation form for the receiving engineering decision.
Agile and continuing requirements research treats models, requirements, traceability, monitoring, and compliance links as maintained parts of changing work rather than one frozen preliminary package.The linked proposal stays revisable, and representations are chosen for the decision and maintained only while they continue to carry useful claims.Liebel and Knauss, Aspects of modelling requirements in very-large agile systems engineering (2023; author preprint), report one Ericsson case, including model-maintenance and tool trade-offs. SYSE.19:11 gives the distinct source scopes and references for Hernández, Moros and Nicolás (2023), Norheim et al. (2024), and Kosenkov et al. (2025): DevOps requirements management, LLM requirements tasks, and regulatory compliance.Adapt. Maintain useful claims and choose representations by use; let the receiving project determine how requirements Work is organized.
Product-service system and servitization research treats useful offerings as configurations of products, service Work, provider and customer relations, capabilities, operations, digital support, and consequences. Reported performance is mixed and configuration-dependent.The Solution compares actual or proposed changes to the designated System, external Systems, interfaces, and Work arrangements and asks for the specialist results that make those alternatives credible.Brambila-Macias, Sakao and Kowalkowski (2018), Braga Junior, de Toledo and González (2020), Kim (2020), Brax et al. (2021), Åkesson et al. (2024), Menon et al. (2024), and Zhao et al. (2025). SYSE.8:11 develops the bounded offering/provider comparison.Adapt. Use the cross-boundary design pressure; establish each System, Work, provider relation, Method, and consequence directly in the receiving project.

A serious alternative is a progressive use-case slice following the Use-Case 3.0 guide. It starts with a user goal and can grow from a sketch through selected normal and failure paths toward a testable increment. It need not enumerate all scenarios before useful work starts.

Compare the two on the same moved-order facts in §5.2, including the stale stock record. A small slice for rescheduling an order can reveal the unsupported commitment and supply a failure path that holds it. The linked proposal should reveal the same failure. Its selected next result is the architecture question: which functioning, people, runtime and interfaces could support a commitment under the stated conditions? An adequate slice can supply those claims directly.

The trade-off depends on the next result. This linked proposal leaves implementation and path-specific acceptance tests unprovided while the bearer and interface choices remain open. Progressive slice practice supplies the route toward implemented, tested behaviour when that is needed. Neither representation earns a general effort advantage from being called small. In the ERP case, the proposed confirmation and reservation arrangements still need comparison, so §§4.3–4.6 return the functional and bearer question to C.32 and SYSE.5; a later testable slice can use that result.

Reopen the choice of a thin linked proposal when it appears coherent but a consequential path changes the functioning or bearer—for example, when another order consumes the promised stock between proposal and commitment. Add the missing path or use the progressive slice directly. Prefer an available scenario treatment when it supplies the required architecture claims with less reconstruction or maintenance. These are selection conditions, not evidence that one description form has superior project outcomes.

These current lines support continuing, use-led, model-linked revision in the settings examined. This pattern connects a use situation, subjects and relations, qualified consequences and a candidate concept, using compatible SYSE.16, SYSE.17 and SYSE.8 results. Relate evidence to the claim it can change. Assess transfer to another setting against the receiving use, Systems, relations and evidence.

SYSE.2:12 - Relations

  • A SYSE.1 account can supply the immediate engineering subject, its relation to the product SoI, current reason, boundary question, alternatives and reopening condition. Use the subject of the present concept question; developing a creator’s concept retains the product grounds. Return a changed local subject or product purpose to the corresponding choice.
  • A compatible SYSE.16 result supplies selected operational structures, conditions, and unsupported assumptions; a compatible SYSE.17 result supplies qualified consequence claims and unresolved representation or protection needs; a compatible SYSE.8 account supplies only its supported provider-arrangement claims and design constraints. Use each result only for a compatible subject, configuration, use, horizon, evidence window, and decision. These relations do not prescribe an order of engineering Work.
  • Use A.3.4 for the identity and boundary test of an actual bounded transformation. Intended, required, and simulated transformations remain claims or representations until that test applies.
  • Use A.6.F to recover the object or claim meant by function-like wording and select the direct subject pattern. Use A.6.M only when a module or interface claim is current.
  • Use A.22 for selected-structure identity in decision-relevant environment structures. Use C.30.ASV for structural-view adequacy only when a description is relied on for a selected architecture use.
  • The linked use-and-system concept proposal supplies functioning, operating conditions, outside effects, selected environment structures, assumptions, and evidence limits to the architecture question. C.30 defines grounded architecture claims and relations; C.32 guides candidate synthesis over selected structures. SYSE.5 develops the engineering functional and bearer alternatives, their allocations, interfaces and feasibility limits from those compatible claims.
  • Architecture, realization, operation, or assurance evidence returns to the affected linked claims it can change. Practitioners in organization change, Operations Management, Platform Engineering, Governance, safety, security, ethics, law, finance, and other specialist practices keep their Methods and supply only the results used in the linked proposal.

SYSE.2:End

SYSE.54 - Make Domain Behaviour Explicit Together with EventStorming

Type: Method Status: Stable Normativity: Guidance for collaborative domain modelling in an engineering undertaking; constructed cases do not establish observed system behaviour.

SYSE.54:1 - Problem frame

Use this pattern when people involved in the same service or product describe incompatible accounts of what happens, why it happens and what should happen next. An equipment dispatcher sees a confirmed booking, maintenance sees an unavailable kit, and a software developer sees an updated row. An engineering team needs the shared behaviour and its unresolved conditions before it can improve the use or design its support.

The first useful result is a jointly corrected domain model: meaningful events, the decisions and actions connecting them, relevant state, disagreements and examples that can change the proposed behaviour. It can support an existing-process investigation or a proposed design. Identify which one is being discussed and keep observed facts, participant reports and proposed rules distinguishable.

Begin with the concrete difficulty and people who know different parts of it. Let each contribute a few significant occurrences in ordinary domain language. Ask what happened, to which case or object, and why that matters. Organize and test the explanation together before choosing software boundaries.

This is EventStorming applied to engineering understanding and design of domain behaviour. Its surrounding practice includes organizational discovery and professional facilitation; this pattern develops a bounded route from exploration to a usable process account and, when needed, software-design questions. It assumes access to people with relevant domain experience and a facilitator able to keep dissent visible. For a sensitive or politically constrained inquiry, obtain suitable facilitation and safe participation; a board filled by people unable to contradict the official account is a poor basis for reliance.

Use an adequate existing account directly. When one actor’s interaction and expected result are understood, SYSE.2 and its use-case treatment can suffice. For a few unknown rules in one interaction, you can clarify those rules and examples in a focused discussion. The wider practices of Domain-Driven Design, business transformation and facilitation extend beyond this treatment.

SYSE.54:2 - Problem

Knowledge is distributed across people and systems. Each local account may be reasonable while their combination omits a waiting period, failed request, external decision or conflicting meaning of “complete”. A requirements list can hide these relations; one expert’s process diagram can make everyone else’s exceptions look like mistakes. Choosing tables or services at this point embeds an unexamined account.

A shared event wall makes differences discussable, but agreement and visual order can create false confidence. “After” may be mistaken for “because”; a request may be mistaken for success; a desired occurrence may be reported as observed. The task is to construct and challenge an explanation useful for the receiving design, not merely to arrange coloured notes or produce a comprehensive diagram.

SYSE.54:3 - Forces

  • Broad participation exposes missing behaviour, while too much scope prevents a usable explanation.
  • Loose initial language lets different perspectives emerge; a design commitment requires enough precision to distinguish actions, conditions and outcomes.
  • A typical path gives people something to discuss; consequential alternatives can defeat that path.
  • A common timeline helps coordination, while concurrent work and negotiation do not have one fixed order.
  • Software boundaries can clarify consistency and responsibility, while premature technical partitioning can silence the domain questions that should determine those boundaries.
  • Collective understanding has value even without a polished artifact. A later user needs a recoverable account of the distinctions and decisions on which the engineering work relies.

SYSE.54:4 - Solution

Choose the extent of modelling from the receiving question. For broad discovery, reconcile the event account enough to locate consequential disagreements and select a useful inquiry. For a selected process, develop the connecting causes and decisions, then challenge the flow with a variation that could change the design. Add software structures only when they answer a current implementation question. The following operations can repeat as the account changes; the selected depth determines which are needed now.

SYSE.54:4.1 - Choose the purpose and prepare participation

Distinguish three useful depths. Big Picture explores a broad domain or business line to find conflicting accounts and important areas for inquiry. Process Modelling develops a selected behaviour, including its alternative outcomes and people’s decisions. Software Design asks how supporting software can preserve that behaviour through state, consistency and interface boundaries. They can be used independently. A broad workshop need not finish with services; a small design session need not repeat a broad exploration.

State the practical question and initial scope, the current or proposed situation, and the decision or learning that would make the session useful. Invite the people who know the consequential perspectives, including those handling exceptions or receiving the result. A representative cannot fill an unknown fact by agreement. Record the missing perspective and obtain it before relying on the affected claim. Arrange a shared surface that everyone can read and change. Physical notes and an accessible digital board are alternatives. Check that remote participants can add and correct the account themselves.

Use a simple visible legend. Introduce events first; add another notation only when the discussion needs its distinction. Labels as well as colour carry meaning. Agree how disagreements will be marked and revisited. Start with the terms the discussion needs. The facilitator keeps the question in view and helps everyone participate, including those who disagree. Domain participants describe and challenge the behaviour. If a design decision follows, identify who makes it and under what authority.

SYSE.54:4.2 - Recover events and reconcile the stories

Collect significant domain events in past-tense language, such as “kit collected” or “inspection failed”. Participants can initially contribute in parallel when an official story may be incomplete. For each ambiguous note, ask which occurrence it means and who would notice a consequential difference. “Process booking” names an activity; “booking recorded” names an occurrence; “booking is active” names a state that can persist. Preserve separate interpretations until examples show whether they are the same.

Arrange events in a plausible temporal account. Use separate lanes for cases or simultaneous threads when needed. Fix gross differences of granularity: a whole service completion and a keystroke do not explain the same level of behaviour. Keep the level that exposes the working difficulty, allowing a detailed local branch where it matters. Mark a hot spot for a disputed rule, missing link, risk or unanswered question. Attach it to the affected behaviour so that it can be investigated, rather than collecting detached worries.

Walk through the account aloud with a narrator and participants who can correct it. Ask where a thread starts, what interrupts it, what counts as a useful or failed ending, and what happens beyond the initial scope. Follow a troublesome result backwards to its required conditions, then forwards again. Add the surrounding event or participant when the initial boundary hid a cause or consequence. Agreement after this walkthrough establishes a jointly corrected account. For a claim about what happens in practice, use observations that support that claim.

SYSE.54:4.3 - Explain decisions and changing state

For a selected flow, identify who uses which information to request an action, to whom they send the request, and who is responsible for responding. The request can be accepted, rejected or remain unresolved. An event note states the claimed outcome. Establish the occurrence separately when the receiving claim requires evidence. A subsequent decision may initiate another action under a rule. Ask who makes that decision, with what information, under which condition, and when. Human judgement and automatic rules can both occur; a drawn rule does not supply authority to act.

ElementQuestion that makes it usefulDistinction to preserve
Domain eventWhat consequential occurrence has happened in this account? To which case or object?Distinguish the report from the occurrence and qualify the occurrence claim. A future scenario can propose the occurrence.
Command or action requestWho asks whom to do what, and what permits or prevents acceptance?Requesting a booking is not successful booking. A command is not the reusable Method of carrying out the work.
Decision rule or policyOn this event, under these conditions, what should be done next and by whom?“Whenever” needs its exceptions and timing. Temporal order alone establishes neither a decision rule nor a causal connection.
Information used for a decision, often called a read modelWhat information must be available to whoever makes the decision, where does it come from, and can it be stale?A display of availability may differ from the state used to accept a reservation.
State-bearing domain object or systemWhat changes, which identity continues, and what must remain true?The event “hold expired” differs from the interval during which a hold is active.
External participant or time conditionWhat can happen without this team’s command, and how is it noticed?For a supplier refusal, identify how notice reaches the responsible participant and how they respond. For a deadline, identify how expiry is detected and acted on.

Connect an event to a next action only after stating the rule or physical dependency that warrants the connection. Ask whether it happens always, immediately, only on working days or only after additional information. A payment notification, for example, may report something already done elsewhere rather than perform it here. For uncertain external behaviour, show the waiting and failure outcome instead of drawing an assured success.

Track one object through the relevant events to expose illegal transitions and missing information. For concurrent requests, ask what must be decided together. When exploring software, an aggregate can be a candidate consistency boundary around domain objects whose invariant one operation must preserve. Derive that boundary from behaviour and invariants; it is not a synonym for any important project subject or alpha. A bounded context bounds a particular model and its language. Neither it nor an aggregate determines one service, one database or one team. Compare those architecture choices separately with SYSE.5 and SYSE.6.

Some parts of the domain are conversational: negotiation, diagnosis or design can revisit questions in many orders. Mark that region and the events or conditions allowing it to finish. Model consequential rules and the ordering constraints needed by the decision. If exact concurrency or temporal guarantees matter, return that question to an appropriate formal or specialist method; the workshop model does not prove them.

SYSE.54:4.4 - Challenge the account and produce a usable return

When developing a flow, first complete a simple meaningful path while retaining deferred objections as hot spots. Then choose a variation that could change the model: rejection, interruption, stale information, concurrent demand, external delay or an expired time condition. Use concrete identities and quantities where they expose the rule. Follow every selected branch to a stable result, an explicit waiting condition with its continuation, or a named unresolved question. If the variation defeats the baseline, change the baseline rather than adding exceptions indefinitely.

For behaviour that will be implemented, express decisive examples as initial state and information, triggering action or event, and expected observable outcome. Include a refused or delayed action where it matters. The group should be able to explain why the outcome follows and what would change it. The examples give candidate acceptance conditions. For a claim about implemented behaviour, use evidence from tests performed, observations of the system or qualification appropriate to that claim.

Resolve the hot spots that prevent the receiving use. An open question can go to a source able to answer it, with the decision it affects and the condition for continuing. The authority for a rule may have defined it already, or an operating record may show when a notification arrived. A blocking contradiction leaves the flow in dispute. An exploratory session can preserve what the participants learned and choose a bounded investigation where one is needed.

Keep enough of the account for the work that will use it. Broad discovery can return consequential meanings, disagreements and a grounded next inquiry; process modelling adds the selected flow, rules and variations; software design adds candidate consistency and interface boundaries. In each case preserve the question, scope, grounds, uncertainties and affected engineering use. Preserve participant understanding as well as an accessible description; test whether a receiving practitioner can retell the consequential relation. A photograph alone may omit the discussion that made a note intelligible.

A compatible account can supply a scenario and changed premise to SYSE.2, functional contributions and coordination questions to SYSE.5, or software alternatives to SYSE.6. A hypothesis about current functioning may instead need observation assessed through SYSE.10. Use only the receiving relation that is needed now. Building an event model does not require event-sourced storage, a message broker or a microservice architecture.

SYSE.54:5 - Worked case: a promised kit that maintenance has withdrawn

A field-service team is redesigning its equipment-booking support. Dispatchers say a crew receives a kit when a booking is confirmed. Storekeepers distinguish a temporary hold from physical pickup. Maintenance can withdraw the kit after inspection. The workshop asks what the new support must promise and what it must do when a hold cannot be fulfilled. The following values are constructed design inputs.

Participants initially place “request submitted”, “booking confirmed” and “kit collected” in one row. A storekeeper asks whether “confirmed” means allocated or collected; maintenance asks where withdrawal appears. They split the wording into “hold accepted” and “pickup recorded”, add the external event “kit withdrawn”, and mark the reaction to withdrawal as a hot spot. This changes the proposed behaviour before any database or service is chosen.

For kit K7, hold H31 belongs to crew C2 until 10:00. The proposed rule permits at most one active assignment of K7. A catalogue display can be a minute old, so a dispatcher viewing “available” sends request hold; the reservation operation checks authoritative availability before accepting it. Its outcome can be hold accepted or hold refused. The displayed value cannot authorize the promise.

The crew’s pickup request must name H31. Acceptance requires H31 to be active and the acceptance time to be before 10:00 on the agreed reservation time basis. Accepted pickup changes the assignment from held to collected; the hold is no longer available for expiry release. At or after the deadline, pickup under H31 is refused even if the expiry worker has not run. Release expired hold checks that H31 is still active and its deadline has passed before releasing it. The group has now exposed a concurrency requirement: pickup and expiry must be decided against compatible authoritative state and time conditions. It records that requirement for the software design.

ChallengeExpected behaviour in the proposed modelConsequence for design
A second crew requests K7 while H31 is activeRefuse that request or offer a different kit; do not promise the same assignment twice.The acceptance operation must preserve the assignment invariant.
The deadline has passed but expiry processing has not runRefuse pickup under H31; reconcile or release the expired hold.Acceptance checks the deadline as well as the current status, with an agreed time basis.
Pickup has already been recorded when an expiry request is processedDo not release the collected kit because of the old deadline.Identify H31 and its current state; replay of a stale request must not reverse a completed pickup.
Maintenance withdraws K7 before pickupSuspend fulfilment of the hold, inform the dispatcher and crew, and request a replacement decision.External withdrawal needs an observable input and a responsible reaction; automatic success is unavailable.
The maintenance message arrives twice or lateDetermine whether it concerns this kit and relevant interval; avoid repeating an irreversible response blindly.Message identity, currentness and reconciliation need an implementation decision.

The participants also ask what the crew sees while a replacement is unresolved. “Confirmed” would now be a false promise. They choose an explicit awaiting-replacement state and notice requiring the dispatcher to act. The model therefore changes the use concept, the information displayed and the work to be supported. A policy for which replacement is acceptable remains a domain decision.

The immediate result is the corrected account, these proposed acceptance conditions and two implementation questions: atomic handling of assignment transitions, and reliable receipt and reconciliation of maintenance changes. SYSE.2 uses the account to revise the linked use and system concept. SYSE.6:4.4.4 shows why the reservation invariant can stay in one authoritative operation while other work is separated. Observations of current depot practice and implementation tests can support claims about actual practice and implemented behaviour; agreement on the proposed model cannot establish either by itself.

Changed condition. Suppose maintenance provides no timely notification, only a nightly export. The same visible event sequence no longer supports a firm real-time availability promise. Participants compare a pickup-time inspection, a qualified provisional reservation and a changed provider arrangement. They must change the promised behaviour or obtain a timely contribution; adding a queue box cannot supply missing knowledge. Still-valid meanings of hold, pickup and identity remain useful.

Unlike use. In a design-consultancy inquiry, a client and engineer negotiate scope, revisiting cost and options in arbitrary order. A conversational region with “proposal accepted”, “inquiry withdrawn” and “response deadline reached” as exits can expose the handover to scheduled work. Enumerating a fixed command for every conversation would misrepresent this use. If only one representative story is needed to understand who exchanges which work objects, Domain Storytelling may supply a smaller sufficient account.

SYSE.54:6 - Biases to watch

The loudest participant can make a preferred story look shared. Seek the exception handler’s and receiver’s accounts, and preserve dissent at the affected step. A facilitator’s plausible completion of a gap is a hypothesis until someone supplies grounds. Familiar software objects can also dominate interpretation: ask about domain behaviour before mapping a sticky note to a class, table or message.

A smooth typical path is an insufficient challenge. Choose the variation from the real risk or uncertainty, not one guaranteed to preserve the current design. Distinguish disagreement about facts from disagreement about which future behaviour to prefer; they need different continuations.

SYSE.54:7 - Conformance checklist

IDA conforming use…
CC-SYSE54-1states the receiving question, current or proposed situation, scope and required perspectives.
CC-SYSE54-2constructs and tests a shared account with participants, who correct it where needed.
CC-SYSE54-3distinguishes occurrences, state, requests, performed actions and evidence where the receiving claim depends on them.
CC-SYSE54-4for a selected process or software design, explains the decisions, information and conditions connecting consequential events, including relevant external or time conditions.
CC-SYSE54-5tests consequential interpretations with concrete examples; when developing a flow, challenges its meaningful path with an action-changing variation and retains a blocking uncertainty as such.
CC-SYSE54-6derives any software consistency or language boundary from the behaviour and keeps its deployment choice open.
CC-SYSE54-7returns a usable account, proposed examples or bounded inquiry with grounds and limits appropriate to the next engineering use.

SYSE.54:8 - Common failures and repairs

FailureRepair
A wall of department tasksRecover meaningful occurrences and the behaviour connecting them; use activities when asking how an occurrence is produced.
Every request becomes successAdd refusal, waiting and failure outcomes; identify the condition governing acceptance.
Timeline treated as causal proofState the rule or physical dependency; obtain evidence for a claim about actual behaviour.
Every sticky becomes a service or event-store recordRecover the invariant, language and runtime question before comparing implementation boundaries.
A tidy happy path hides dissentRevisit the attached hot spot with a concrete counterexample and the missing perspective.
Negotiation explodes into arrows and loopsShow the conversational region, consequential rules and exits; formalize only the required guarantee.
Workshop consensus substitutes for permissionObtain the relevant decision and authority before changing actual work or promises.

SYSE.54:9 - Consequences

Participants gain a shared explanation they can challenge and use to change a concept, requirement or architecture question. The method can reveal hidden coordination, ambiguous promises and missing information before implementation commits to them. Learning and corrected relationships can be valuable even when the next result is an inquiry rather than a design choice.

It takes time and effort to involve people with the relevant experience, maintain a useful level of detail and preserve the reasoning for later users. Missing access, unsafe participation or unresolved professional questions limit reliance. A general claim that workshops reduce defects, delivery time or conflict needs evidence of those effects in practice.

SYSE.54:10 - Rationale

An event gives different participants a shared point from which to ask what preceded it and what it changes. Requests, decisions and state then explain the connections that chronology alone leaves open. Collective construction makes incompatible perspectives visible; concrete variations test whether their reconciliation survives a consequential change. The result is a domain explanation, with implementation and assurance questions made more precise.

A corrected domain flow can change a linked use and system concept in SYSE.2. An available concept can supply the question for a narrow modelling session. The method also specializes the collaborative reasoning of B.5.SD with a particular subject grammar and constructive route.

SYSE.54:11 - SoTA and source use

The practice question is how a mixed domain and engineering group can make behaviour understandable and challengeable before relying on it in design. Adopt and adapt EventStorming’s progressively corrected shared account. Brandolini’s current overview, especially “Main recipes” and its three format sections, distinguishes broad discovery, process modelling and software design. The overview also permits paper-based processes and simpler software architectures. The useful contribution is the relation between purpose, depth and modelling operations; promotional claims about universal effectiveness are not evidence for this pattern’s results.

Brandolini, Collaborative Process Modelling with EventStorming (2022) develops the request, decision-information and reaction-rule grammar. The current official patterns Chaotic Exploration, Incremental Notation, Rush to the Goal, Raise the Bar, and Extract Acceptance Tests explain different moves, not one mandatory workshop script. Adopt their conditional uses in §§4.1–4.4. Conversational System shows how to model a conversational process without imposing a fixed order. The kit case, its engineering returns and the distinction between proposed behaviour and evidence are the present synthesis; they are not reported source experiments.

For the software-design question, Microsoft’s tactical DDD explanation, “Aggregates”, connects a consistency boundary to domain invariants. Adopt that question when modelling conflicting state changes. The boundary can contain one entity or several; it is not inferred from the number of event notes. This use of DDD does not require microservices or make an aggregate, bounded context and deployed service identical.

An alternative is Hofer and Schwentner’s Domain Storytelling quick-start guide, especially its scenario and workshop sections. It develops concrete stories of actors, activities and work objects, with immediate correction and retelling. Prefer that route when a few representative interactions supply the needed understanding with less notation. EventStorming becomes useful when comparing event-centred accounts and the rules joining multiple reactions exposes the live difficulty. Neither method is generally superior; both require participants who know the domain. Another smaller answer is the use-case route in SYSE.2:4.5 when the question is already a bounded actor interaction and its implementable, testable slice.

The current official resources provide further facilitation and software-design material, including the inventor’s book and workshop formats. They can help a facilitator prepare. Obtain the domain knowledge from participants who hold it. When choosing a facilitator depends on their competence, use evidence of their ability to do the work. Reopen the selected route when its notation hides relevant behaviour, the participation burden exceeds its useful contribution, or an adequate existing account answers the question more cheaply. When the practice or its sources change, reassess the advice that depends on them.

SYSE.54:12 - Relations

  • SYSE.2 consumes a compatible domain account when it changes a use or system concept; it can also supply the bounded situation being modelled.
  • SYSE.5 uses the explained contributions, state and coordination conditions to construct bearer alternatives. SYSE.6 chooses among sufficiently developed architectures.
  • SYSE.7 keeps the resulting description compatible with other engineering accounts. SYSE.10 assesses the observations or tests used to support claims about actual behaviour.
  • B.5.SD supplies the general construction of a joint substantive answer.
  • When an explicit state-change rule is needed, use A.3.3.TR to specify what an action reads, changes and leaves unchanged, and to distinguish jointly active conditions from alternative actions. Return the usable rule or missing condition to the domain account. An adequate qualitative account needs no additional rule.

SYSE.54:End

SYSE.22 - Coevolve Engineering Problems and System-Family Options

Status: Stable

SYSE.22:0 - Use This When

Use this pattern when an engineering decision concerns alternatives for an actual or proposed product family and a changed condition calls the problem or the options into question. An observation on one unit can change the choice for the family when its shared design, admissible differences or effectivity matter. If the decision concerns only how one system can meet its own requirements, use SYSE.2.

A new operating condition, an effect on another System, a supplier limit, a technology or new evidence can invalidate the old problem–solution pair even while its backlog closes.

Begin with one observation or claim that can change the current engineering decision. Put the selected problem record beside the System option it currently constrains. State the receiving decision and the claim within it that would change—for example, an admission rule, comparison coordinate, affected-System consequence, evidence need, or choice. If none changes, keep the observation without reopening this decision.

The first useful result contains these four parts:

  1. the problem records selected for current attention and a separately retained problem archive;
  2. actual Systems in current configurations and possible-future System-family specifications with their architecture, membership, and effectivity bases;
  3. supported problem–option correspondences and unresolved mismatches; and
  4. one replayable ChoiceResult: choose an option or tie-set, reject the current set, request one worthwhile probe, or refer the question to the decision and authority that can answer it.

An Agent makes the bounded choice under authority. A DecisionSubject states whose choice is represented. Identify the performer and applicable authorization for any later experiment or implementation Work separately; the deciding Agent may also perform that Work.

When project focus, the operating environment or the affected Systems are unclear, use an applicable result from SYSE.1, SYSE.16 or SYSE.17, respectively, or obtain the result you need. Use SYSE.2 when the immediate question is a linked use-and-System concept, and SYSE.6 when the problem and option set are stable and only an architecture choice remains. Use C.18 when the question concerns only an archive or Front. A contested problem formulation may require a Decision Design Method; a changed Method may require Method Engineering.

SYSE.22:0.1 - Terms and Distinctions

Name in this patternWhat it denotes
problem situationThe world-side condition or relation that can frustrate an interest or intended use.
problem recordA ProblemCard episteme describing a problem situation or unresolved claim for one decision and period.
problem archiveRetained problem records, weak signals, alternative formulations, and stepping stones kept for possible later inquiry under a stated retention rule. This is an open content set governed by that rule.
selected problem portfolioThe finite set of problem records receiving attention, resources, or experiments in the current decision horizon.
actual System configurationA world-side System and its obtaining configuration during a stated interval.
possible-future System-family optionA specification of a candidate member, variant, or configuration under a named family architecture, membership rule, and effectivity basis.
System familyA family relation among member Systems or possible-future specifications under explicit membership and effectivity rules. The family is identified through that relation rather than reclassified as another System.
exploration archiveRetained candidate descriptions and lineage kept under a stated exploration-value rule.
FrontA non-dominated set identified for one candidate set, admission rule, comparator or dominance relation, characteristic set, and date.
decision OptionSetThe finite set eligible for consideration in one current C.11 choice under that decision’s inclusion rule. Inclusion for a development or probe decision does not establish admission for operational use. Membership in an archive or Front supplies no automatic membership here.
problem–option correspondenceA supported claim stating how one option changes admission, comparison, consequence, evidence need, or next action for one selected problem.
experiment proposalPossible-future content describing a bounded change and distinguishing observation whose expected decision value can be compared with its cost.

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.

SYSE.22:2 - Problem

The usual failure is a frozen pair: one backlog becomes the problem and one baseline becomes the solution. Local optimization continues after a relevant condition changes—for example, intended use, environment, a protected characteristic, a supplier condition, or the reachable System family.

Another failure retains many alternatives without their identities and rules. A single portfolio mixes records of unlike kinds—for example, signals, problem formulations, architectures, configurations, experiment proposals, and decisions. A moving Pareto Front then hides changes in its candidate set or comparator and appears to demonstrate improvement across incomparable questions.

Reopening everything after every signal can add work without changing the decision. The project needs dependencies and currentness conditions for individual claims so it can revise a problem without restarting unrelated Work.

SYSE.22:3 - Forces

  • Stable identities preserve evidence and decisions, while stale problem or family boundaries make that continuity misleading.
  • Retained variants preserve stepping stones, while a project needs finite current commitments.
  • Shared family architectures reduce repeated Work, while one environment or affected System can require a distinct branch.
  • Several options can remain non-dominated. For the next project move, decide whether to retain the set, choose a member or select a worthwhile probe.
  • Novelty can open a useful region, while admission, safety, evidence, integration, and service constraints remain.
  • Dependencies support selective reopening, while records that change no decision add maintenance cost.
  • A local gain can move cost, risk, Work, or failure exposure to another affected System.

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.

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 referent selected for engineering, or the System family with its membership and effectivity rules. For a creator, retain the products or classes of future use whose demands and shared resources its options must serve. Current use, environment, affected Systems, configuration, horizon, resources, DecisionSubject and authority complete the boundary. Local realization and acceptance do not require calling the creator a new SoI.
  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 a 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. For each option, state what is realizable now and any builder or platform change it requires.
  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.1.1 - Recover the changed engineering question

Use the eight moves above as a reminder. When a problem formulation or alternatives are missing, the following sections explain how the project can develop them. The intended practitioner can interpret the project’s operating and configuration records and obtain the needed domain, production, service, and assurance judgements. For a needed compressor model, safety limit or manufacturing process, use the result from the practice that establishes it.

Start at the observation that made the old pair doubtful. Recover the earlier use claim and the System concept that was supposed to support it. For one consequential operating situation, follow what happens from the triggering event through the proposed behaviour to the effect on the user or another affected System. Use SYSE.2:4.3–4.6 for that linked construction; use an adequate existing result directly. The return needed here is a use–concept pair, its conditions, any material uncertainty and the connection that is supported or has failed.

Identify what the observation changes. It may contradict the predicted effect, expose an omitted condition, change the value of the effect, or make a new means available. These lead to different engineering questions. For example, repeated network outages can change “minimize purchased peak power using cloud forecasts” into “maintain occupied-building comfort during a demand reduction, including loss of network service.” The new formulation retains the useful outside result and adds a condition that the old means did not meet. It does not make reduced comfort acceptable simply because the incumbent cannot deliver it.

A new means can instead initiate the inquiry: a local controller may make coordinated short demand reductions possible where only fixed schedules were previously affordable. Ask which use would benefit, what change in behaviour could supply that benefit, and which operating condition could defeat it. Keep a technically interesting challenge in the archive until there is a reason to spend current project resources on it. C.40.CD:4.1–4.5 supplies this general reciprocal development of a problem and a way; here the returned question must bind an engineering use, family configurations and realization conditions.

Preserve the obligation or interest behind the earlier formulation. Distinguish correcting a mistaken description, negotiating a different wanted result, and exploring a deliberately relaxed condition. A solution to the relaxed question answers the original only if its result can be returned under the original condition. When interests or authority remain contested, return that specific formulation question to the competent decision participants. Do not hide it as a low score for a design variant.

The result of this inquiry is a revised problem record and a reasoned relation to its predecessor: retained need with corrected conditions, a distinct new need, a superseded premise, or an unresolved disagreement. That relation tells later engineers which earlier evidence still applies.

SYSE.22:4.1.2 - Construct family alternatives with a feasible common basis

Develop alternatives around the disputed connection. Change the allocation of behaviour, the physical or computational means, the interface, or the operating arrangement when that could answer the revised question. An alternative can retain the incumbent, vary a current member, add a family branch, change the shared architecture, replace a previously assumed means, or stop pursuing this use. Creativity need not come from one assigned role: production, service and domain practitioners can expose a better candidate through their own constraints and available means.

For each promising alternative, recover what remains common and what must vary. State the retained architectural commitments, permitted differences and dependencies between differences. Use SYSE.13:4.1 for variant, unit, configuration and effectivity identity. It supplies the distinctions and supported mappings; the engineering work here determines which proposed combinations can meet this problem.

For example, local fallback, a different compressor, a larger processor and a network gateway are four design choices, not four independent switches. The new compressor may require a different output board; the fallback algorithm may fit only the larger processor; that board may lack an applicable test result. Build a candidate by carrying these dependencies together. Reject an incompatible combination, retain a conditional combination for inquiry, or propose the missing interface or realization change. Do not count the Cartesian product of independently feasible features as reachable family variants.

Retain more than one alternative when they answer materially different conditions or preserve a useful future choice. Ask which differences change admission, value, burden or later reuse; do not expand every possible parameter. The family boundary can also change. If an option requires different functioning, support and evidence assumptions from the shared architecture, compare a separate branch or family with extending the common basis. Forced commonality can move repeated adaptation and service burden into every member.

This produces candidate specifications with explicit variation and compatibility rules. It does not produce new actual Systems or establish that current installed units realize the specifications.

SYSE.22:4.1.3 - Test the join between use, variant and means of realization

A correspondence becomes useful when an engineer can follow why the variant could answer the problem. For each relied-on pair, connect the outside result to the proposed behaviour, the required configuration, the means of obtaining it, and the evidence the receiving decision needs. Use the supported realization branch from SYSE.3:4.2–4.4, a platform result from SYSE.12:4.1, and the applicable SYSE.10 evidence assessment where these answer the question. Open only the first unsupported result that can change the decision.

The conditions must hold together. A candidate that fits one board, a test that covers another firmware realization, and a service procedure for a third installation do not combine into one supported family option. Likewise, separate statements that two trials can each use the only rig this week do not make their simultaneous commitment feasible. Compare compatible configurations, conditions and receiving decisions, and check shared capacity where the portfolio relies on simultaneous Work. Use SYSE.20 when overlap or acceptance of a partial result is the engineering question.

Keep two different conclusions visible. An option can deserve development attention while its operational admission remains unresolved. A bounded experiment can be feasible even when its subject variant is not yet admissible for ordinary use. State the scope of admission at the receiving decision; evidence sufficient to select a probe does not become evidence that permits deployment.

Use a failed join constructively. If a variant cannot be tested within the existing arrangement, the result may be a precise builder investment question for SYSE.23. If the proposed behaviour cannot supply the required outside effect, return to the use–concept pair. If every candidate fails a protected condition, reject the set or seek an authorized reformulation; ranking failed options cannot supply a successful one.

SYSE.22:4.1.4 - Let one side revise the other without losing the original need

Run the candidate forward far enough to reveal the consequential mismatch. A model, an existing comparable case, a supplier answer or a performed trial can supply that result at its own evidential strength. Relate it back to the problem before generating another variant.

Result that changes the inquiryEngineering revisionWhat remains to be established
A candidate achieves the stated output but an occupant or service System is worse offCorrect the problem’s consequence or protected condition; revisit dependent alternativesWhether a replacement candidate satisfies the corrected use
A new means makes a previously unattainable use plausibleAdd a use–concept pair and compare its worth with the selected portfolioActual demand, feasibility and admission; technical possibility alone supplies none of them
Different family members require incompatible assumptionsSeparate their applicable conditions, introduce a justified branch, or change the family basisShared resources and cross-member consequences under the proposed arrangement
The target variant is plausible but its construction, evidence or support cannot be obtainedKeep its promise conditional and frame the limiting builder relation for SYSE.23 or the obtaining question for SYSE.24A compatible supported means of obtaining the result
A candidate disproves one interpretation of the problem but leaves another usefulRevise or retire the defeated claim and preserve the supported branchWhat the evidence supports about the remaining branch and any question still open

A better means may change which problem is worth current attention. Conversely, a revised problem may change which retained design is useful. Preserve the decision-bearing reason for that movement. This is how an old stepping stone can become useful again without treating its earlier rejection as an error or its archive membership as current endorsement.

SYSE.22:4.1.5 - Compare complete alternatives and stop at a useful decision

Use one comparison situation per consequential operating profile, including the failure condition that reopened the question. Compare complete candidates under the same profile and assumptions. Keep admission constraints separate from preferences among survivors. If an option obtains its benefit only with an unprovided builder change, include that change and burden in the comparison or keep the benefit conditional.

When profiles favor different members, the useful result can be a family rule assigning different variants to different conditions, rather than one universal winner. Examine the shared consequence: supporting two members may require extra configuration, spare parts, qualification or service Work. The cost of the portfolio is not necessarily the sum of isolated variant estimates; common tools can save work while common scarce resources can create conflicts. Do not claim family superiority from two separate local wins.

A revealing probe is worth selecting only if an obtainable outcome could change this comparison enough to justify its full burden. The current result can also be enough to choose, retain a tie, reject, narrow or stop. Use the existing decision account in C.11.

SYSE.22:4.1.6 - Pass the unresolved engineering question at its actual scope

The receiving work determines the next use of the joint account. A compatible use–concept pair can go directly to architecture Work through SYSE.6; a supported member can proceed through its existing realization arrangement. Use SYSE.23 when the unresolved question is which change in the target or its builders is worth making to enable later changes. Send the expected change family, blocked correspondence, current configuration and realization basis, protected conditions, horizon and relevant uncertainty. The receiver constructs its investment alternatives; the SYSE.22 choice does not select an investment for it.

Use SYSE.24 when the needed contribution is clear and the remaining comparison is how to obtain it. If the question instead concerns wider agreement about the problem, return that question to the relevant problem-structuring or strategy practice.

A builder improvement from SYSE.23 returns as a changed feasibility premise only for the family options it affects. An investment decision can support an expectation of improved feasibility. Stronger reliance needs evidence of the capability or a realization result that demonstrates the improvement. Reconsider the comparison to the extent that the new result warrants.

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.

SYSE.22:5 - Worked Case: Heat-Pump Controller Family

In this constructed case, a manufacturer maintains heat-pump controllers for occupied apartment buildings. The current decision concerns the controller family and a reversible building pilot. Installed controllers and a laboratory unit are actual Systems; the options below are possible-future specifications under the family’s architecture and effectivity rules.

The earlier selected problem was peak electrical demand during cold mornings. The preferred specification used a schedule optimizer and cloud forecast service. These three field observations now reopen the comparison:

  1. several buildings lose network service during the coldest periods;
  2. compressor cycling increases service calls in one installed configuration; and
  3. a new tariff rewards short demand reductions but penalizes slow recovery that leaves occupants cold.

The current problem portfolio and System-family options produce four correspondence rows:

Problem recordSystem-family optionDecision-bearing correspondence
peak demand, now with recovery-time and occupied-temperature acceptancecloud schedule specificationNetwork loss makes the option inadmissible without a qualified fallback; recovery time enters comparison.
network-loss continuitylocal-fallback specificationLocal forecasting can change continuity and recovery, but processor-load and fallback evidence are missing.
compressor cycling for the affected configurationvariable-speed-control specification and incumbent controlVariable speed can change cycling and energy use while increasing calibration and service burden.
speculative voice-control request, retained only in the archivevoice-gateway specification, retained only in the option archiveNo current use or affected-System consequence gives this pair decision priority.

The final row explains archive retention and current non-selection; it supplies no OptionSet member. The first three rows are the complete correspondence set used by the current decision.

The earlier Front compared energy use and peak demand. The current comparison uses a new candidate set and the following complete coordinate set: continuity, recovery time, occupied-zone temperature, peak power, compressor cycling, processor load, calibration effort, and service burden. It is therefore a new Front with its own basis.

The fixed current OptionSet has three members:

  1. continue developing the cloud-schedule specification;
  2. develop the local-fallback specification; or
  3. develop the variable-speed-control specification.

Safety and occupied-zone comfort are hard guards. The remaining coordinates form a partial order. The cloud- schedule specification without a qualified local fallback fails the network-loss guard. The variable-speed option retains the incumbent local control during network loss and remains admitted, but evidence about processor load and cold recovery is missing for the local-fallback option. That option cannot yet be admitted or rejected.

The controller-family council is the deciding Agent. Its current assignment authorizes it to choose the next engineering probe, or decline new probing on the present basis, and allocate no more than 160 engineering hours. A building operations manager authorizes any occupied-building trial; the product-family owner authorizes later adoption. The probe choice grants neither authority.

The council uses one shared comparison basis:

  • The fixed OptionSet remains cloud schedule, local fallback, and variable-speed control.
  • The current BeliefState contains the three field observations, the hard safety and comfort guards, the cloud option’s network-loss failure, the variable-speed option’s admitted local control, and the missing local-fallback processor-load and recovery evidence.
  • The OutcomeModel states how each possible probe observation changes admission and the survivor relation. A local-fallback pass admits that option and leaves it non-dominated with variable-speed control; a guard failure or processor overload rejects it. The current calibration uncertainty changes burden estimates for variable- speed control but does not change its admission or resolve the local-fallback question.
Candidate next probeBounded burdenDistinguishing observationsEffect on the current decision
Scripted network-loss and cold-recovery trial96 engineering hours, two hardware-in-the-loop bench days, one three-day reversible building-pilot window, and about one week of decision delay.In each of two representative building configurations: no safety violation; occupied-zone recovery inside 20 minutes; and controller processor load below 70%. The outcome is contrary if either configuration has an established safety or comfort guard failure or a processor load at or above 70%. Incomplete, uncertain or otherwise non-decisive observations remain unresolved only when no such failure has been established.A pass admits local fallback and leaves it with variable-speed control in the survivor set while cloud-only is rejected. A contrary outcome rejects local fallback and leaves variable-speed control as the admitted next-development option. An unresolved outcome preserves the unresolved local-fallback status and requires a new bounded decision.
Variable-speed calibration trial128 engineering hours, four calibration-rig days, the same single building-pilot allocation, and about two weeks of decision delay.Calibration effort and service burden may fall or rise within the currently supported range; the trial does not observe network-loss recovery or local-fallback processor load.Either bounded outcome refines the burden comparison for an already admitted option but leaves the local-fallback admission defect and survivor question unchanged.
No probeNo immediate trial resource use or delay; preserves the scarce pilot allocation and engineering capacity.No new observation.Retain the qualified current comparison: cloud-only fails the guard, variable-speed control remains admitted, and local fallback is retained only as an unresolved candidate, not admitted for use. Later development or adoption still belongs to its competent owner.

The ChoiceRule compares obtainable probes with retaining the qualified current result. Changing admission or the survivor relation is a possible contribution, not an obligation to buy it. In the first resource situation of this case, the council’s qualified judgement is that resolving the local-fallback option before the next family investment is worth the 96 hours, scarce pilot allocation and one-week delay. Assume that capable performers and the windows can be obtained, and that this allocation does not displace more valuable protective or development Work. Those benefits, costs and conditions support selection within the 160-hour ceiling. The calibration trial cannot resolve that question. The deciding Agent applies C.11 and records ChoiceResult-HPF-1 = probe_again for the network-loss and cold-recovery trial.

In the paired resource situation, the same discriminator would consume the only pilot window needed for already supported protective maintenance, or no competent performer can use it before the investment decision. The council can decline that probe and retain the qualified comparison above. Local fallback stays unresolved; no observation or safety assurance is invented. A later owner can make a supported bounded development choice among admitted options.

In the selected-probe situation, after that ChoiceResult, a planning Agent must prepare the trial plan, the building operations manager must authorize the occupied-building trial, and assigned Agents must perform and interpret the Work. Family adoption remains a separate decision by the product-family owner. If pilot authority is withdrawn before the trial Work, a new decision pass records reroute and the missing authority without rewriting ChoiceResult-HPF-1. For a later observation, reconsider any of the three current problem–option correspondences and family results that depend on what changed. The voice-control archive entry remains unchanged.

For currentness, first keep the same configurations, relied-on observations, calibration, rights and supported use while only the source export date changes: the comparison remains usable. Now change a controller configuration so that the relied-on processor-load evidence no longer covers it, or let a calibration or pilot permission window end. Reopen or suspend the uses that relied on the changed condition. Keep the needed qualification with the comparison for later receivers. The case’s 20-minute and 70% limits are receiving acceptance conditions, not universal thresholds supplied by this pattern. Their protective basis and any proposed amendment require the relevant engineering judgement and authority; merely choosing or declining a probe changes neither.

SYSE.22:5.1 - Construct the family account behind the probe and use its return

The heat-pump case starts with observations, not three fully formed alternatives. To obtain the specifications above, the engineers first retain the outside need for acceptable heating and change the problem from peak reduction alone to peak reduction with continuity and timely recovery. Following SYSE.2:4.3, they trace the cloud command through the connection, local controller and compressor to the occupied-zone effect. The trace exposes the missing behaviour during disconnection. Continuing with only a lower peak-power target would leave that failure intact.

They then vary the means at the failed connection. One proposal adds an independently functioning local mode; another changes compressor control while retaining the existing local protection. The cloud-only proposal is kept in the comparison long enough to show why it fails the revised condition. Voice control does not repair that connection and stays outside the selected portfolio.

For this constructed account, assume the larger processor is available only in two controller configurations, and that the variable-speed compressor needs its matching output board. The option descriptions therefore name those combinations and the effectivity proposal; they do not offer every feature on every installed unit. The local-fallback option’s conditional status is precise: a plausible configuration exists, but the current decision lacks the load and recovery evidence that would permit its admission. The rig and occupied-building window in §5 explain how that uncertainty could be resolved.

Now take the selected-probe branch and stipulate that the authorized trial is subsequently performed and passes its stated limits in both configurations. The interpretation admits local fallback on that bounded basis and preserves variable-speed control as a non-dominated alternative. It does not choose a release or extend the observation to other boards. The family owner can now compare different members for their applicable buildings rather than insisting on one universal controller. The problem portfolio remains the three selected problems; the voice-control request is unchanged.

The next supplier-change inquiry reveals that producing and assuring more combinations with rig R4 requires repeated interface work. The returned SYSE.23 question is specific: for the named controller family and next supplier replacement, which target, rig and evidence changes would reduce that repeated work while preserving the existing comfort and configuration limits? Local-fallback evidence supplies one applicable input; it does not settle the supplier interface or evidence-reuse questions in SYSE.23:5.

Changed condition. Suppose a later building requires the smaller processor, on which the fallback algorithm would exceed the same load limit. The passed trial remains valid for its two configurations. The revised family account keeps the supported larger-processor member where applicable. The same fallback specification fails the smaller-processor condition and is excluded for that use; it is not merely awaiting more evidence. Incumbent local control can retain its previously supported use while a different algorithm or board is considered for the unmet demand. The owner compares a separate branch’s supply, configuration and service burden with replacing the small board. Reclassifying the small-board building as “not a customer” would change the problem scope and require its own grounds and authority; it would not demonstrate that the fallback solves the original use.

SYSE.22 changes which problem–variant pairs are worth pursuing; SYSE.23 can change the means and burden of reaching them. Either result can stand for its own decision while the other remains unresolved.

SYSE.22:6 - Bias Annotation

Watch for these six recurring biases:

Recurring biasLikely driftRepair
requirements-freeze biasThe approved backlog becomes the permanently current problem.Recover the world-side situation and the receiving claim’s applicable premises, including real time limits; reopen only decisions affected by their change.
solution-fixation biasEvery observation becomes a modification of the incumbent design.Reopen both problem formulations and family alternatives; admit a branch, replacement, or stop when supported.
archive-as-portfolio biasEverything worth remembering receives current attention and budget.Keep retention membership separate from current portfolio membership.
one-Front biasPoints from changed candidates or comparators are plotted as one improvement curve.Identify each Front and its basis; make any cross-basis comparison separately.
novelty biasA distant or AI-generated option is treated as useful or admissible by novelty alone.State the reference set, admission rules, consequences, and evidence.
measurement maximalismThe project waits for field-wide prevalence or conclusive causal attribution before a reversible probe.Use proportionate evidence with explicit uncertainty and limits.

SYSE.22:7 - Conformance Checklist

  • The decision boundary identifies the actual System or intended System referent selected for engineering, or the System family; current use, environment, affected Systems, configuration, horizon, chooser and authority. For a creator, it retains the product-use grounds and bounded acceptance.
  • World-side problem situations and ProblemCard epistemes remain separate.
  • The problem archive and finite selected problem portfolio have separate membership rules.
  • Actual Systems and configurations remain separate from possible-future specifications.
  • Every option identifies its family architecture, membership or variant rule, and effectivity basis.
  • Exploration archive, Fronts, and current OptionSet retain their own candidate and admission rules.
  • Every relied-on correspondence changes a decision-bearing claim or remains visibly unresolved.
  • The comparison preserves relevant result and resource coordinates, protected losses, affected-System consequences, uncertainty, and non-dominated alternatives.
  • The choice or probe result states its basis, rule, full burden and value when relevant, actual obtaining conditions, authority, and reopen condition. Retaining a supported result is not conditional on a new probe.
  • Proposal, planning, authorization, performed Work, observation, and later adoption retain separate results.

SYSE.22:8 - Common Failures and Repairs

Recurring failureRepair
Backlog equals problem portfolioRepair the selected ProblemCard values and state why each receives current attention.
Candidate specification equals future SystemKeep the specification possible-future; state realization and later-test Work.
Addresses problem fills every correspondence cellState the changed admission, coordinate, consequence, evidence need, or next action.
Archive equals FrontPreserve archive membership under its retention rule and Front membership under its comparator.
A changed Front is presented as improvement on the old FrontIdentify both bases and make any cross-basis claim separately.
A probe choice is presented as family adoptionIdentify later planning, authorization, Work, evidence, and adoption decision.
Every new source restarts the projectTrace the source claim to its receiving use and reopen only dependent results.

SYSE.22:9 - Consequences

The project can change both what it is solving and what Systems it considers without discarding lineage. Useful stepping stones remain recoverable, stale comparisons become visible, and one bounded probe can be chosen while the problem and System family remain revisable.

The cost is maintenance of identities and decision-bearing correspondences. Some correspondences may remain unresolved. The best current result may be a probe, rejection, or referral to another decision.

SYSE.22:10 - Rationale

FPF supplies problem records, plural search, archives, Fronts, currentness, comparison, and choice. Systems Engineering adds the action-changing specialization: selected problem formulations must be compared with architecture- and configuration-identified System-family options under project use, operational environment, affected-System consequences, realization limits, and engineering evidence.

The terms problem factory and solution factory describe different but corresponding Work and Method structures. The described Work can take place concurrently. Identify the Systems involved separately; use SYSE.20 when overlap or required order becomes the engineering problem.

SYSE.22:11 - SoTA and Source Use

Engineering can revise problem formulations and System-family options together, including the Work and Methods used to develop them. Problem archives and portfolios retain material for later choices; comparison and acceptance use their stated bases. When the way of developing a System becomes the obstacle, the same inquiry can extend to its builders.

NASA’s Design Solution Definition guidance, §4.4.1.2 connects iterative concept development, operating concepts, stakeholder expectations, technology maturity and enabling products. Use a sufficient result from that practice directly. This pattern’s additional work is the engineering connection between a changing problem portfolio and configuration-qualified family alternatives: explaining which combination is reachable, which use it can answer, and which changed premise reopens the comparison.

A competent product-line practice can provide a variability model and a way of producing its members. For example, the SEI production-plan guidance describes how core assets are used to build a particular product. Retain that supported basis rather than rebuilding it here. The remaining question in this pattern is whether changed use and realization conditions require a different family option, problem formulation or current commitment.

SourceRetained contributionUse boundary
Dorst and Cross (2001), Creativity in the design process: co-evolution of problem–solutionMutual development of problem and solution spaces in protocol studies of experienced industrial designers.Use as bounded design-process evidence; establish the current System family and configuration separately.
Liker et al. (1996) and Sobek, Ward, and Liker (1999) on set-based concurrent engineeringCommunication about design sets, delayed commitment, feasibility, and narrowing in automotive product development.Transfer the set-based moves only where the receiving profile’s constraints and evidence support them.
Castle, Stock, and Gorochowski (2024), Engineering is evolutionVariation, expression, evaluation, selection, exploration, and exploitation as an engineering perspective.Use the evolutionary analogy as a hypothesis source; ground the current engineering Method and cultural claims separately.
Zhang et al. (2025), Darwin Gödel MachineAn AI-engineering case retaining a lineage-bearing archive of coding-agent variants for later improvement.Treat coding benchmarks as one application case; test transfer to physical Systems and causal claims separately.

Reconsider how you use a source when changed evidence alters its practical contribution or the scope of the conclusions you can draw from it.

SYSE.22:12 - Relations

  • SYSE.1, SYSE.16, and SYSE.17 supply project focus, operational environment, and affected-System consequences for compatible uses.
  • SYSE.2, SYSE.6, SYSE.7, SYSE.10, and SYSE.13 supply linked concepts, architecture decisions, descriptions, evidence, and family/configuration/effectivity identity.
  • SYSE.15 can supply a compatible engineering-Method repertoire. SYSE.21 can supply bounded observations of an enacted variant and its population; each claim keeps its own evidence and transfer boundary.
  • C.40.CD:4.1–4.6 supplies the general reciprocal development of a question and a way; SYSE.22:4.1.1–4.1.6 binds its use here to family compatibility, realization and receiving decisions. SYSE.2:4.3–4.6 supplies the linked use–concept construction, and SYSE.3:4.2–4.4 the realization branch.
  • C.22.2 governs ProblemCard epistemes and C.22.PFR any world-side ProblematicForRelation. C.17, C.18, C.19, G.5, and G.11 govern characterization, archives and Fronts, live pools, selected sets, and use-qualified currentness. SYSE.19 and SYSE.23 retain changed-premise and claim-specific receiving rules.
  • C.11.CRC governs finite configuration-relative contribution comparisons and C.11 the bounded choice.
  • Supply the project focus, selected problem portfolio, System-family option set, correspondences, unresolved mismatches, and current ChoiceResult from SYSE.22 to the Agent using SYSE.23 for an investment or reconfiguration decision.
  • Feedback reopens SYSE.2, SYSE.6, or SYSE.13 only when the changed result crosses their stated reopen condition.
  • Decision Design, Strategy, Method Engineering, and Operations Management retain their domain Methods even when their Work uses the same archives or decisions.

SYSE.22:End