OCIO » Testing Methodology Main Page

Testing Methodology Main Page

Last modified by Mike Phillips on 2014/07/01 10:26

Contents

Software Testing Methodology for DAS / ITE

The software testing methodology in place for DAS / ITE is based on risk management, which represents a shift from task oriented test methodologies. Task oriented test methodologies focus on completing a set of project tasks that generally remain the same across projects. A shift to a risk management oriented methodology does not mean project tasks are not used as milestones. Project tasks, such as test plans, requirements reviews, and test execution, are still completed according to the project schedule; however, the project tasks are not the main focus of the test effort. Instead, the testing effort is dynamic and flexible, allowing test resources to be applied to the high risk functional areas of the new software product. 


 

Advantages of Risk Analysis Methodologies

DAS / ITE software projects are driven by customer requirements; It is the goal of DAS / ITE to provide the customer with a software solution that meets customer needs. It is not uncommon for a software project to be affected by budget constraints. While all project tasks are affected by budget realities, the testing effort often bears the brunt of the cutbacks due to the nature of its place in the lifecycle and the desire to deliver all functionality wanted by the customer. A good risk analysis methodology allows the testing process to be scaled back without compromising the main features of the software. 


 

Risk Analysis throughout the project lifecycle

Risk Analysis occurs at every step of the project lifecycle. During the requirements gathering stage, the requirements review includes a section for assigning risk. This assessment is then used during the test planning process to determine test scripting priority. High risk requirements are given priority over other requirements for planning and scripting. During the test execution phase, the high risk features are tested first. Bug fixes for high risk features are given priority over low risk features that may or may not have been tested during the previous round of testing. 

LINKS

DAS / ITE Software Project Testing Activities

The DAS / ITE testing team is normally engaged by the project manager during the requirements gathering phase.
 

 

Tags:
Created by Mike Phillips on 2011/06/07 15:13

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 3.0.36132 - Documentation