Systems Engineering and Decision Science Analysis

Model and evidence

Systems engineering owns lifecycle integration and interfaces [EV-BOUNDARY-2026-5E8B]. Assurance cases link claims, arguments, and evidence [EV-SYSTEMS-2026-22C8]. Value-of-information analysis measures expected decision improvement, not information volume [EV-SYSTEMS-2026-A730].

Counterevidence and methods

Assurance cases can become persuasive paperwork; evidence quality is not assured by structure. Quantitative decision models require contentious probabilities and utilities. Methods include interface analysis, traceability, claims-argument- evidence review, uncertainty/sensitivity analysis, VoI, and verification plans.

Coverage, gap, and challenged assumptions

This body already owns integration, lifecycle, risk, evidence arguments, and decision value. It most directly challenges the need for a new “engineering” field. Its communication methods may be too heavyweight for routine work.

Discriminating experiment

Compare a lightweight assurance-case handoff with the proposed profile, measuring decision accuracy, evidence gaps, authoring cost, and update cost.

Confidence and limits

Very High overlap confidence; Medium practicality comparison confidence.

Ten future questions

1. Which handoff claims require assurance arguments?
2. What risk threshold justifies formal structure?
3. Can evidence quality be scored independently of rhetoric?
4. What is the VoI of another handoff field?
5. How should uncertainty propagate to action?
6. When does assurance structure become ceremony?
7. Which interfaces dominate continuation risk?
8. Can lightweight cases preserve challengeability?
9. How should decisions update after evidence decay?
10. Is “Communication Engineering” redundant with tailored systems engineering?

Completion assessment

Bounded map complete; comparative cost experiment remains debt.