Abstract
AbstractText books provide guidance on how Systems Engineering should be done. Multiple papers and reports provide statistics and dissections of Systems Engineering related program failures. Few papers discuss how to bring programs back from a self perpetuating Systems Engineering downward spiral. This paper provides real world examples of how major legacy programs facing schedule slips, funding overruns and customer dissatisfaction, choose not to become a failure statistic and instead developed fiscally realistic solutions to successfully repair fractured, neglected, contested, and inconsistent technical requirement baselines.
Full Text 
Sign-in/Register to access full text options
Sign-in/Register to access full text options 
Published version (
Free)
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
