l17_software_eng

l17_software_eng - June 17, 2004 Massachusetts Institute of...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: June 17, 2004 Massachusetts Institute of Technology, 2002 1 oftware Engineering for Satellites Kathryn Anne Weiss Software Engineering Research Laboratory Department of Aeronautics and Astronautics Massachusetts Institute of Technology October 22, 2003 June 17, 2004 2 June 17, 2004 Massachusetts Institute of Technology, 2002 opics 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 June 17, 2004 3 June 17, 2004 Massachusetts Institute of Technology, 2002 ackground Ariane 5 Mars Climate Orbiter SOlar Heliospheric Observatory Courtesy of Arianespace / ESA / CSG. Used with permission. June 17, 2004 4 June 17, 2004 Massachusetts Institute of Technology, 2002 ackground 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 June 17, 2004 5 June 17, 2004 Massachusetts Institute of Technology, 2002 ackground Software Lifecycle Feasibility Study V & V Requirements V & V Design V & V Implement ation V & V Testing V & V Maintenance V & V June 17, 2004 6 June 17, 2004 Massachusetts Institute of Technology, 2002 ackground Software Cost Maintenance Testing Requirements Coding June 17, 2004 7 June 17, 2004 Massachusetts Institute of Technology, 2002 equirements Specification Most critical portion of the software lifecycle Majority of errors in software can be traced back to flaws in the requirements Many methods and types of requirements including: Informal English UML Formal Zed State Machines Intent Specifications June 17, 2004...
View Full Document

This note was uploaded on 11/08/2011 for the course AERO 16.851 taught by Professor Ldavidmiller during the Fall '03 term at MIT.

Page1 / 28

l17_software_eng - June 17, 2004 Massachusetts Institute of...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online