Page - 171 - in The Future of Software Quality Assurance

Embracing Qualitywith Design Thinking 171 Fig. 6 Design thinking informs production requirements that govern production design, imple- mentation, and testing deployedrelativelyearlywithregularrevision.Continuousdeploymentislessviable forproducts that at best canbepatchedorupdatedonceamonth. Once the design thinkingphase hascompleted, the interactivedynamicbetween users and the design for the most part ends. The design outcome provides an established set of user-facing requirements that need to be implemented and tested to accepted productionquality.Given the speed at which prototypecode is written, its base may only be partially salvageable. The languages and libraries chosen may have enabled prototyping speed and flexibility. Now knowing what needs to be implemented, the language and library selections may need to be revisited in order to provide a more manageable, reliable, secure, and computationally efficient foundation. By having senior developers participating on the design thinkingproject,variousdevelopmentconventionsand toolchainsused instandard development projects are more likely to be used during prototype implementation, thus making reuse more feasible. Figure 6 shows design thinking as a launch point that influences production requirements, but it is no longer a dynamic componentamong productiondevelopmentactivities. The central motivating force is the production requirements activity, which will develop new requirements necessaryfortheresult tobeofsufficientreliability,fitnessforuse,security,privacy, usability,maintainability,andperformancetobesuccessful in themarketplaceor in production.