2013 Issue

55 components were not included in their version, and they will have to start their testing process all over again. Next should be unit testing, where each screen is tested thoroughly for desired functionality. Integration testing, or scenario testing, ensures the software is adequate for real-world situations. Good integration tests track the consistency of data input in one screen to the same data output in other screens or reports. UI (user input) tests are always good to ensure the screens paint and react prop- erly to user-input. Make a list of common UI problems, and have your testers check each screen for each problem. A trace- ability matrix will help with this. User Acceptance Once your software has progressed this far, have an end-user confirm the working screens and reports are ready and useful to their needs. Be sure to confirm which user performed the test, and what their role was. Be sure to include every major role in the user acceptance testing process. Sponsor Acceptance As a final step, confirm with your project sponsor all of the deliv- erables are accounted for and have met all of the required quality checks along the way from concept to delivery. Be sure your spon- sor has established success criteria and objectives for the project up front. Review these objectives and deliverables, and success criteria and confirmwith the sponsor everything is ready for launch. A traceability matrix is useful for this final sponsor acceptance process. The traceability matrix should show project deliverables or requirements cross references with upstream project objectives and downstream quality review and successful testing results. Release Create a list of lessons learned during the development process. Hold a project retrospective after roll-out and record any additional lessons learned. Be sure to save all project quality documentation and lessons learned in a release repository, where it can be accessed easily by future software teams. In conclusion, putting a quality management system in place for your software environment requires a mild investment in quality practices. Don’t be surprised to find some pushback from some teammembers. The key is to compare the cost of quality measures to the cost of penalties, fire-fighting, rework, and lost time due to quality related efforts, and you can almost always make a case for adopting advanced quality practices as described here. A R W 1594 Park Circle, Ogden, Utah 84404 ph. 801.782.6008 www.arwengineers.com A Commi tment to Qual i ty, A Four -Decade Legacy of Serv i ce structural consultant s ENGINEERS