The Software Intelligence Blog

Tag: Technical Debt

  • Technical Debt Indexes Provided by Tools: A Preliminary Discussion

    In software maintenance and evolution, it is important to assess both code health and application architecture in order to identify issues impeding software quality goals. One way to move the needle toward software quality is to use Technical Debt (TD) indexing as a method to evaluate development projects.

    We recently presented a paper at MTD 2016, the International Workshop on Managing Technical Debt put on by the Software Engineering Institute at Carnegie Mellon, where we discussed the way five different and widely known tools used to compute Technical Debt Indexes (TDI), for example numbers synthesizing the overall quality and/or TD of an analyzed project.

  • Takeaways from the CAST Italy Summer User Group

    On June 22nd, CAST held its annual User Group in Italy, hosting software measurement professionals from major companies in the Banking, Insurance, Telco, Public Sector and IT Consulting industries for a four-hour working session. Attendees walked away from the event with a better understanding of best practices in establishing objective software measurement standards and creating better visibility in to application portfolios.

    Among CAST Application Intelligence Platform presentations and updates regarding the new CISQ RFC for Automated Enhanced Points and its relationship with the AFP OMG standard, attendees also discussed software measurement in Agile and DevOps environments.

  • 4 Keys to Successful Digital Transformation

    Recently, CAST co-authored a paper with The Boston Consulting Group titled, Will Your Software Help or Hinder Digital Transformation? Navigating the digital transformation journey is a challenge, often wrought with roadblocks and IT complexities related to technical debt, disparate application development techniques and more. So how can CIOs help their company achieve digitization goals?

  • The Age of Digital Transformation: Where to Start?

    The term “Digital Transformation” has become more than just a buzzword as companies continuously work toward the goal of realigning and investing in the digitization of all business aspects to meet and predict customer demands. In the midst of these big changes, there has been much confusion about what it means to actually achieve digital transformation and how to monitor your progression through each stage of the transition.

  • Using Code Quality Metrics to Improve Application Performance

    For years refactoring software has been a common process used to improve the quality, efficiency, and maintainability of an application. However, a recent article by IT World discusses how CIOs may not be getting a valuable return on their investment of time and effort into the refactoring process. While many believe refactoring reduces the risk of future headaches, new findings acquired through a study by Sri Lanka researchers suggests code quality is not improved significantly by refactoring.

  • Measuring Legacy Systems for Technical Debt and Quality

    Legacy Code

    When a business develops software, new technologies eventually outgrow the software. But that doesn’t mean the software stops working, which is why businesses continue to use legacy software. In fact, after all the fixes and patches, the legacy software still gets used because it simply works, even if it means the users are forced to run older operating systems and older web browsers to use it.

  • Key Points dalla CAST CIO CONFERENCE 2015

    Giovedì 11 Giugno 2015 ha avuto luogo la IV Edizione della CAST CIO Conference. Ringraziamo i numerosi aderenti alla manifestazione che hanno contribuito al successo di questo evento consentendoci di analizzare, traendo spunto dai più recenti  casi di malfunzionamento di applicazioni “mission critical”, le strategie di prevenzione dei rischi attraverso la misurazione della qualità strutturale degli asset applicativi critici.

  • Key Points dal 1° Evento Metrico 2015 GUFPI ISMA

    CAST ha partecipato al 1° Evento Metrico 2015 organizzato dal GUFPI ISMA, associazione di riferimento nazionale per la misurazione del software in Italia, tenuto a Roma lo scorso 14 Maggio. La conferenza ha visto la partecipazione di Cast sui seguenti 3 topics:

  • Paying Down Technical Debt with Mircoservices: Miracle or Myth?

  • Technical Debt: Is Management Only Getting Half the Picture?

    As Larry Quinlan, Global CIO, Deloitte Touche Tohmatsu Limited explains, “CIOs need the courage to make the investments that reduce technical debt -- and the knowledge and the team to know where and when to make those investments.”

  • IT Needs New Ways To Talk About Quality!

    Gartner report highlights “application development managers need new ways to demonstrate and communicate the business value of software quality for innovation projects.”

  • Modernize QA with Automated Structural Quality Gates

  • A Financier’s Guide to Technical Debt

  • Guest Webinar: How to Reverse Your Technical Debt

  • Two Decades of Technical Debt And What Do We Know?

    It’s been over 20 years since Ward Cunningham introduced the debt metaphor with an experience report at OOPSLA, the conference for Object Oriented Programming. At the time, Cunningham was arguing that debt was a good idea -- you could get the software out faster by taking shortcuts, collect additional revenue, and come back later to pay it off.

  • Technical Debt: Principal but no interest?

    Making technical debt visible already proves to be quite a challenge, as it’s all about exposing the underwater part of the iceberg.

    But how deep underwater does it go? To know for sure, you would need the right diving equipment. To go just below the surface, you would start with a snorkel. But to go far down, you need a deep-sea exploration submersible.

  • Remediation cost versus risk level: Two sides of the same coin?

    While working in a CISQ technical work group to propose the "best" quality model that would efficiently provide visibility on application quality (mostly to ensure their reliance, performance, and security), we discussed two approaches that would output exposure. The first is a remediation cost approach, which measures the distance to the required internal quality level. The other is a risk level approach, which estimates the impact internal quality issues can have on the business.

  • Is Every Part of the Application equal when Assessing the Risk Level?

    Risk detection is about identifying any threat that can negatively and severely impact the behavior of applications in operations, as well as the application maintenance and development activity. Then, risk assessment is about conveying the result of the detection through easy-to-grasp pieces of information. Part of this activity is about highlighting what it is you’re seeing while summarizing a plethora of information. But as soon as we utter the word "summarizing," we risk losing some important context.