TMMi-P_Syll2.1: TMMi Test Maturity Model Integration Professional

The Debugging-oriented phase from Gelperin and Hetzel's evolutionary testing model is associated with Maturity Level 1 'Initial' of TMMi. At this maturity level, testing is not yet a distinct and well-defined process but is often interleaved with debugging. Organizations at this level have chaotic and ad-hoc testing activities, with no separation between testing and debugging.

Maturity Level 1 organizations lack formal processes, and testing is often reactive, performed alongside fixing bugs in the code. This is in line with the debugging-oriented phase, where testing and debugging are seen as part of the same activity.

TMMi

Reference:

The TMMi framework draws directly from the evolutionary model of Gelperin and Hetzel, associating the Debugging-oriented phase with Level 1, which describes a chaotic, unmanaged testing environment.

The TMMi model is designed to support test process improvement in both software engineering and systems engineering. This is critical because it addresses the needs of total system development, which may include hardware and software. The model covers various testing activities across different disciplines, allowing organisations to improve their test processes regardless of whether they focus solely on software or integrated systems.

Reference: 'The TMMi is intended to support testing activities and test process improvement in both the systems engineering and software engineering disciplines'.

In an Agile context, testing is often a shared responsibility among team members. This means that improvement ideas related to testing can come from any team member, not just dedicated testers. Agile encourages cross-functional collaboration, and because of the continuous feedback loops, all team members contribute to the refinement of both development and testing processes. This distributed responsibility fosters a more dynamic environment for test process improvements, where insights are drawn from diverse team roles.

Reference: 'TMMi acknowledges that in Agile environments, testing tasks are not isolated to testers, and team-wide participation leads to diverse input on process improvements'.

At TMMi Level 5, the Quality Control process area becomes relevant as it focuses on statistically managing and controlling the test process. Since the organisation is already at TMMi Level 4, moving to Level 5 involves ensuring that the test process is fully predictable, measured, and statistically controlled. Quality Control is a key process area in achieving TMMi Level 5 compliance, alongside other areas such as Defect Prevention and Test Process Optimization.

Reference: 'TMMi Level 5 includes Quality Control, a process area aimed at statistically managing the test process and making it more predictable'.

The process areas Test Organization and Test Life Cycle and Integration at TMMi Level 3 most strongly build on the practices and experiences of Test Planning from TMMi Level 2. Test Organization focuses on institutionalising the testing roles and responsibilities across the lifecycle, while Test Life Cycle and Integration ensures that testing is integrated throughout the development lifecycle, improving coordination and planning of test activities across different phases of the project.

Reference: 'Test Organization and Test Life Cycle and Integration are critical areas that build upon the foundational practices established in the Test Planning process area'.

Test Design and Execution is a key process area at TMMi Level 2, not Level 3. However, other process areas at TMMi Level 3 include Non-functional Testing, Peer Reviews, and Test Lifecycle and Integration. Test Design and Execution plays a foundational role in laying down the practices for creating and executing test cases, especially at earlier maturity levels. By TMMi Level 3, processes become more sophisticated with a broader range of testing techniques and integration into the overall lifecycle.

Reference: 'TMMi level 3 includes process areas such as Non-functional Testing, Test Lifecycle and Integration, and Peer Reviews'.

The TMMi framework is applicable to all levels of testing, including static testing (such as reviews) and dynamic testing, regardless of the phase of the software development lifecycle. TMMi encompasses structured testing activities across various test levels such as component testing, integration testing, system testing, and user acceptance testing, along with both static and dynamic techniques. Therefore, all levels of testing can be improved using the TMMi model.

Reference: The TMMi document clearly states, 'TMMi addresses all test levels (including static testing)'.