Government acquisition policies and contracts have assumed that source code equaled control of portability, extensibility, and interoperability. Unfortunately, control is an illusion. The reality is that the DoD now has millions of lines of code, divorced from their original architects and developers, that the government seeks to reuse - and it often costs more to reuse than to develop from scratch.
Legacy Software Migration
There are many reasons why military embedded systems become obsolete. Sometimes it’s because vendors stop supplying required hardware or supporting certain operating systems or versions. Other times it’s because of changes in the developmen...
COTS-based DBMSs are emerging to take the reigns from homegrown and enterprise databases on the legacy migration path.
Static analysis tools can help find concurrency and other defects to cut legacy's latency.
The next evolution of the legacy software migration will need to focus on flexibility, and should be architected to enable the construction of Systems of Systems.
The use of test tools is vast across countless applications, but of particular value when used for quality assurance in the customer environment.
As new systems are being designed, software developers are using open-standards-based programming languages and OSs, such as C/C++ and POSIX, to ensure portability for the future. But for existing deployed legacy systems, the same considerations and ...
FPGA migration strategies: IP development tools ease Xilinx Virtex-6 to Virtex-7 migration challenges
Migrating to a new FPGA platform is not for the faint of heart, but the challenges can be eased, thanks to modern IP development tools.
Exploitation of MCUs, MPUs, and multicore and FPGA hardware with C/C++ and POSIX implementations offer SWaP-reducing legacy system restructuring alternatives to virtualization.
Soon most hardware processing platforms will be based on multicore architectures. But what does this mean for legacy software applications?