Entries by 'Mike Phillips'

Mar 26
2012

Toward Efficient and Effective Software Sustainment, Second in a Series

Acquisition , CMMI , Software Sustainment , Team Software Process (TSP) No Comments »

By Mike Phillips
Principal Researcher
Acquisition Support Program

Mike Phillips In my preceding blog post, I promised to provide more examples highlighting the importance of software sustainment in the US Department of Defense (DoD). My focus is on certain configurations of weapons systems that are no longer in production for the United States Air Force, but are expected to remain a key component of our defense capability for decades to come, and thus software upgrade cycles need to refresh capabilities every 18 to 24 months. Throughout this series on efficient and effective software sustainment, I will highlight examples from each branch of the military. This second blog post describes effective sustainment engineering efforts in the Air Force, using examples from across the service’s Air Logistics Centers (ALCs).

 

Read more...

Feb 27
2012

Toward Efficient and Effective Software Sustainment

Acquisition , CMMI , Software Sustainment 2 Comments »

 By Mike Phillips
Senior Member of the Technical Staff
Acquisition Support Program

Mike Phillips Our SEI blog has included thoughtful discussions about sustaining software, such as the two-part post “The Growing Importance of Sustaining Software for the DoD.” Software sustainment is growing in importance as the lifetimes of hardware systems greatly exceed the normal lifetime of software systems they are partnered with, as well as when system functionality increasingly depends on software elements. This blog post—the first in a multi-part series—provides specific examples of the importance of software sustainment in the Department of Defense (DoD), where software upgrade cycles need to refresh capabilities every 18 to 24 months on weapon systems that have been out of production for many years, but are expected to maintain defense capability for decades.

Read more...