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

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 10:39:56 UTC

SYSE.2:7 - Conformance Checklist

IDRequirement
CC-SYSE2-1A conforming use SHALL name one concrete use situation, one candidate system-concept claim, and their 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 the uncertainty carried into it.
CC-SYSE2-9When architecture, realization, observation, or specialist evidence challenges a claim, that evidence SHALL return to the smallest use, concept, or project-focus claim it can change.