Construct an influence diagram—software: late design change
Make a design change in hopes of solving a software bug. It is only 6 weeks before a software product’s launch. On rare occasions, commercial users who are beta testers have run into a problem that caused the software to lock up. However, software engineers are not able to reproduce the crash in a controlled environment. They are fairly sure that the problem stems from a series of three subroutines. They have a new design that can be implemented quickly and that should solve the problem. In constructing the diagram, identify all the key issues and inputs. Use your judgment to specify whether or not a key variable is simply a deterministic input or will represent significant uncertainty that should be taken into account. Are there any downstream decisions?