It’s no shocker that the federal government is turning to cost cutting measures in the middle of a down economy. But there’s a bigger problem looming on the horizon.
The federal government has become very dependent on open source products; which wouldn’t be a problem if open source software was held to the same standard as custom commercial code.
What government agencies fail to realize is that the open source components they’re using to cut costs are being integrated into their most crucial systems. They’re not standing alone. They’re right in the mix, integrated into various data feeds and sources.
Don’t get us wrong, open source software is great. And the development communities around open source are active and responsive. But that, in and of itself, does not equate to the same level of quality that proprietary applications face before release.
Do you think it’s safe for the federal government to be using open source technologies? Weigh in with a comment.
Erik Oltmans, an Associate Partner from EY, Netherlands, spoke at the Software Intelligence Forum on how the consulting behemoth uses Software Intelligence in its Transaction Advisory services.
Erik describes the changing landscape of M & A. Besides the financial and commercial aspects, PE firms now equally value technical assessments, especially for targets with significant software assets. He goes on to detail how CAST Highlight makes these assessments possible with limited access to the targetâ€™s systems, customized quality metrics, and liability implications of open source components - all three that are critical for an M&A due diligence.