Software Change Impact Analysis demo
Each release's change set lights the software items it touches, with lines to their hazards and tests. 1:29
What the demo shows
Software change impact analysis: each device software release traced to its hazards and tests
Agents read release 3.5 of a heart pump console (61 files, 9 tickets), light the 4 of 6 software items it touches, and follow them to 23 requirements, 5 hazards and the regression tests. A ticket marked user interface only also edits the alarm manager, a class C item, so 6 alarm tests are added; 2 changed functions with no test block approval until tests are linked. The test lead agrees 46 tests and the software QA lead approves the pack.
Transcript
- Software Change Impact Analysis shows device software teams what a release touches. In FDA's 1992 to 1998 study, most software recalls came from later changes.
- Four items light up, and Radomila checks each. One ticket says interface only, yet it edits the class C alarm manager.
- Hazard H-22 adds six alarm tests; two functions lack a test. Radomila signs.
- Bastiaan, the test lead, reads the six added tests,
- then a random sample from each lit item.
- He opens the new test written that morning for each loose line, and links it to that line.
- Then he agrees, with his own password.
- Gunnhild, the software QA lead, reads the alarm manager trace herself.
- Then flow estimation, L1 closed by its new test.
- And the service interface; then she approves. Forty-six tests, each cited. Agents never release software.
- Built on Botminds: agents, data, screens and governance on one platform.
The narration as written for the film. Captions are on the player.