SYSE.3:4.2 - Describe one realization branch
Write one branch in ordinary language. Include only the distinctions that change the feasibility question:
- the architecture result to be realized;
- the pre-existing System, material, assembly, description, or other referent that would be changed, or the identity and completion conditions for a System that does not yet exist;
- the intended change, production result, interface state, integration state, or configuration relation;
- the proposed transformer System or unresolved need for one and the local
TransformerSystemRolecondition it would meet for this Work; - the needed Method, capability envelope, resource, tool or platform contribution, access condition, interface, integration, and configuration relation; and
- the fact or specialist result that would make the branch usable, require its repair, or reopen an earlier answer.
Keep modal and actual claims apart. An intended change belongs in a plan or description until an actual
continuing referent, boundary, conditions, and before/during/after facts satisfy A.3.4. When the proposed
System does not yet exist, describe changes to pre-existing materials or assemblies and use A.15.PROD later
for independently grounded identity inception and production completion. Do not describe transformation of a
future System before it exists.
The claim that a candidate transformer will perform the Work is also modal. Name the candidate holder System,
or the unresolved need for one, and the local TransformerSystemRole condition in the WorkPlan. Use A.2.1 only when an assignment occurrence actually obtains, and use A.2.2 only when the
holder’s capability has a recoverable Work family, envelope, measures, qualification window, and currentness
condition. Treat a job title, supplier category, tool list, past success, or Method description as possible
evidence inputs; establish the capability claim through its Work family, envelope, measures, qualification
window, and currentness.