C.30.TFS-REL:12 - Relations
Builds on: C.30, C.30.AD, C.30.ASV, A.22, A.6.F, A.3.4, E.18 for one TFS, E.18.NET for one selected conforming network and obtaining cross-member relations, E.17.0, E.24.PUB, A.7, E.10, C.2.P, and F.18.
Coordinates with:
C.30.STRAT;C.32.P2Swhen architecture-to-transformation-flow grounding is one stage of problem-to-structure architecturing;C.32when selected transformation-flow variants become candidate architecture inputs;C.33when transformation-flow relation descriptions capture or lose selected architecture structure;C.34when transformation-flow claims must be preserved across a mapping, model, generated output, or realization;C.35when a generated or discovered carrier may seed synthesis;A.15.1for Work occurrence;A.15for Method/Work alignment;A.20,A.21,A.10,G.6,B.3,C.28,C.29,C.16, admitted measurement, selection, or candidate-set governors;A.6.Mmodule-claim repair and direct interface owner;A.6.5when reusable relation-participant typing is needed;A.6.0when a signature declaration is being made.
Related claims stay with their governing patterns:
| Governing pattern | Related claim or use |
|---|---|
C.30.STRAT | Stratification wording and source-label repair |
| E.18 | One selected TFS, path, crossing, and flow valuation |
| E.18.NET | Network identity and cross-member relations |
| E.18.2 | Mathematical descriptions |
| C.29 | Mathematical representations and lens use |
| C.30 | Direct architecture relations and selected-structure adequacy |
| C.30.AD | Description identity/use |
| E.17.0/C.30.ASV | Structural-view conformance and adequacy |
| A.3.4 | Actual transformations |
| C.32.P2S | Connected problem-to-structure carry-through |
| A.6.F | Function-use repair |
| Non-flow governors named in section 4.3 | Non-flow claims |
C.30.TFS-REL governs only the bounded architecture use of the selected TFS or TFS network.