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

Link to current text

Published source confirmed at last check

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

SYSE.15:12 - Relations

  • A.3.1 identifies each Method; A.3.2 identifies a MethodDescription; A.15.1 governs dated Work. A source, description, assignment, capability, tool, or run does not occupy the Method position. A.15.6 governs the project-relative Method-of-interest designation. It distinguishes a Method enacted in the subject’s operational Work, a Method used to create or change a System, a solution Method, a Method-of-interest, and a Method used to develop that Method-of-interest.
  • A.3.1 distinguishes several broader Method kinds from participation in several whole Methods. A.22, B.1.5, and direct relation patterns still govern selected structures and whole–part claims.
  • C.32.MWA keeps Method classification, Method holarchy, result dependencies, Work order, provider or enabling Work, capability development, and cultural change as different structures that may all be needed in one case.
  • E.8:4.1.3 tests whether a narrower engineering contribution changes useful and warranted action at comparable effort. It neither selects the Method nor proves practical worth.
  • Apply E.23 when a named Method itself must be improved. In this pattern, the Agent choosing a bounded engineering Method repertoire performs the decision Work described here. When a Method must be created or changed, use the applicable Method Engineering result or a qualified direct source.
  • G.5 supplies a shortlist or joint-use set only when a later selection needs that result. It establishes neither Method identity nor actual capability, compatibility, enactment, or uptake.
  • Route platform, simultaneous-Work, cultural-continuation, and obtaining-arrangement questions to the Agents applying SYSE.12, SYSE.20, SYSE.21, and SYSE.24, respectively. Their co-use creates no automatic temporal order.
  • Application Methods—for example, organization-change, operations-management, software, electrical, medical, maritime, or building Methods—retain the Systems they create or change, their evidence, authority, and applicability. Shared vocabulary does not make them parts of one universal process.