In Systematic Test and Evaluation Process (STEP) and CTP it is not necessary for improvements to take place in a predefined sequence, unlike TPI Next and TMMi.
STEP is a content reference model that believes that testing process starts with software product requirements gathering phase and goes on till the system retires. It lays emphasis on “testing before coding” through a test strategy based on requirements. This makes sure that the test cases are developed early which in turn confirms that the requirements are correct, before design and coding begins.
These are some of the basic assumptions of STEP model:

• Test strategy based on requirements
• Testing starts as the software development lifecycle begins
• Tests are aligned to requirements as well as usage
• Software design is led by testware design
• Defects must be identified in the initial stages or avoided completely
• Defects must be analyzed thoroughly
• Testers must work as a team with the developers

Sometimes, STEP model is merged with the TPI Next model.
In the next topic, we investigate the points a Test Manager must consider before selecting a testing tool.

Critical Testing Processes (CTP) model assumes that some testing processes are critical. If executed properly, the test teams will be successfully supported by the critical processes.
On the other hand, if these tests are not done properly, even the most experienced and skilled teams can fail, making the most successful testers and Test Managers fail.
CTP is mainly a content reference model and identifies 12 test processes that are critical. The CTP assessment model can be tailored as per the needs of the organizations to include:

• Identifying specific challenges
• Recognizing characteristics of good test processes
• Prioritizing suggested improvements that are important to the organization

The CTP model can be integrated within any SDLC model. CTP model uses metrics to compare companies against best practices and averages in the industry, which are derived from interviews with participants.

With TPI Next model, each facet of the testing process, like test planning, test metrics, test environment, etc. – is covered by 16 predefined areas. This model has 4 maturity levels:

• Initial
• Controlled
• Efficient
• Optimizing

Each of the 16 key areas is assessed using predefined checkpoints at each maturity level. Based on assessment results, a maturity matrix is developed to assist in visualizing and summarizing key areas.
Definition of objectives for improvement and their execution is customized according to the testing organizations needs and capacities.
TPI Next model is independent of all software development process improvement models because of its generic nature. It covers test engineering as decision support systems.

There are several industry standard models that have been created in order to improve the testing process. These software testing process improvement models are specifically tailored for testing and hence, they are better suited than other process improvement models which are usually meant for software development.
Software Testing Process Improvement Models

• Testing Maturity Model integration (TMMi)
• Test Process Improvement (TPI) Next
• Critical Testing Processes (CTP)
• Systematic Test and Evaluation Process (STEP)

Testing Maturity Model integration (TMMi)Testing Maturity Model integration (TMMi) complements the CMMI model and consists of five levels of maturity. Each level of maturity has predefined processes areas with general goals as well as goals that are specific.
The organization will be able to move to higher maturity level only after these goals are at least 85% complete.
Maturity levels defined for TMMi

• Level 1: Initial
  In this level, testing is considered equivalent to debugging and its aim is to simply prove that the software functions as expected. The testing process is not properly structured or even documented officially. The tests themselves are introduced in an unplanned manner as and when required, once coding is complete.
• Level 2: Managed
  If the testing process is separate from the debugging process, the organization reaches the managed level. To attain this level, test goals and test policy must be defined clearly. Basic steps seen in test process like creating a test plan, implementing testing methods and techniques, must be put into practice.
• Level 3: Defined
  In this level, testing is an integral part of the overall software development process. Test processes have formally defined standards, methods and processes that are documented. There is a distinct test function for software testing that is monitored and controlled and reviews occur periodically.
• Level 4: Measured
  This maturity level is attained when the test process can be efficiently measured and controlled at company level for individual projects benefit.
• Level 5: Optimized
  This highest maturity level is said to be reached if data obtained as a result of testing process is used to minimize defects. The focus at this level is to optimize the existing test processes.
  

Other popular articles:

• What is the IDEAL model for test process improvement?
• Software Testing Process Improvements for Test / QA Managers
• What is Capability Maturity Model (CMM)? What are CMM Levels?
• What is Iterative model- advantages, disadvantages and when to use it?
• What are the Software Development Models?