What Does Software Size Have to Do with It?

by

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.

Codebases

To learn more about software size and the million lines of code CAST analyzed last year, download the CRASH Report here.

  This report describes the effects of different industrial factors on  structural quality. Structural quality differed across technologies with COBOL  applications generally having the lowest densities of critical weaknesses,  while JAVA-EE had the highest densities. While structural quality differed  slightly across industry segments, there was almost no effect from whether the  application was in- or outsourced, or whether it was produced on- or off-shore.  Large variations in the densities in critical weaknesses across applications  suggested the major factors in structural quality are more related to  conditions specific to each application. CRASH Report 2020: CAST Research on  the Structural Condition of Critical Applications Report
Open source is part of almost every software capability we use today. At the  very least libraries, frameworks or databases that get used in mission critical  IT systems. In some cases entire systems being build on top of open source  foundations. Since we have been benchmarking IT software for years, we thought  we would set our sights on some of the most commonly used open source software  (OSS) projects. Software Intelligence Report <> Papers
Making sense of cloud transitions for financial and telecoms firms Cloud  migration 2.0: shifting priorities for application modernization in 2019  Research Report
Load more reviews
Thank you for the review! Your review must be approved first
You've already submitted a review for this item
|
()

A safer approach to application modernization and re-factoring for cloud
×