Tag: Static code analysis

Examining New Technical Debt Research from the Software Engineering Institute.
Uncovering Technical Debt Through Data-Driven Management
An Analysis of Gartner’s Note “Ensuring Quality From External Agile Software Developers”
2 Tips to Ensure External Agile Teams Deliver Software Quality
Technical debt and DevOps are two topics on every organizations mind.  Yet, no one tackles the topic better than this article
Technical Debt & DevOps: 5 factors fueling automation in IT
Software risk is business risk, but who is ultimately responsible? This blog explores insights from the Cutter Consortium on how to de-risk business-critical software systems.
Software Risk is Business Risk

The ever-growing cost to maintain systems continues to crush IT organizations, robbing their ability to fund innovation while increasing risks across the organization. The cost of maintaining a software system is directly proportional to the size and complexity of the system. Therefore any effort to reduce the size and complexity translates into direct improvement of software maintenance costs. The following provides guidance on how a static code analysis of applications generates actionable insight you can take to immediately improve the maintainability of systems.

Static analysis: Leveraging source code analysis to reign in application maintenance cost
Anyone whose professional life has intersected with the technical debt metaphor knows its power: the simple proposition that such a thing exists opens up a new channel of communication among groups (IT and application developers, designers, biz dev) that famously have trouble communicating about technical decisions. Not everyone understands test cases, aging platforms, crufty code bases, or security loopholes, but everyone understands debt (needless to say, most everyone has personal debt, and a sizable proportion of the news media conversation concerns debts, mortgages, and deficits).
Can Technical Debt Be Quantified? The Limits And Promise Of The Metaphor
This interview will focus on the ground-level steps that should be taken in order to help IT teams deal with their Technical Debt in a pragmatic and efficient way, while working in a fast-paced Agile environment.
Pragmatic Ways for Your IT Team to Deal with Technical Debt
elow is an updated set of slides from a webinar presented by IEEE Software and Boeing on how to identify and manage technical debt. The slides outline how business and product quality goals should affect the choice of approaches (and combinations of approaches) for managing technical debt. They also discuss a set of automated approaches based on static code analysis that are likely to spot problems in source code that have real impact on productivity and defect proneness.
Identifying and Measuring Technical Debt – IEEE Software & Boeing
Technical Debt exists in many forms. Perhaps the most common concerns software maintainability. Code that is difficult to maintain is more expensive to maintain, plus the development group can’t respond to the business as quickly. So, we can then conclude that code that is poorly-written or difficult-to-read costs the company money – directly or indirectly.
Part II: Practical Examples of Paying Down Technical Debt