[irv]

What needs to be done is a complete rearchitecture and rewrite of the entire system. A costly undertaking that RARELY happens to software once it is in a production environment.

Indeed, if you're going to rewrite that much code from the ground up, I, personally, would want to carefully consider the hardware components, too, in order to look for interactions and common interface requirements. (That's off the top of my head)

Translation: Scrap the whole project and start again.

[Spruce]

Re-write is the first solution for any coder tasked with working on another's code.

[Filibuster_60]

I'm positive that the F-22 code overall is not only poorly written and documented, but the whole software development process used for it is highly flawed and would help explain why new problems keep showing up even as older ones are tackled. However that shouldn't be surprising - software development back in the early 80s is vastly different from software development today. If you ask me, a brand-new program using existing best practices has a good chance of fielding a reliable product before the clunky system out there now.