STR.13:4.3 - Change the right thing

Identify whether the proposed change alters reusable operations, dependencies, entry or stop rules, or only their description, representation or support. A clearer sentence is not automatically a new Method; a reordered decision rule can be a real semantic change even if its description needs only one sentence.

For a proposed variant, preserve the earlier way or source account, what is retained and changed, why it was changed and the intended situations. State which evidence for the earlier way still applies and what remains unsupported for the changed one. A traceable entry can preserve the proposal as a candidate and complete the present maintenance task.

When later users need to distinguish an identified FPF U.Method from a candidate proposal, use ME.15’s independent admission step under A.3.1. Here admission means establishing a reusable way of doing, the kinds of participants it is for, its applicability and preconditions, intended result or preserved condition, and limits or stops. Establish that basis for the changed way itself or retain its candidate status. ME.14 answers the separate practical question of whether using or changing the way is worthwhile for this strategic decision.

For a non-variant change, name the actual object, the affected claim or edition and the needed maintenance action. Repair an ambiguous instruction where the ambiguity occurs and inspect its affected uses.

Obtain the relevant Method Engineering result when the open question is how to construct the method, whether its operations are coherent or whether it fits the intended conditions. Keep that answer distinct from section 4.2’s comparison of its practical worth.