iSQI TMMi-P_Syll2.1 - TMMi Test Maturity Model Integration Professional (TMMi-P)

This statement is FALSE because TMMi does not focus only on higher test levels like system and acceptance testing. In fact, TMMi covers all 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 both systems and software engineering. Furthermore, TMMi addresses the four cornerstones of structured testing: lifecycle, techniques, infrastructure, and organization. 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 covers all test levels including 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​.

One of the key differences between informal and formal assessments is that informal assessments are not as rigorous. Informal assessments are more flexible, quicker, and less costly; however, they do not provide the same level of detail or accuracy as formal assessments. The statement that "informal assessments provide a result just as accurate as with a formal assessment" is therefore false. Formal assessments involve multiple types of evidence and a more thorough evaluation, while informal assessments typically rely on fewer types of evidence (often only interviews)​​.

In a staged model like TMMi, an organisation follows a predefined improvement path that includes a set of process areas organised by maturity levels. Each level builds upon the previous one, and the organisation progresses in a step-by-step manner through these maturity levels to improve its processes. The staged model is well-structured and prescriptive, offering a clear improvement roadmap for the organisation.

ISO/IEC 15504, which is known for its process assessment model, was not one of the sources used during the development of the TMMi model. The TMMi model was developed using inputs from sources such as the Capability Maturity Model Integration (CMMI), international testing standards (like those from ISO and IEEE), and industry testing best practices surveys. While the ISO/IEC 15504 model has relevance to general process assessments, it was not specifically referenced in the creation of the TMMi.

For safety-critical systems, reliability testing is a key concern. The identified shortcoming relates to the lack of formal techniques and approaches for reliability testing. The Non-Functional Testing process area, at TMMi Level 3, addresses testing non-functional aspects like reliability, performance, and usability. This process area would need specific attention as it provides a structured approach to assess non-functional risks, define testing techniques, and execute tests to verify the reliability of the product, which is critical for medical systems.

For the Test Policy and Strategy process area, with a 40% achievement, the appropriate compliance rating is "Partly achieved". According to TMMi, a process area is rated as "partly achieved" when a portion of the practices has been implemented, but significant improvements are still needed​​​.

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.

In Agile environments, TMMi is often used to complement the Agile methodology by providing structured guidance on critical testing practices that may be overlooked. While Agile focuses on flexibility and responsiveness, TMMi can remind organisations of essential practices that ensure thorough testing, such as formal reviews or defect management. The TMMi framework does not impose strict processes but offers structured support for critical test process improvements that align with Agile principles.

At TMMi Level 4, the scope includes process areas like Test Process Optimization, Product Quality Evaluation, and Advanced Reviews. However, Test Lifecycle and Integration is part of TMMi Level 3 and focuses on aligning test processes with development processes, not on Level 4. Therefore, it is not within the scope of a test improvement program aimed at achieving TMMi Level 4​​.

A. Required component (II): Must be achieved. These are specific and generic goals that are mandatory for reaching a particular maturity level.

B. Expected component (III): Will typically be implemented. Expected components include specific and generic practices, which provide guidance on how to achieve required goals.

C. Informative component (I): Supports the understanding. Informative components provide details that help organisations understand and implement the required and expected components effectively, such as sub-practices and example work products.