Software Obsolescence: Why Modernization Doesn’t Necessarily Mean “Modern”
For players in the embedded industry it is easy to forget how large the problem of obsolescence can be, especially beyond the component level. Recently, I was talking to a software engineer who had spent a year doing software modernization, as a result of upgrading a flight navigational system from the original code to Linux.
The reasoning for the transition certainly made sense—the program was having difficulties finding software engineers who could continue to sustain programming that had been implemented during the early 1980s. While the system was incredibly robust and was considered “bulletproof,” it could no longer be supported the way it had been. Under pressure to upgrade, the program moved to Linux, which has a community that affords an active and growing resource for talent.
Critical Thoughts RSS Feed