Safety Critical Software Justin Shelite Matt Smith Justin Dolezilek Tony Trujillo Justin Metcalf Kenton Shuck

Scenario A large company develops safety critical software on a time and materials basis. That is, the company charges based on the actual effort. However, there is a bonus/penalty for high reliability/failures.

Overview Requirements Requirements Development Development Monitoring Monitoring Testing Testing

Requirements Highly Detailed Highly Detailed Use Scenarios Use Scenarios Watch user perform the tasks on previous applications if applicable Watch user perform the tasks on previous applications if applicable

Development Partner Programming Partner Programming Ensure reliability Ensure reliability Many releases to ensure required quality is achieved as well as ensuring timely completion Many releases to ensure required quality is achieved as well as ensuring timely completion Test Driven Test Driven Ensure quality by specifying tests that it needs to pass Ensure quality by specifying tests that it needs to pass

Monitoring Dashboard Dashboard Upper Management Upper Management Simple graphics to keep them aware of progress Simple graphics to keep them aware of progress Progression of test cases passed Progression of test cases passed EV – Make sure project is on task for timely completion EV – Make sure project is on task for timely completion

Testing Test every release to make sure it passes required tests Test every release to make sure it passes required tests User tests User tests Object Oriented Testing Object Oriented Testing DPU and DCU DPU and DCU