SYSE.15 - Choose and Refresh the Engineering Methods Needed by a Project
Status: Stable
SYSE.15:0 - Use This When
Use this pattern when an engineering project has assumed that a lifecycle, standard, model-based framework, toolchain, or AI workflow supplies the whole engineering Method, yet practitioners cannot say which reusable Methods the project’s Agents should apply in Work to obtain the results their current decisions need. Use it also when a local automation makes one task faster while integration, assurance, rework, or the engineered System shows no benefit.
Begin with one recurring engineering result that is missing, unreliable, or too costly. State the actual System or intended System referent selected for engineering, its relevant use and conditions, and the decision that needs the result. For a creator, retain the products or future uses that ground its required contribution. Then identify and compare reusable ways of obtaining that result without importing an entire source bundle.
The first useful result is a decision account for the project’s engineering Method repertoire. It states which Methods are retained for the named results, which alternatives or gaps remain, where each Method applies, which relations among Methods are supported, what evidence informed the choice, and what change reopens it. The account is an episteme about the choice. MethodDescriptions, capability and provider claims, Work plans, and performed Work retain their own identities and grounds.
Use direct FPF patterns when the question concerns one already identified Method or MethodDescription. Use
SYSE.20 when the difficulty is a conflict among simultaneous Methods or Work wholes, SYSE.12 when the missing
result is an engineering-platform capability, SYSE.21 for wider cultural continuation, and SYSE.24 when the
project must choose how to obtain a needed engineering result.
SYSE.15:0.1 - Precision Restoration
| Name in this pattern | What it denotes |
|---|---|
| engineering Method | A reusable way of obtaining or preserving a named engineering result under stated participant meanings, conditions, applicability, and limits. |
| MethodDescription | An episteme about one identified Method that states a substantive way-of-doing claim. A standard, handbook, program, diagram, or workflow qualifies only when A.3.2 admits it. |
| recurring engineering result | A result needed in more than one relevant Work situation—for example, an operating-situation account, prediction, design choice, changed System, integration observation, configuration basis, assurance result, or release decision. The current claim must name its kind and use. |
| project conditions affecting Method choice | The actual System kind and use, or the intended System kind and use stated in the project-system choice account, operating environment, physical phenomena, configuration, evidence and authority needs, provider conditions, decision horizon, and losses that must be protected. These conditions form the comparison boundary. |
| Method-repertoire account | The episteme returned here: current Method choices, alternatives, exclusions, evidence, limits, supported relations, gaps, and reopen conditions for named project conditions. Use G.5 separately when a later selector needs a formal shortlist or joint-use set. |
| unresolved Method cue | A source phrase such as model-based process, AI workflow, agile, or systems approach whose reusable action, participant meanings, intended result, or boundary has not yet been recovered. |
| Method classification and specialization | A Method can meet several kind criteria and therefore have several broader Method kinds. This does not make the broader kinds parts, stages, or providers. |
| Method participation in whole Methods | One Method can contribute to several whole Methods. State each whole–part relation separately; shared participation does not identify the wholes with one another. |
| result use and dependency | A result from one Method can inform a decision involving another. That relation neither makes one Method part of the other nor proves a first–then Work order. |
| Work order and concurrency | Dated Work can overlap, recur, or follow a case-specific order while enacting the same or different Methods. A lifecycle diagram or table order does not establish that timing. |
| capability, assignment, provider, and platform | Different claims about which Agents can perform Work, who is assigned, how a result is obtained, and which supporting Systems are available. None follows from selecting a Method. |
| cultural prevalence | Claims about generation, transmission, recognition, selection, retention, or loss of Method variants in a population. One project choice establishes none of them. |
During this choice, each candidate Method is a project Method-of-interest because its identity, applicability, comparison, and retention are current project questions. That designation is project-relative, not a Method kind. After the choice, the Method’s enactment in engineering Work, any later Method-development Work, the Method-development Method, and the Agents and Systems involved retain separate relations.
Identify who chooses the repertoire and who performs Work with its Methods.
SYSE.15:1 - Problem Frame
Systems Engineering is not one Method. Engineering different Systems—for example, a software-intensive controller, ship, building, electrical installation, medical device, or experimental machine—can require different physical models, trials, specialist evidence, permissions, platforms, and release Methods. Useful Methods can be shared across those applications, but domain phenomena and consequences change how some Methods are performed and checked.
An Agent that is also the actual System designated as project system-of-interest may enact an operating Method. For a System that does not yet exist, state the expected operating Method against its intended-system designator. The project also uses engineering Methods to obtain results such as an account of intended use, a design, a created or changed System, an integration observation, an assurance result, or a release decision. An operating Method enacted by the System and an engineering Method used to create or change that System answer different questions, even when one project must understand both. A non-agentic System has behaviour and functions but performs no Method.
Methods can stand in several relations at once. A trial Method can belong to several Method kinds, participate in several whole Methods, supply results to several decisions, and be enacted concurrently with modeling or implementation Work. Distinguish these relations when selecting or combining Methods.
SYSE.15:2 - Problem
A named framework makes Method choice look easier than it is. A standard can contain useful obligations and descriptions without showing which Methods work together or whether they fit this project. A lifecycle can show contributions while falsely suggesting one pass. A connected model can improve some decisions while hiding missing physical evidence for others. An AI Agent can shorten generation Work while review, integration, and assurance become the limiting contributions.
The opposite error is to invent every Method afresh. Sources such as standards, handbooks, engineering specializations, tool-supported practice, and observed successful or failed Work contain recoverable Method candidates. Retain useful distinctions while testing source-specific elements—such as authority, vocabulary, stages, roles, or artifacts—under current FPF kinds instead of importing the source whole.
SYSE.15:3 - Forces
Recurring tensions include:
- Reusing familiar Methods saves search and learning effort; source authority and internal coherence do not prove fit for the current result.
- A bounded Method comparison can be manageable; false decomposition can destroy a working whole or invent Method parts that do not obtain.
- Shared engineering Methods reduce coordination cost; specialist physics, evidence, permissions, and failure modes still change the move in some domains.
- Representative trials cost time and equipment; document completion, declared conformance, and local task speed are weak substitutes for System and decision consequences.
- Method choices need a current answer while tools, sources, Agent capabilities, provider conditions, and project constraints continue to change.
- A project can justify a local Method choice without proving wider cultural prevalence or universal superiority.
SYSE.15:4 - Solution
Choose and refresh engineering Methods from the results the project needs and evidence from representative Work. Identify Methods before comparing them, preserve every relation that matters, and return capability, provider, platform, or cultural questions to their own decisions.
Reuse an existing Method choice when its reasoning and qualified evidence remain sufficient for the same required result and conditions. Add only what an unresolved choice, interaction or realization gap needs. If the reusable way itself must be created or changed, obtain the relevant Method Engineering contribution before relying on it as an available Method.
Local mantra. Start from a needed engineering result. Recover reusable Methods from sources and Work. Compare them under the same project conditions. Keep classification, whole–part structure, result use, and Work timing separate. Exercise the Methods together where interaction can reveal loss. Retain, replace, develop, or leave a gap with evidence and a reopen condition.
SYSE.15:4.1 - Perform the Move
- Name the engineering result and receiving decision. State the actual System or intended System referent selected for engineering, relevant use, configuration, conditions, horizon, account users and the first recurring result whose Method is missing or doubtful. For a creator, keep its product-use grounds and local acceptance identifiable.
- Recover candidate Methods from Work. Inspect representative Work, including successful, failed, and difficult occurrences. For each candidate, recover the reusable action, generic participant meanings, conditions, intended result, applicability limits, and evidence. Keep actual performing Agents, assignments, capabilities, and authority with the dated Work.
- Recover candidates from sources without importing the source whole. Inspect relevant sources—for example,
standards, handbooks, lifecycles, model-based frameworks, AI workflows, or local traditions. Apply
A.3.1before identifying a Method andA.3.2before relying on a MethodDescription. Keep an unresolved cue when the reusable way cannot yet be stated. - Compare the same result under the same conditions. Hold the result, System kind identified for the engineering subject, use, configuration, evidence needs, and protected losses stable while varying the Method. A new tool, description, assignment, or parameter is not automatically a new Method. State the criterion that will prefer one feasible option, including continuing with an adequate existing Method. Compare the work needed through the receiving result, including material preparation, adaptation, review and integration costs.
- Test whether specialization changes the work. Compare a narrower engineering Method with the broader FPF or DPF move at comparable effort. Retain the specialization only when it changes what practitioners notice, decide, do, obtain, check, or use as a stop or return, and that difference is useful and warranted for this domain. A domain noun or extra example is insufficient.
- State each Method relation separately. Record broader-kind classifications, participation in whole Methods, alternatives, refinements or replacements, result-use dependencies, and compatibility only when their own conditions obtain. Do not infer any of them from a list, vertical diagram, shared source, or Work order.
- Examine an interacting engineering slice. Reuse sufficient evidence from bounded representative Work in which candidate Methods interact—for example, modeling, implementation, integration, configuration, assurance and release around one change. Select new Work when a remaining interaction question warrants it. Examine the needed decisions and System effects together with integration loss, rework, elapsed time, capability, platform constraints and protected characteristics.
- Make the repertoire decision. The authorized Agent records which Methods are retained now, retained as alternatives, replaced, excluded for this use, proposed for development, or still unresolved. Explain the selected disposition from the criterion and grounds, including the accepted burden or loss. If a retained Method lacks a capable Agent, provider, platform, or assignment, record that separate gap and send it to the appropriate capability, provider, platform, or obtaining-arrangement decision.
- State evidence, currentness, and return conditions. Give each relied-on claim its actual epistemic status— for example, project observation, qualified expert estimate, institutional description, academic or press visibility, declared conformance, or evidence of enacted practice. Reopen only when a changed result, source, Method, project condition, capability, provider, or platform can change the decision.
The numbered steps explain the Method. Source inquiry, modeling, realization, integration, assurance, platform development, and Method development can overlap and recur; choose Work order from the actual dependencies.
SYSE.15:4.2 - Record the Result
| Field | Required content |
|---|---|
| use boundary | Actual System or intended System referent selected for engineering, use, configuration, conditions, horizon, account users, recurring results and protected losses; product-use grounds and bounded acceptance when it is a creator. |
| Method choices and open cues | Methods retained now, alternatives, replacements, exclusions, proposed developments, unresolved cues, and relied-on MethodDescriptions or direct sources. |
| Method identity | For each Method: reusable action, generic participant meanings, intended result or preserved condition, applicability, and limits. |
| Method relations | Supported classifications, whole–part participation, alternatives, refinements or replacements, result uses, and compatibility claims. |
| representative Work evidence | Work situation, performing Agents, assignments, enacted Methods, relevant Systems, results, evidence limits, System consequences, integration loss, cost, time, capability, and platform observations. |
| separate realization gaps | Missing capable Agent, assignment, provider result, platform capability, permission, evidence, or authority; receiving decision for each gap. |
| decision and currentness | Authorized choosing Agent, retained and excluded Methods, reasons, accepted losses, source status, currentness window, and material reconsideration conditions. |
Use a G.5 shortlist or joint-use set only when a later selector needs that formal result.
SYSE.15:4.3 - What Changes in Practice
Practitioners can explain which reusable Methods the project’s Agents should apply in Work to obtain each needed engineering result, what representative Work has produced, why the Methods fit this System and use, how they relate, and which evidence, capability or provider result is still needed. Use standards as scoped sources and tools in Work; compare local speed with integration and System consequences. The account can change while the Method remains the same: a changed assignment, tool or publication does not by itself change the reusable way of doing.
SYSE.15:5 - Worked Case: Methods for a Heat-Pump Controller Change
An engineering team is changing the controller of an occupied-building heat-pump plant. Its current process description points to a V diagram, a Systems Engineering handbook, a simulation repository, an issue tracker, a hardware-in-the-loop bench, an AI coding service, and a release checklist. The V diagram, handbook, and checklist are descriptions. The repository and issue tracker store or carry records. The bench is a platform System. The AI service may be an Agent, provider resource, or tool depending on the actual arrangement and agency. Calling this heterogeneous set our model-based process does not make it one Method.
The engineering lead acts as the Agent authorized to choose Methods for this controller project. Release authority remains with another Agent. The team starts from recurring results rather than the list of assets:
| Needed result | Candidate or retained Method | Evidence and current gap |
|---|---|---|
| Operating situations and protected room-temperature and equipment conditions | Recover operating situations, affected Systems, and required effects before choosing a controller concept. | Existing operating records cover normal weather; rare grid events remain an explicit gap. |
| Plant-response prediction | Identify physical parameters and simulate the heat-pump, building, sensor, and controller interaction. | Earlier predictions omitted measured sensor latency. |
| Controller implementation candidate | Implement the controller change from an existing template, or generate a bounded implementation candidate with AI. Independent implementation review remains a separate Method. | Use AI is not a Method. Recover the reusable implementation ways before comparing them; review supplies its own result. |
| Integration observation | Exercise the actual controller interface and plant model on the hardware-in-the-loop bench. | Bench time is scarce; occupied-building trials require separate safety and release conditions. |
| Configuration, assurance, and release decisions | Use the corresponding configuration, assurance, and release Methods for the identified controller and plant conditions. | None of these decisions follows from the V diagram or a green code check. |
The hardware-in-the-loop trial Method meets both experimental-engineering and cyber-physical-integration Method criteria. The team also uses it as a part of two stated whole Methods: controller integration and release-evidence development. Those classifications and whole–part relations are recorded separately. The modeling result informs the controller choice, but that result use does not make modeling a stage of one universal lifecycle.
In a representative three-day slice, an AI coding Agent performs bounded generation Work, a controls engineer reviews the candidate, and a test engineer performs the bench trial. If the coding service lacks enough agency to perform the assigned Work, it is recorded as a tool used by the controls engineer instead. The trial reveals sensor latency that destabilizes the candidate despite an acceptable simulation prediction. The release Agent withholds the candidate, and the controls engineer revises the physical model. Faster code generation did not shorten the limiting integration and assurance Work.
The next choice is how to produce a corrected implementation candidate for the revised latency model. The lead compares continuing with the team’s established implementation from a controller template and using bounded AI generation. Both must serve the same controller interfaces and required response, and both feed the same independent review and hardware-in-the-loop qualification. Neither option resolves scarce bench time.
For this illustrative comparison, assume a qualified controls engineer is available and the template’s applicability to this correction is supported. The team already knows how to use it. The AI alternative is also available, but requires preparing its context, examining unfamiliar generated constructs and adapting them to the controller interfaces. The lead’s qualitative estimate is that this additional preparation, review and integration work exceeds the generation effort saved for this correction.
The lead’s rule protects the required candidate quality and physical-evidence conditions, then prefers the option with lower total engineering effort for this correction. On the stated basis, the lead retains implementation from the existing template and defers AI generation. The accepted loss is slower initial code production in exchange for less preparation and checking of unfamiliar implementation choices. Independent review and latency-sensitive integration checks remain necessary for either option. A changed template, loss of the qualified engineer, or a better-supported AI alternative with lower full continuation cost reopens this choice. The corrected implementation still has to be produced and qualified.
The repertoire account keeps operating-situation recovery and linked concept development for their named results, carrying forward the rare-grid-event gap. Physical modeling and hardware-in-the-loop trial remain needed to address the exposed latency interaction. Configuration, assurance and release still supply their separate decisions. The account retains an occupied-building trial only under the stated safety, plant-state, weather and release conditions. The V diagram remains an overview. The phrase AI workflow Method remains unresolved; the identified bounded generation Method is a deferred alternative.
Scarce bench time leaves several possible repairs. The team can use OPS.11.1 to compare available time with
already assigned work and revise allocation under the existing authority. It can also compare trial Methods
that occupy the bench for less time while preserving the required integration result and evidence conditions.
A shorter trial that misses the sensor-latency failure would not serve the present use. New bench provision or a
different way of obtaining the result belongs to SYSE.12 or SYSE.24 when that contribution is needed. None of
these options is selected merely by observing scarcity.
Simultaneous modeling, generation, review, trial, and assurance conflicts go to SYSE.20. Evidence of wider use,
selection, retention, or loss can later inform SYSE.21; this project choice does not establish a cultural trend.
When the full pattern is unnecessary. If one identified Method already supplies a well-understood result for the same System and conditions, and no interaction, specialization, capability, provider, or currentness question can change the decision, use that Method and its direct evidence patterns.
SYSE.15:6 - Bias Annotation
Sources such as official standards, handbooks, maturity schemes, curricula, publications, and project declarations provide evidence about descriptions or institutional activity. Evidence of enacted Work and practical worth requires observations of the relevant practice and consequences. When broader observations are unavailable, use a bounded expert estimate and state its population, period, basis, uncertainty, and application limit.
Check software and AI evidence against the receiving engineering application. Fast feedback can transfer without identical cadence, physical evidence, release authority, or assurance. Specialist Methods—for example, safety, security, legal, manufacturing, maintenance, clinical, maritime, electrical, or building Methods—remain where their domain changes the Work.
SYSE.15:7 - Conformance Checklist
- The System to be created or changed, recurring engineering result, receiving decision, conditions, and protected losses are stated.
- Every Method remains distinct from descriptions, tools, Work, performing Agents, assignments, capabilities, evidence, provider arrangements, and cultural relations.
- Each Method has a reusable action, participant meanings, applicability, intended result, and limits.
- A narrower engineering Method is retained only when its specialization changes useful and warranted action at comparable effort.
- Classification, whole–part participation, alternatives, replacement, result use, compatibility, and Work timing are stated separately.
- Evidence from representative engineering Work addresses the relevant Method interactions and their System, integration, assurance, cost, time, capability and platform consequences. Further Work is selected only for a remaining question that warrants it.
- Missing capability, assignment, provider, platform, permission, evidence, or authority is returned to its own decision rather than hidden as a Method defect.
- Project evidence and expert estimates remain distinct from visibility, declared conformance, and cultural prevalence.
- The account names retained, replaced, excluded, proposed, and unresolved Methods with material reopen conditions.
SYSE.15:8 - Common Failures and Repairs
These recurring substitutions hide a Method choice or send the project to the wrong next decision:
| Failure | Repair |
|---|---|
| Framework status stands for practical worth | Recover the Methods actually used and test their fit and consequences separately. |
| Tool or notation stands for Method | State the reusable action and result; keep representation, mechanism, tool, and Work separate. |
| A stage, role, artifact, or meeting is called a submethod | Apply Method identity and whole–part tests; retain the item under its actual kind when the Method claim fails. |
| Lifecycle order stands for Method architecture | State classifications, whole–part relations, result uses, compatibility, and actual Work timing independently. |
| Every result is expected from one connected model | Name the decisions each model supports and the physical, specialist, or operating evidence it does not supply. |
| AI speed stands for engineering improvement | Compare generation gains with review, integration, assurance, maintenance, and System consequences. |
| Missing capable Agent or platform is called a bad Method | Keep the Method choice and return the separate capability, provider, assignment, or platform gap. |
| Visibility stands for prevalence | State observed use or a bounded expert estimate; publication and teaching coverage establish neither enactment nor retention. |
| Generalize one application profile to all engineering | Preserve the engineering subject, product-use grounds and domain boundary and obtain the relevant specialist result. |
SYSE.15:9 - Consequences
The project gains an inspectable repertoire without repeatedly importing or rejecting whole frameworks. Useful combinations become visible, representative Work exposes limiting contributions, and a changed source or condition reopens only the affected choice. Capability, provider, platform, and culture decisions receive named gaps instead of Method-shaped ambiguity.
The cost is real comparison and trial Work. Some source cues remain unresolved, some Methods cannot be safely decomposed, and evidence from one project may not transfer. Recording those limits is more useful than hiding them behind a universal process name.
SYSE.15:10 - Rationale
FPF supplies general Method identity, descriptions, specialization, whole–part relations, Work, cultural change, and source-use discipline. Systems Engineering adds the recurring subject-specific question: for the actual or intended System referent selected for engineering under these physical and organizational conditions, which reusable Methods should the project’s Agents apply in Work to obtain the connected engineering results— for example, concept, modeling, realization, integration, configuration, assurance, release, or continuing-change results—and what did representative Work applying those Methods actually produce? Starting from those results preserves valuable engineering specializations. Representative Work tests the Methods together, because a locally faster activity can move cost or failure to integration, assurance, operation, or maintenance. The resulting choice remains bounded to the project rather than being advertised as a universal methodology or cultural fact.
SYSE.15:11 - SoTA and Source Use
Working question: How should an engineering lead choose and refresh a sufficient repertoire for the project’s recurring results, while preserving interactions and the conditions for performing the Work?
The selected line starts with an adequate existing choice and adds only the missing comparison or connection. A developed situational Method Engineering approach is a serious alternative: it can select, adapt and connect reusable ways for the same project purpose. Use its result directly when it already answers the choice and realization questions. When the reusable way is missing, use the qualified Method Engineering contribution named in :12 to construct or improve it.
The narrower contribution here is useful when known Methods are hidden inside a heterogeneous framework or tool bundle. Steps 2–6 identify the ways and their distinct relations; steps 7–9 connect interaction evidence to a choice and return any separate realization gap. For this use, the team accepts making that comparison without constructing a new composite Method or adopting a source’s entire apparatus. It still has to establish the relations and grounds it needs.
The :5 choice works the trade-off: the same implementation result, quality and physical-evidence conditions govern both alternatives. The lead accepts slower initial code production to avoid greater estimated preparation, review and integration effort. The extra repertoire account earns its cost by changing the retained implementation Method and separating the remaining bench-time question. An unchanged adequate answer takes :4’s direct route.
| Source answer considered | Disposition and operative use | Scope and limit |
|---|---|---|
| Henderson-Sellers and Ralyté 2010, §7.1–7.3; Tsai, Zdravkovic and Söder 2023, §§2.3–4.3, §5.2 and §6; Bender 2024, §§3.2–4.3 and §6 | Adapt requirements-led selection, situational alternatives and explicit dependencies in steps 1/3/4/6. The developed treatments can supply the construction returned by :12. | The 2010 survey is a historical anchor. The later DBE and business-process treatments demonstrate domain-specific choices; their modules, indicators and role meanings do not establish an engineering-wide repertoire or transfer automatically to physical Systems. |
| Ralyté, Koutsopoulos and Stirna 2025, §§2.2–4.1 | Adopt the distinction among internal correctness, contextual fit and worthwhile use; adapt proportionate assessment in steps 4/7/8. A correct description still needs grounds for the project’s choice, including training and use effort. | These are modeling-method recommendations. Their allowance for simpler early validation supports proportionate work; it does not qualify a physical controller or prove the benefit of this repertoire. |
| DORA continuous integration, change approval and platform engineering; Zampetti et al. 2022 | Adapt timely feedback and enabling capability while preserving different physical and software contributions in steps 6/7 and :5. The latency failure makes that connection consequential even when generation is faster. | The software guidance and heterogeneous cyber-physical cases support qualified contributions. They do not select one cadence, approval arrangement or automation level for every System. |
| Becker et al. 2025, v2 abstract; METR self-report study, May 2026 | Adopt the distinction between observed completion time and perceived or reported gain in steps 7/9. The early-2025 coding experiment reported a slowdown despite perceived speedup; the later survey measures reported gains. | The experiment’s population and tools bound that observation; the 2026 convenience sample and counterfactual self-reports do not establish realized project productivity. Neither result selects the controller Method without its own comparison. |
| METR task-substitution note, May 2026; Pradas Gomez et al. 2025; Luke et al. 2026 | Adapt the distinction between task speed, changed task mix and useful value, and consider proposed human/tool/AI allocations against capability and workflow fit in steps 4/7/8. Section :5 compares the full continuation and retains its separate performers and authority. | The task-substitution argument is theoretical under simplifying assumptions. Conceptual allocation proposals, survey findings and one automotive organization’s interview-based recommendations are different evidence kinds; they are not controlled measurements of the proposed arrangements’ effectiveness. |
Reopen the affected comparison when qualification no longer covers the required result, an interaction changes the protected outcome, realization conditions change, or a better applicable Method or different preparation and transition burden can reverse the choice. Use available qualified evidence; obtain further inquiry only when an attainable answer can change the warranted continuation. A new source or tool matters through that changed comparison.
SYSE.15:12 - Relations
A.3.1identifies each Method;A.3.2identifies a MethodDescription;A.15.1governs dated Work. A source, description, assignment, capability, tool, or run does not occupy the Method position.A.15.6governs the project-relative Method-of-interest designation. It distinguishes a Method enacted in the subject’s operational Work, a Method used to create or change a System, a solution Method, a Method-of-interest, and a Method used to develop that Method-of-interest.A.3.1distinguishes several broader Method kinds from participation in several whole Methods.A.22,B.1.5, and direct relation patterns still govern selected structures and whole–part claims.C.32.MWAkeeps Method classification, Method holarchy, result dependencies, Work order, provider or enabling Work, capability development, and cultural change as different structures that may all be needed in one case.E.8:4.1.3tests whether a narrower engineering contribution changes useful and warranted action at comparable effort. It neither selects the Method nor proves practical worth.- Apply
E.23when a named Method itself must be improved. In this pattern, the Agent choosing a bounded engineering Method repertoire performs the decision Work described here. When a Method must be created or changed, use the applicable Method Engineering result or a qualified direct source. G.5supplies a shortlist or joint-use set only when a later selection needs that result. It establishes neither Method identity nor actual capability, compatibility, enactment, or uptake.- Route platform, simultaneous-Work, cultural-continuation, and obtaining-arrangement questions to the Agents
applying
SYSE.12,SYSE.20,SYSE.21, andSYSE.24, respectively. Their co-use creates no automatic temporal order. - Application Methods—for example, organization-change, operations-management, software, electrical, medical, maritime, or building Methods—retain the Systems they create or change, their evidence, authority, and applicability. Shared vocabulary does not make them parts of one universal process.