Acting as EngineerC3Accept
Change impact
Pick something that might change and see everything that would have to be re-examined, with the path that made it relevant. The traversal is the same one the database performs with a recursive query.
SRS section 12, change impact analysis
Origin
What is changing.
Nodes reached
0
Requiring rework
0
Gates re-opened
0
Impact
Breadth first from the origin. Depth is how many hops away the node sits.
Nothing depends on this yet.
The distinction between rework and re-read matters. A change that reaches a frozen baseline or an issued drawing costs money; a change that only reaches an ontology definition costs a read. Reporting both as impact would make the analysis useless.