Coordinate Related Models for Use and Handover
About this pattern
This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a FPF Reference product feature page.
How to use this pattern
Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.
Type: Method pattern Status: Stable
Use this when a decision depends on what several models establish together, or a successor must be able to interpret, reproduce or revise their results. The models may concern a system, a method, a relation, or several connected entities. A colleague can understand every diagram and still be unable to answer the question for which they received the set.
Relations
Content
Problem frame
Use this when a decision depends on what several models establish together, or a successor must be able to interpret, reproduce or revise their results. The models may concern a system, a method, a relation, or several connected entities. A colleague can understand every diagram and still be unable to answer the question for which they received the set.
Start with the work the recipient must do and the conclusion on which it depends. If a single understood model settles the question, use it directly. C.37:4.6 covers the simpler case in which a recipient needs several representations for one action and each keeps its own supported conclusion.
Problem
One model can omit a condition another silently assumes. A recipient can also receive all the needed models and still lack the conventions for reading a blank entry, a shared designation or an estimate. Which models, relations and methods must remain available for the recipient's work?
Forces
Adding material from more specialists can improve coverage while making a contradiction harder to locate. The author may know an interpretation that a successor has never encountered. Recording every possible connection imposes work and can hide the few connections that determine the answer.
Solution
Establish what the models must support together
Name the intended inference, action or reproduction task and its possible outcomes. Identify which model supplies which premise. For each premise recover the modeled entity, conditions, interpretation and relevant edition. A local name for several models supplies a convenient reference. If the proposed multimodel is to be relied on as a coordinated set, establish the consequential connections that let the models support this use.
When several models concern the same entity, establish its identity across them. When they concern different entities, state the actual relation. A system, the work that produces it and a cost estimate for that work can all affect one design decision. The estimate's use depends on what work it covers. For an admitted holon, B.1 and the kind-specific method govern the inference from the constituents and their organization to a whole-level result. A modeled relation with independently identified participants needs no presumption of physical parts.
Choose and connect the required ranges
Start from the composition scales and model distinctions the decision calls for. If choosing a range is part of your task, use C.39.SA:4. If the intended recipient must choose, make the method and evidence for that choice available to them. In a multimodel, establish what each model contributes and how those contributions can hold together.
- Identify the types of entities and actions that can affect that result. For each relevant kind of holon, follow its own composition as far as the decision needs. A system has integrated components. A composite Method admits particular Methods under its construction rule. For composite dated Work, establish which actual performances did a constitutive part of that very job. An overlapping or earlier performance can help without belonging to it. An episteme can depend on several claims with a common ground. For a discipline, identify the knowledge and practice its working arrangement integrates. A part, an available alternative and an external supplier can play different parts in the decision.
- For each inference, identify what its model can leave open. Which alternatives must remain distinguishable for this inquiry? Can a general rule settle it throughout the stated range? Use B.5.MR when comparing models towards greater abstraction or refinement. You can change the scope of composition while holding model abstraction fixed, or compare models of the same whole while holding its composition in view.
- Connect the results. Name who or what participates and the relation on which the inference depends. Work enacts a Method. A system participates in the Work. A report relies on an observation made during that Work. These links may be needed together. A rule at every eligible scale, an influence across scales and a result of several working together each need grounds for the connection they assert. A control layer adds its own functional organization when the decision depends on it.
- Trace the explanation forward to the recipient's decision. Could all the local claims stay true while a different connection changed that decision? If so, recover the missing connection when it is available. If it is unavailable, give the warranted partial answer and identify the condition that still decides the original question. A partial result can finish the commission when it already settles the recipient’s criterion. For an assertion covering a range, show why the grounds hold throughout it. One governing rule or a sufficient bound can sometimes settle the entire question.
For example, a receiving shift needs to know whether two language desks can jointly issue consistent stop instructions today. The desks are components of one publishing service. Comparing the stop clauses belongs to the release Method. Identify the reviews actually performed as contributions to this release. Check that each signed report covers the translation now ready to issue and identifies its applicable source edition. An earlier, independent review of those same texts can support their consistency when the release terms accept it. That reliance need not make the earlier review part of today’s Work. Both reviews can be correct while one source calls for a stop before the next operation and the other calls for it afterwards. Following the reports back to their sources reveals the conflict. If the sources differ only elsewhere, both translations convey the same applicable stop condition, and the commission accepts that equivalence, consistency is established. Suppose that both approved texts are ready, the desks have authority to issue them, the required staff and channels are available to both in the agreed release window today, and these are the remaining release conditions. The desks can jointly issue the consistent instructions in that window. If one desk has no usable route to the shift before the deadline, joint issue in that window is unavailable even when the instructions agree. A claim that the shift actually received them needs evidence of delivery.
The general result is a connected account of the conditions for one receiving action. The principle about agreement applies across disciplines. Editorial work makes the relation concrete through the applicable clauses, a local release procedure can further restrict which editions qualify, and one actual issue supplies evidence about identified texts and reviews. A larger service could still be examined on one occasion. The number or size of its desks assigns no level of model abstraction. Keep the account's declared types and ranges when applying the method to a different action. C.39.QR:4.1 gives the return from an example to that commission.
Test the joint conclusion
State how the claims from the models are to be read together. Align such matters as units, conditions, time, configuration and whether a value was stipulated, observed or predicted when the conclusion depends on them. Check whether the commitments can all hold in the same case. Pairwise compatibility can leave the whole set inconsistent. If no case satisfies all the commitments, trace the conflict to the models or their interpretation. If information is missing, identify the premise or correspondence needed to settle compatibility.
To establish that an outcome is possible under these models, show that at least one jointly admissible case has that outcome. You can exhibit such a case or prove that it exists. If the recipient needs a setting they can actually use, recover one and check it against the conditions. To guarantee the outcome under the stated conditions, establish that at least one case is admissible and that every jointly admissible case has that outcome. One admissible exception defeats the guarantee.
Ask whether the outstanding uncertainty affects the decision you owe. Two interpretations can yield different estimates and still put every admissible result on the same side of a decision threshold. That can settle the choice while the estimate remains open. If admissible interpretations give different choices, recover the convention, observation or model relation that separates them. When the set of possible interpretations is itself open, qualify the answer to the ones examined.
A claim about a candidate is distinct from a claim about how an actual system performed. To use a test result from an observed system, state what was observed and which target claim it supports under which conditions. B.5.MR supplies the test for a further claim that joint use strictly refines the earlier model. A gain in interpretation can occur while the set of eligible candidates stays the same.
Make the receiving use reproducible
Ask what the successor will need to do. To read an existing result, they need the governing types, meanings, constraints, editions and consequential links. A metamodel can supply conventions that determine which models are admissible. A megamodel, in this handover use, makes the related models and the relevant links to their governing models recoverable. A reference to an accessible, identified edition suffices when it gives the recipient what they need. If the governing conventions may themselves change, preserve the grounds for the relevant higher-order choices.
To repeat, adapt or examine the original derivation, identify its production method and the inputs and assumptions on which it depends. To check its conclusion independently, establish the common target, conditions and meaning of the result. A missing premise leaves the original derivation incomplete. The conclusion can still be established by another sound method. For a claim about every admissible case, one counterexample that meets its conditions refutes the claim. A glossary can settle what an estimate means while leaving the successor unable to recompute it. When one source supplies a well-understood method, name the applicable edition and the values fixed locally.
To act on the result, the recipient may additionally need the resources, capability and authority for the work. An assignment, where relied on, is a relation with a system as its holder under A.2.1. Handing over an account does not establish that anyone has performed the work.
Reopen only the dependent conclusions
When an observation, model edition or interpretation changes, follow the consequential relations to the conclusions and actions that used it. Tell their users what changed and which use must be reconsidered. Test the revised result under the conditions that made the change relevant. If an earlier model is retained as evidence of a past decision, keep its effective edition identifiable.
Archetypal Grounding
Two accounts bear on the same stipulated preference relation over three alternatives. The first reports that A is preferred to B, the second that B and C are tied. With a shared population, comparison conditions and the premise that these judgments are readings of one complete and transitive weak order, the two claims imply that A is preferred to C. If a blank in the second table means “uncompared”, the tie is missing and the conclusion is open. The two files can remain as they are. A recipient needs the applicable interpretation of that entry and the grounds for the common relation. Observed human choices require evidence for any claim that this weak-order interpretation fits them.
An engineering team receives a design and an annual maintenance estimate of €12,000 for one service visit. The contract file identifies two possible charging arrangements. One charges €12,000 per visit. The other charges €12,000 per year for up to two visits. The signed schedule that selects the arrangement is missing. Both account for the old figure. For two visits next year the estimates are €24,000 and €12,000. The team can confirm that the service charge fits a €25,000 annual allowance under either arrangement, provided those are the only possible terms and the allowance covers that charge alone. With an €18,000 allowance, one arrangement fits and the other exceeds the budget. The team needs to establish which arrangement applies. Reconstructing the original estimate or pricing a third visit would also require further information. A wider commission to account for the system throughout its life may require additional engineering coverage under SYSE.7.
Bias-Annotation
Readers commonly give precedence to the most precise-looking model. A model precise about functional behavior can omit a cost, construction or usage premise on which the recipient's decision turns. Recover the missing premise before preferring a format.
Conformance Checklist
- The intended result, the modeled entities, each model's contribution and the indispensable relations are recoverable.
- The account tests whether the models admit a joint case. A possibility claim has an example satisfying the joint conditions or a sound argument that such a case exists. A guarantee covers every jointly admissible case and at least one such case exists. An unresolved value can still settle the receiving decision if every admissible value yields the same choice. An inconsistent set is reported as a conflict.
- Material supplied at handover is sufficient for the recipient's actual use, including the production method for repeating, adapting or checking its derivation, and the grounds of comparison for an independent check.
Common Anti-Patterns and How to Avoid Them
A common title, shared file or new graph can hide a missing relation. Read its consequential links in ordinary terms and test the conclusion they are claimed to support. A publisher can also provide every governing convention while omitting an entire aspect the decision needs. Check coverage against the original assignment.
Consequences
A recipient can identify why a joint conclusion holds, which question remains open and which work must be repeated when a premise changes. One usable edition reference can support several models.
Architectural Rationale
The needed method concerns the relations required by the receiving use. C.13 governs a separate claim of collection or composition, and A.22 governs identity for a selected structure. The same work can be carried through in ordinary prose, a project account or a maintained registry.
SoTA-Echoing
Megamodeling in model-driven engineering makes models and typed relations, including conformance, available for navigation. Architecture-description practice uses stakeholder concerns to select views and viewpoints to interpret them. A model register can serve a successor who needs to retrieve the governing edition. For a decision that depends on several views, even a complete register leaves open which conclusions their commitments support together. Section 4.2 tests the joint inference. Section 4.3 distinguishes the inputs needed to repeat its derivation from the grounds for checking the conclusion independently. Revisit the selected views and links when a new decision needs a different premise or when a change of convention alters a premise already in use. Bézivin, Jouault and Valduriez, On the Need for Megamodels · ISO/IEC/IEEE 42010:2022
Relations
C.37 governs co-use for one action. C.37.MP relates different uses of representations of the same Method description or candidate account. C.2.1 supplies the identity of each model episteme, E.17.0 governs viewpoint and view when asserted, B.5.MR compares model commitments, and SYSE.7 applies this method in engineering.
C.37.MM:End
Last Updated: 2026-11-15 — this section last modified in upstream FPF commit c3b97217 (github.com/ailev/FPF)