As the impact computers have on our lives increases at an unprecedented rate, software systems are becoming increasingly complex. For example, a pacemaker has less than 100,000 lines of code written into it. A F-35 Fighter jet has about 250,000 lines. Facebook on the other hand has upwards of 600,000. Now what about that fancy new Lexus you just purchased? That has about a million lines of code. As the applications that make up these various systems are becoming more and more integrated and intricate, it is crucial for those in application development to take a multifaceted approach to developing their technologies and measuring their software size.
We are all too familiar with the feeling of the GPS in your car leading you to an empty field instead of the grocery store, or Facebook not being able to successfully upload the photo of your new nephew. Just imagine there was something wrong with the pacemaker surgeons implanted into your brothers chest last week. Why does software size matter? Because without a complete understanding of the size of your software, how can you deploy it, how can you fix it, and most importantly- how can you build onto it? As applications become more and more integrated with one another, and as the lines of code written into various applications becomes longer, it’s important to stay informed and maintain your systems to the highest standard.
For a visual on software size, check out this infographic from Information is Beautiful.
To learn more about software size and the million lines of code CAST analyzed last year, download the CRASH Report here.
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.