Library / Engineering DPF Suite Reference
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 11:52:20 UTC · snapshot created 2026-10-03 11:53:41 UTC · last check 2026-10-03 12:10:10 UTC

When source material should change a pattern language

Suppose a handbook, a research paper and an existing repertoire partly agree, but a recurring user still cannot recover a condition needed to act. The optional PLUS-ME production MethodDescription explains how to turn those sources and current supply into usable Method-description knowledge in pattern-language form. It describes prospective performance without establishing a decomposition into part Methods; use ME.7/B.1.5 when a receiving use depends on that relation. Trial evidence is still needed to judge how that Method performs in practice.

Begin at the missing result. ME.4 recovers what each documentary source actually contributes. ME.21 uses the recovered meanings to decide what the existing repertoire already supplies and what should be added, changed or left at the source. ME.23 organizes the needed descriptions and neighboring contributions around users’ questions and the results they consume. ME.24 tests a promised source-to-language answer by reconstructing its action, conditions and source basis, then returns a loss to the affected description, allocation or language relation. A sufficient source passage or single MethodDescription is a valid stopping point.

For example, a handbook permits reusing a review after a display-only change, while a paper adds that the reviewed claims, question and qualification window must still match. ME.21 keeps that condition with the checking guidance already supplied by ME.12. If the language says only “reuse for display changes”, ME.24 identifies the missing condition and returns a description repair. Later, loss of access to an argument required for a new recheck can block that recheck while an earlier supported result retains its historical basis.