SYSE.5:12 - Relations

• When compatible, practitioners can use linked use/System candidates and unresolved mismatches from a SYSE.2 result as inputs. They must still check the subject, configuration, horizon, evidence, and compatibility before developing the alternatives in this account.
• Use A.6.F to restore each function-like claim and possible bearer. A.6.M governs module and interface claims; A.22 and C.30 govern selected structures and architecture relations. Applying those patterns alone does not produce the Systems Engineering allocation account defined here.
• Use C.32 for general multi-structure architecture-candidate synthesis. SYSE.5 specializes that Method with the required-effect, functional-organization, constructive-bearer, physical-interface, realization, integration, wrong-use, and decision-use questions. Use a C.32 candidate palette here only when its subject and fields fit the current decision question.
• The allocation-alternative account is an input to architecture-decision Work governed by SYSE.6. That Work may produce a chosen architecture and conditions for revisiting it. Candidate generation in SYSE.5 does not select the architecture.
• When an unsupported realization or build-the-builder dependency, evidence claim, description-correspondence problem, or assurance question is current, apply SYSE.3, SYSE.10, SYSE.7, or SYSE.4 respectively to its own subjects and sources. The realization dependency, evidence claim, description-correspondence problem, and assurance question concern different engineering subjects and require different Work results; Work performed for one does not supply the missing results for the others. A description ensemble remains distinct from candidate Systems, allocations, interfaces, and the selected architecture.
• Under XRI-03, practitioners can reuse a compatible SYSE.5 result in MDPE.3 when an engineered instrument, robot, hybrid body, venue, or software System is itself an architecture subject in the performing whole. Recheck the reused result against the MDPE subjects, authority, conditions, evidence, and current music-and-dance sources.
• Agents performing downstream application Work—for example procurement, manufacturing, configuration, maintenance, operations, software, electrical, mechanical, safety, or human-factors Work—use the result through their own Methods, authority, conditions, and evidence.