Success in ever more competitive worldwide marketplaces demands products and services
that are increasingly personalized and innovative. These attributes can increase
an organization's competitiveness and ability to provide value to customers, but
at the same time they can compound the complexity of delivering such products
and services to market.
While advanced functionality is an important competitive differentiator, quality
has become part of the "price of entry" into the marketplace that
can no longer be added into systems at the end of the development lifecycle.
As a result, when managing quality, an organization must consider all key systems
engineering disciplines including requirements engineering, systems design and
testing, and change and configuration management. This article examines the
changing role of quality assurance and looks at approaches that effectively
extend application lifecycle management (ALM) to include quality management
and align project outcomes with customer needs and business objectives.
Smarter products and the evolving role of quality assurance
In conventional product development, requirements analysis, design and development
are typically completed first, with testing done in a silo -- at the end of
the development process.
When products become more complex, not only can the risk of quality problems
increase; the potential customer impact of those problems can be much greater.
What's more, as you go from specifications through analysis, architecture, design
and implementation, the cost of finding and fixing a problem grows. In the worst-case
scenario, finding an issue in the field can be especially costly to the bottom
line and the brand.
Today's innovative products frequently deliver their value through interoperation
with systems which are external to the product and often external to the product
development organization. Consider a smart phone, which might offer GPS capability
and 3G web and voice connectivity. Developing the software for such distributed
systems is a complex challenge. For example, compliance with interface standards
and interoperability across system boundaries tends to increase the complexity
of both projects and development organizations. Teams may be distributed across
organizational and geographic boundaries, working across different time zones,
languages and cultures. Organizational and infrastructure barriers arising from
varying perspectives and approaches to development create challenges, impeding
quality and slowing time to market.
-1-