Pass the iSQI TMMi certification TMMi-P_Syll2.1 Questions and answers with CertsForce

With a 40% achievement in the Test Planning process area, the rating would be "Partly achieved." According to TMMi, a process area is rated "Partly achieved" when the percentage of achievement is between 15% and 50%. This indicates that some practices have been implemented, but significant improvement is still required to meet the full requirements of the process area.

This statement is FALSE because in the staged representation of CMMI, there are fixed levels or stages that an organization must proceed through in a predefined sequence. These stages guide organizations to improve their processes systematically by following a maturity path, with each stage building on the processes defined in the previous one.

The staged representation is designed with predefined levels that organizations must achieve in an orderly manner, making sure that process improvements at each level lay the foundation for the next one.

In contrast, the continuous representation allows organizations to select specific process areas from various categories based on their improvement goals and does not impose a strict sequence of levels.

TMMi References:

The CMMI documentation within TMMi clearly states that the staged representation involves a fixed set of levels through which organizations progress​.

CMMI also has a continuous representation where organizations can select improvement areas freely from different process categories​.

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.

A specific practice is an expected component of the TMMi model. Expected components describe what an organisation will typically implement to achieve required components, such as specific and generic goals. Specific practices are activities that are crucial for achieving the specific goals of a process area, and they are evaluated during assessments to determine whether the goals have been met.

The process area Test Lifecycle and Integration at TMMi Level 3 focuses on establishing a coherent test process across multiple test levels and integrating the test lifecycle with the development lifecycle. This process area addresses the creation of a master test plan, which is essential for ensuring consistency and avoiding redundancy or omissions across different test levels.

The specific goal and practice for establishing a master test plan are well documented within the Test Lifecycle and Integration process area. Practices include performing a product risk assessment, establishing the test approach, and developing the master test plan itself​​.

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 an Agile context, the emphasis is typically placed on lightweight, flexible documentation. Test documentation should be "just enough" to support the test process, and excessive documentation may be seen as unnecessary overhead. Therefore, calling for more rigorous and thorough documentation is not in line with Agile principles. Instead, Agile favours working software and collaboration over comprehensive documentation, supported by mentoring and just-in-time guidance rather than formalised documentation​.

A typical business reason for starting a test improvement program is to achieve higher productivity. Test process improvements can lead to better efficiency in test execution, reduction of defects, and optimised resource usage, all of which contribute to the overall productivity of the organisation. By improving testing processes, organisations can reduce time-to-market and minimise costs associated with fixing defects post-production, which in turn boosts productivity.

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 References:

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​​.

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.