The Quest for Application Quality
Independent testing introduces a degree of separation in the application development lifecycle that improves application quality by eliminating potential testing biases. An independent provider can also bring to bear the resources and specialists needed to ensure that applications run well across a diverse set of platforms or meet specific industry standards.
Independent facilities integrate testing throughout the application development lifecycle, beginning at the requirements stage. This guarantees that application features and design are aligned to business needs while also meeting user needs and expectations. Code that meets user requirements the first time out is a good indicator of quality. Well received code requires less rework, and therefore, less of the intrusion that can lead to complexity, performance issues and other quality detractors.
You’ve just launched a new application. Congratulations!
Now, the real work begins.
An application doesn’t stop changing the day it ships. A successful application goes through multiple revisions and releases over its lifetime.
Some changes, such as the build-out of new features and add-on modules, can be planned during the requirements and design phase, and implemented methodically in subsequent releases. Market-driven changes aren’t as easy to anticipate, often surfacing later in the software development lifecycle or once an application is in the field. These may include:
• New statutory or compliance requirements
• Emerging technology that fundamentally alters the way an application is deployed or how it’s used
• Changing user and usability needs (e.g., from laptop to tablet to phone, and from typing to swiping)
Due to the combination of both planned and market-driven changes, it’s not unusual for an application to require significant architectural changes from one version to the next in order to remain relevant.
That’s why getting it right the first time, and setting the stage for continuing quality over the life of an application, is getting more attention.
Studies show that addressing a defect can cost as much as 70 times more when it is identified after application release than when remedied during development. If that metric surprises you, multiply that value by the number of defects found in a released application, then by the number of releases expected over the app’s lifetime: When you do this, the savings associated with managing application quality become very apparent and very significant.