We know that Developer/Architect/functional resources should be able to perform enough software testing to save any product from collapse. In my opinion, that is wrong approach. There should be designated software testing resources that identify bugs and risks before the product is handed to the customer. Buggy software creates ambiguity and confusion in the customers’ mind. It doesn’t matter what is done to reassure them afterwards or how quickly the product is fixed. The importance of software testers/QAs resources needs to be acknowledged. Preventing problems saves both the customer and the implementer money and time. Refer to the diagram below.
Borland. “Driving Quality Throughout the Software Delivery Lifecycle: The Benefits of Lifecycle Quality Management.” 2007. Web. 14 July 2001.
Support EasyBib! Try Premium!)
Next time you out there in the field and want to be successful, don’t overlook the importance of software testing. Testing is fundamental to any successful implementation. Whenever you are coding or configuring any system, repeat the mantra, “Testing is very important, don’t ignore it.” Always remember, cost of nonconformance is higher than conformance on any project.
