Software Engineering for satellites Kathryn Anne Weiss Software Engineering Research Laboratory Department of Aeronautics and Astronautics Massachusetts Institute of Technology October 22. 2003 June17.2004 o Massachusetts Institute of technology 2002
June 17, 2004 © Massachusetts Institute of Technology, 2002 1 Software Engineering for Satellites Kathryn Anne Weiss Software Engineering Research Laboratory Department of Aeronautics and Astronautics Massachusetts Institute of Technology October 22, 2003
Topics of Discussion ◆ Background ◆ Why is Software Why is Software Engineering hard for Engineering Hard? Spacecraft? Lifecycle ◆ SERL Approach Cost ◆ Component- Based Requirements Specification Systems Engineering Approaches to Design SPHERES Implementation Testing ◆ Conclusions Maintenance June17,2004 o Massachusetts institute of technology 2002
June 17, 2004 June 17, 2004 © Massachusetts Institute of Technology, 2002 2 Topics of Discussion Background Why is Software Engineering Hard? Lifecycle • Cost • Requirements Specification • Approaches to Design • Implementation • Testing • Maintenance Why is Software Engineering Hard for Spacecraft? SERL Approach Component-Based Systems Engineering SPHERES Conclusions
Background Ariane 5 Courtesy of Arianespace /ESA/CSG Used with permission Mars climate Orbiter ISD VisuLab SOlar Heliospheric Observatory June17,2004 o Massachusetts institute of technology 2002
June 17, 2004 June 17, 2004 © Massachusetts Institute of Technology, 2002 3 Background Ariane 5 Mars Climate Orbiter SOlar Heliospheric Observatory Courtesy of Arianespace / ESA / CSG. Used with permission
Background Why is Software Engineering Hard? s“ Curse of flexibility And they looked upon the software and saw that it was good. But they just had to add one other feature No physical constraints Intangibility Lack of historical usage information Organized complexity Too complex for complete analysis Too organized for statistics Large discrete state spaces June17,2004 o Massachusetts institute of technology 2002
June 17, 2004 June 17, 2004 © Massachusetts Institute of Technology, 2002 4 Background Why is Software Engineering Hard? “Curse of flexibility” • ‘‘And they looked upon the software and saw that it was good. But they just had to add one other feature ...’’ • No physical constraints Intangibility Lack of historical usage information Organized complexity • Too complex for complete analysis • Too organized for statistics Large discrete state spaces
Background ◆ Software Lifecvc|e Feasibility Study Requirements v&v Design v&v plement V&Ⅴ ation Testing v&v v&v Maintenance v&v June17,2004 o Massachusetts institute of technology 2002
June 17, 2004 June 17, 2004 © Massachusetts Institute of Technology, 2002 5 Background Software Lifecycle Feasibility Study V & V Requirements V & V Design V & V Implement ation V & V Testing V & V Maintenance V & V