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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:20:20 UTC

SYSE.9:4.1 - Perform the Move

  1. Name the receiving decision. State the question, alternatives, deciding Agent, Work that will use the result, and consequence of delay or error.
  2. Use the present result and select any further acquisition. Inspect what the available result supports for this decision and return its useful answer and material limit. If further inquiry is live, use A.15.9 and C.11.DUA to compare its attainable contribution with preparation, qualification, supplier Work, delivery, interpretation, delay, displaced work, and alternatives. For a selected request, name the bounded calculation, constraint, objection, observation, or other result that supplies that contribution.
  3. Bound the result. Name its subject and the applicability dimensions that could change the answer. For a System claim these may include the actual or intended System, configuration, part, environment, affected System, use, interval, scale, and assumptions.
  4. Retain the supplier’s Method and evidence. For a selected acquisition, the specialist practice identifies its Method, source family, inputs, observations, uncertainty, and non-use boundary. A missing Method limits the promised result; investigating it is another acquisition choice under step 2.
  5. Choose and enable the performing Agent. Check current capability and the conditions that affect this Work, such as access, workload, conflicts, resources, and tools. Establish an assignment only when it matters. Establish permission, authority, commitment, or responsibility separately and from its own governing relation.
  6. Perform and identify the Work. Keep planned Work distinct from dated Work. Record the enacted Method, inputs, performer, relevant assignment, and production of the result. A ticket, calendar entry, generated activity trace, or tool label does not prove this Work.
  7. Assess and use the return. Check its subject, configuration, provenance, evidence, uncertainty, limits, and acceptance conditions. Accept it within a stated reliance limit, reject it, request repair, choose another contribution when its acquisition is worthwhile, or retain the blocker in the useful answer.
  8. Observe and reopen. Use later evidence—for example from integration, realization, operation, affected Systems, or assurance—to reopen the smallest affected request, assignment, Method use, result, or engineering decision.

Step 2 can finish with the supported answer; steps concerning a new request or Work open only for that branch. This is an A.22.CGUS learning unfolding, not a required temporal sequence for all project Work. Several Agents may perform specialist Work concurrently and return partial results iteratively. The logical dependencies remain: a title cannot replace a requested result, an assignment cannot replace Work, and a produced result cannot replace its assessment and use.