Sustaining Software-Intensive Systems

As today's systems become increasingly reliant on software, the issues surrounding sustainment become increasingly complex. The risks of ignoring these issues can potentially undermine the stability, enhancement, and longevity of fielded systems. Questions about sustaining new and legacy systems include

  1. What does it mean to perform sustainment from a software perspective?
  2. What types of development and acquisition activities are required to sustain software-intensive systems?
  3. Although the Department of Defense (DoD) has a technical definition of sustainment, does the DoD typically consider sustainment as maintenance?
  4. How does the increased use of commercial-off-the-shelf software complicate sustainment?

This technical note discusses these questions and presents definitions, related issues, future considerations, and recommendations for sustaining software-intensive systems. Sustainment done well leads to well-supported software-intensive systems and reduced total ownership costs and should help organizations meet current and new mission area and capabilities requirements.

The information contained in this technical note is based on information that the Software Engineering Institute gathered during work with Air Force software-intensive systems. While the information is pertinent and can be applied to systems in the commercial sector, keep in mind minimal effort was made to convert "DoDspeak" into commercial sector language.

PDF [272 KB]

Author

Mary Ann Lapham

Contributor

Carol Woody

This report is related to the following area(s) of work:

Acquisition Support

Technical Note
CMU/SEI-2006-TN-007
May 2006

Cite This Report

SEI:

Lapham, Mary Ann; & Woody, Carol. Sustaining Software-Intensive Systems (CMU/SEI-2006-TN-007). Software Engineering Institute, Carnegie Mellon University, 2006. http://www.sei.cmu.edu/library/abstracts/reports/06tn007.cfm

IEEE:

M. Lapham, and C. Woody, "Sustaining Software-Intensive Systems," Software Engineering Institute, Carnegie Mellon University, Pittsburgh, Pennsylvania, Technical Note CMU/SEI-2006-TN-007, 2006. http://www.sei.cmu.edu/library/abstracts/reports/06tn007.cfm

APA:

Lapham, M., & Woody, C. (2006). Sustaining Software-Intensive Systems (CMU/SEI-2006-TN-007). Retrieved May 18, 2013, from the Software Engineering Institute, Carnegie Mellon University website: http://www.sei.cmu.edu/library/abstracts/reports/06tn007.cfm

CHI:

Lapham, Mary Ann, and Carol Woody. Sustaining Software-Intensive Systems (CMU/SEI-2006-TN-007). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, 2006. http://www.sei.cmu.edu/library/abstracts/reports/06tn007.cfm

MLA:

Lapham, M., & Woody, C. 2006. Sustaining Software-Intensive Systems (Technical Report CMU/SEI-2006-TN-007). Pittsburgh: Software Engineering Institute, Carnegie Mellon University. http://www.sei.cmu.edu/library/abstracts/reports/06tn007.cfm

Find Us Here

Find us on Youtube  Find us on LinkedIn  Find us on twitter  Find us on Facebook

Share This Page

Share on Facebook  Send to your Twitter page  Save to del.ico.us  Save to LinkedIn  Digg this  Stumble this page.  Add to Technorati favorites  Save this page on your Google Home Page 

For more information

Contact Us

info@sei.cmu.edu

412-268-5800

Help us improve

Visitor feedback helps us continually improve our site.

Please tell us what you
think with this short
(< 5 minute) survey.