research-document
Software Engineering known risks
Software Engineering known risks
| Risk | Likelihood | Impact | Mitigation | Owner |
|---|---|---|---|---|
| Process overhead exceeds decision value | Medium | High | Measure time and rework; use artifact thresholds | Unassigned |
| “Communication Engineering” is treated as validated before evidence exists | Medium | High | Keep boundary claims provisional and comparative | Unassigned |
| Sensitive communication data enters repository artifacts | Medium | High | Define data classes and use synthetic fixtures until reviewed | Unassigned |
| Documentation becomes detached from implementation | Medium | High | Link decisions to tests and refresh handoffs at milestones | Unassigned |
| Baseline is selected after results are known | Medium | Medium | Register baseline and measures before the first slice | Unassigned |