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 project-system choice and domain boundary and obtain the relevant specialist result. |