Resources
IDC

As organizations seek the visibility needed to measure and evaluate software complexity, size, productivity and risk, IDC has defined a new market category of Software Quality Analysis and Measurement (SQAM). Learn more about the motivation contributing to the impressive growth in this space including competitive pressures, complex sourcing, and economic impacts.

Gartner Research

A formal approach to quality management is needed that recognizes the key dimensions of quality (Stakeholders, Technical Quality, Functional Quality), and a set of measures that enable the organization to identify areas for improvement and focus on the specific changes that they can make successfully.

Any organization that outsources a lot of custom development and enhancement should care about CAST, which has become the de facto standard for measuring the quality and productivity of vendor deliveries in some markets.

Gartner Research Director Thomas Murphy notes that software quality is often a poor misnomer for the current practice of risk management applied by most companies. Many organizations use risk management to mitigate delivery risk, typically at the expense of application quality. Learn about the importance of focusing on application structural quality to reduce business disruption risk in this Gartner-CAST paper.

Read exclusive analysis from Andy Kyte, Gartner VP and Fellow, on the systemic risk in the typical application portfolio caused by the accumulation of Technical Debt. You will also learn how to define Technical Debt and calculate a dollar value for a typical application; express both delivery agility and business risk in terms of the same unit–dollars; and set and monitor the right quality threshold for balancing delivery agility with the risk of business disruption.

Forrester Research

To gain transparency into developer productivity and code quality, some companies are using tools, such as those from vendors like CAST, to evaluate the quality of externally developed code and ensure that it meets certain coding and productivity standards.

Failure to consider quality requirements results in Technical Debt — the need to rework something in the future based on your failure to pay for it now. Static analysis tools, such as CAST, mine source code to uncover common errors, development shortcuts, and code complexity all of which contribute to Technical Debt.

Follow
Us