ME.Preface:7.7 - Architectural Rationale and source comparison
Method Engineering keeps SME’s situation dependence and deliberate construction of reusable ways of working. PLUS-ME changes neither premise. It selects one profile in which patterns expose problems, forces, actionable contributions and useful relations, while Method identity and composition remain separately governed. The reuse unit is therefore not indiscriminately a source slice: it can be an independently qualified smaller Method, a description contribution or a neighboring non-Method answer.
This explains the distinct production results. Recovery must remain faithful even when allocation later rejects a proposal. Description comparison must not be replaced by either a cross-use representation profile or a judgment of Method worth. Language architecture must make material relations useful without creating parthood. Reconstruction must be able to find a missing contribution before a contradictory maintained claim and its owner are already known. ME.4, ME.21, ME.22, ME.23 and ME.24 keep these differences actionable; none requires an obligatory pipeline.
The following sources supply specific questions and alternatives, not a proof that this profile is universally best:
| Source and role | Contribution and limit in this profile |
|---|---|
| Ralyté, Deneckère and Rolland, generic SME and Map, 2003 — historical anchor | On-the-fly construction and intention-sensitive navigation are prior art. Do not contrast PLUS-ME with an exclusively up-front history of SME. |
| Gottschalk et al., continuous composition and enactment, 2022/2023 — implemented contemporary alternative | Continuous situation-specific composition already joins construction with enactment. This profile changes the useful knowledge and return arrangement, not by itself its effectiveness. |
| Wilke et al., Method Engineering review, 2024 | Diverse definitions and adaptation routes justify checking the live field before extraction. One database review does not settle a universal Method ontology. |
| Stacey et al., Methods as engineering knowledge, 2025 | Preserve use conditions and practitioner knowledge around procedural guidance. These questions do not automatically become mandatory fields or Method parts. |
| Doellken, Nelius and Matthiesen, ACAP analysis, 2024 | Distinguish attention, comprehension, application and performance in a description’s use. The sheet-metal-design study does not establish a universal measure or isolate every content contribution. ME.22 adapts the distinction. |
| Veloso, Varajão and Moreira, Method selection in information systems, 2026 | Interacting project, team, organizational, Method and environment conditions can change selection. Their synthesis and focus groups do not establish PLUS-ME effectiveness. |
Alexander et al.’s A Pattern Language (1977) supplies the historical problem-first, connected-guidance idea. Minsky’s frame account (1974) connects situation knowledge, expectations and adaptation. The architectural analogy drawn here concerns those knowledge-use roles; historical descent of pattern languages from frame systems is not established by it. Declarative and case-management approaches, including CMMN 1.1, remain operational comparison targets, not the ontology adopted by this language.
The selected alternative is a profile within Method Engineering because its general qualification, architecture, representation and assurance questions remain shared. A separate framework would need a different justified field promise. A prose-only synthesis remains a serious lower-maintenance option; a fixed route remains legitimate under stable conditions. Reopen the profile choice when current supply removes a distinct result, reconstruction fails for a promised use, source conditions change, or the maintenance burden defeats the practical gain.