iSQI TMMi-P_Syll2020 - TMMi - Test Maturity Model Integration Professional

In theDefect Preventionprocess area at TMMi Level 5, one of the key specific goals (SG2) is to prioritise and define actions to systematically eliminate the root causes of defects. This involves proposing solutions to address common defect causes that have been identified during causal analysis. These solutions aim to prevent defects from reoccurring across the development lifecycle.

The specific goals of the "Test Monitoring and Control" process area at TMMi Level 2 focus on monitoring both test progress and product quality. One of the key practices is managing and monitoringtest incidents to closure(Specific Practice 3.3). The goal is to ensure that any test-related issues are tracked, addressed, and resolved. This process area emphasises identifying corrective actions when deviations occur and ensuring that they are brought to closure.

Monitoring test incidents helps provide insight into the test status and product quality while ensuring that all critical incidents are resolved effectively, thus aligning with the overall objective of controlling the testing process​​.

The TMMi process areas complement the CMMI process areas for Verification and Validation by providing more detailed guidance specific to testing. While CMMI defines these areas at a high level, TMMi elaborates on how to establish and maintain a defined testing process that includes both verification and validation activities. The relationship between the two models is complementary rather than hierarchical, meaning that improving testing processes using TMMi can lead to fulfilling CMMI requirements for Verification and Validation.

This statement isFALSEbecause TMMi doesnotfocus only on higher test levels like system and acceptance testing. In fact, TMMi coversall test levels, including lower levels like unit and integration testing, as well as static testing (e.g., reviews and inspections).

TMMi is designed to address testing at all levels of the software lifecycle and goes beyond dynamic testing (e.g., system and acceptance) to include static testing techniques as well. The model is comprehensive and is intended to support testing in bothsystems and software engineering. Furthermore, TMMi addresses the fourcornerstonesof structured testing:lifecycle,techniques,infrastructure, andorganization. These are essential to ensure a thorough and structured approach to improving test processes and aligning them with business goals.

TMMi References:

TMMi documentation clearly indicates that it coversall test levelsincluding static testing (such as peer reviews) and dynamic testing across different stages of development​​.

It is lifecycle-independent and can support different models, such as Agile, DevOps, and traditional V-models​.

Expected components in the TMMi model guide organisations on how to implement improvements or conduct assessments. These components, such as Specific Practices and Generic Practices, are necessary for satisfying goals. Expected components must be implemented, either as described or through acceptable alternatives, for an organisation to achieve compliance with the model and reach maturity in test processes.

The correct order of TMMi maturity levels fromlow to highis:

Managed(Level 2): Testing becomes a managed and separate process from debugging, with formal strategies and plans.

Defined(Level 3): Testing is fully integrated into the development lifecycle, with standardized processes across projects.

Measured(Level 4): Testing processes are measured quantitatively, and product quality is evaluated with formal metrics.

This sequence reflects the increasing maturity and sophistication of an organization's testing processes as they progress through the levels.

TMMi References:

The TMMi maturity levels follow the order ofManaged (Level 2),Defined (Level 3), andMeasured (Level 4)​​.

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 staticand dynamic techniques. Therefore, all levels of testing can be improved using the TMMi model.

The process area that addresses the definition of test functions and the establishment of test career paths is the Test Organization process area,found at TMMi Level 3. This process area focuses on creating a well-structured test organisation, defining various test functions, and establishing career paths for testers. Specific practices include defining roles for test specialists, assigning staff to those roles, and establishing career development frameworks to support the professional growth of testers within the organisation.

This statement isFALSEbecauseTMMiis flexible and does not require the imposition of a predefined set of practices in Agile organizations. Instead, it encourages the adaptation of practices to fit the Agile context. TMMi allows for alternative practices that achieve the same goals as the expected practices, making it possible to integrate testing improvements in a way that aligns with Agile principles. The focus is on continuous improvement, not compliance with rigid practices.

TMMi References:

TMMiemphasizes flexibility in adapting practices, particularly in Agile environments where imposed processes would contradict Agile values of adaptability and continuous improvement​​.

The specific practice"Maintain horizontal traceability with requirements"is part of theTest Design and Executionprocess area in TMMi. This process area ensures that there is traceability between test conditions, test cases, and requirements to ensure comprehensive test coverage. Horizontal traceability guarantees that test cases can be traced back to the specific requirements they are intended to verify, which is critical for managing and ensuring the quality of the testing process.

TMMi References:

TheTest Design and Executionprocess area includes practices that ensure test artifacts are traceable to requirements, supporting effective test coverage​​.