Software Change Impact Analysis¶
Bohner, S. A., & Arnold, R. S. (1996). Software Change Impact Analysis.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Impact Assessment Checkpoint
- It is the analytical counterpart to any dependency- or ripple-effect analysis in change management.
This sourceDefines change-impact analysis as tracing dependencies and potential ripple effects of a proposed change.
- It is the analytical counterpart to any dependency- or ripple-effect analysis in change management.
- Lineage Impact Analysis Report
- The discipline is ordinary change-impact-analysis hygiene: trace before deciding, credit the overrides that shield descendants, rank by real exposure, and treat an empty blast radius as a prompt to check the graph's completeness, not a certificate of safety.
This sourceFrames software change-impact analysis around tracing dependencies and relationships to predict which parts may be affected by a change.
- The discipline is ordinary change-impact-analysis hygiene: trace before deciding, credit the overrides that shield descendants, rank by real exposure, and treat an empty blast radius as a prompt to check the graph's completeness, not a certificate of safety.
Verification¶
Does it exist? Confirmed. This work's ISBN resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Not recorded. Neither this nor any other of the 2 citations of this work carries a recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:4821fc0f8092 · see in the full table