Information Technology Reference
In-Depth Information
CHAPTER 19
SOFTWARE DESIGN VERIFICATION
AND VALIDATION
19.1
INTRODUCTION
The final aspect of DFSS methodology that differentiates it from the prevalent “launch
and learn” method is design verification and design validation. This chapter covers
in detail the Verify/Validate phase of the Design for Six Sigma (DFSS), (Identify,
conceptualize, optimize, and verify/validate [ICOV]) project road map (Figure 11.1).
Design verification, process validation, and design validation help identify the un-
intended consequences and effects of software, develop plans, and reduce risk for
full-scale commercialization to all stakeholders, including all customer segments.
At this final stage before the release stage, we want to verify that software product
performance is capable of achieving the requirements specified, and we also want
to validate that it met the expectations of customers and stakeholders at Six Sigma
performance levels. We need to accomplish this assessment in a low-risk, cost-
effective manner. This chapter will cover the software relevant aspects of DFSS
design verification and design validation.
Software companies still are finding it somewhat difficult to meet the requirements
of both verification and validation activities. Some still confound both processes today
and are struggling to distinguish between them. Many literatures do not prescribe how
companies should conduct software verification and validation activities because so
many ways to go about it were accumulated through mechanisms such as in-house
tribal knowledge. The intent in this chapter is not to constrain the manufacturers and
to allow them to adopt definitions that satisfy verification and validation terms that
Search WWH ::
Custom Search