Infographic: Software Understandability

Software understandability practices allow developers to drop in code changes and bug fixes at the exact breakpoint with all relevant data.

Jason English

Nov. 04, 20 · DevOps Zone · Analysis

Like (1)

Save

7.05K Views

Figure 1. Development feature additions and issue resolution processes with and without software understandability, demonstrating in-flight time reduction and productivity gains.

In conventional issue-and-task driven development processes, each new bug report or feature modification request results in several unnecessary ‘hops and stops’ atop a high-traffic application portfolio for resolution. Developers must obtain access permissions, search the enterprise application portfolio for data to find code, wait for results, and write more instrumentation code to get more data.

Software understandability practices complement observability and IT operations management tools with direct code-level breakpoint insertion, to eliminate unproductive work and unnecessary wait time, thereby reducing unproductive hours and days from issue resolution and feature delivery.

Download (PDF, 720K) your own copy, or view a full-size (JPG, 353K) version of this infographic from Intellyx principal analyst Jason English.

Topics:

software development, debugging, issue resolution, analysis, observability, breakpoint, agile development

Published at DZone with permission of Jason English. See the original article here.

Opinions expressed by DZone contributors are their own.

Comments

Infographic: Software Understandability

Software understandability practices allow developers to drop in code changes and bug fixes at the exact breakpoint with all relevant data.

Popular on DZone

DevOps Partner Resources