Pass the iSQI TMMi certification TMMi-P_Syll2020 Questions and answers with ExamsMirror

The specific practice "Define a coordinated approach that coordinates both static and dynamic testing" is part of theAdvanced Reviewsprocess area at TMMi Level 4. The goal of this process area is to integrate static and dynamic testing, particularly through peer reviews, which helps optimise both defect detection and product quality management throughout the lifecycle​​​.

The statement thatall defects should be analyzedto prevent as many defects as possible isFALSE. In theDefect Preventionprocess area atTMMi Level 5, only asubset of defects—those that are recurring or considered to be of significant impact—are analyzed. Analyzing all defects would be inefficient and not always necessary. Instead, a targeted approach is used to identifycommon causesof defects and implement actions to prevent their recurrence.

TMMi References:

TheDefect Preventionprocess area is based on the analysis of a subset of defects to find and eliminate common causes​​.

A test policy is a high-level document that outlines the objectives, goals, and strategic views regarding testing. It serves to align testing activities with the organisation's business objectives and quality goals. One of the critical elements in a test policy is defining thequality levels to be achieved, which ensures that testing aligns with the expectations for product quality, both functional and non-functional. Other aspects, such as risk categories, test types, and regression testing approaches, are typically defined in more detailed test strategies or plans, not in the high-level policy.

For aformal TMMi assessment, bothstaff interviews and document studyare required to collect sufficient evidence. The assessment must adhere to the TMMi Assessment Method Accreditation Requirements (TAMAR), which state that formal assessments require thecorroboration of interview data with documentary evidence (artifacts). These can include documents, templates, or screenshots, ensuring that the evaluation is robust, repeatable, and auditable​​.

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.

The description provided—where testing ismulti-level, with distinct test levels (component, integration, system, and acceptance), and where the processes of testing and debugging are differentiated—applies toTMMi Level 2 (Managed). At this maturity level, testing is separated from debugging, and there are formalized processes for different testing levels. A company-wide or program-wide test strategy is established, and specific testing objectives are defined for each test level.

TMMi References:

TheTMMi Level 2framework defines structured testing withmultiple levels, including component, integration, system, and acceptance testing, as well as the separation of testing and debugging​​.

In the scenario described, where an organisation suffers from poor test estimations despite many practices being in place, the process area that requires attention is Test Planning. Specifically,SG 3 (Establish Test Estimates)focuses on developing well-founded estimates for testing effort and cost. This includes creating a top-level work breakdown structure, defining the test lifecycle, and determining estimates for the test effort and costs associated with different test activities. By addressing these practices, the organisation can improve its ability to generate accurate test estimations, leading to better project planning and resource allocation.

To improve the management and control of test environments, one of the specific practices under SG 3 (Manage and Control Test Environments) of the Test Environment process area is to coordinate the availability and usage of test environments. This involves managing reservations, scheduling, and ensuring the efficient use of test environments across different projects. This practice is essential for ensuring that the test environments are available when needed, reducing delays, and improving the overall efficiency of the testing process.

TheDebugging-oriented phasefrom Gelperin and Hetzel's evolutionary testing model is associated withMaturity 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 1organizations 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:

TheTMMi frameworkdraws directly from the evolutionary model of Gelperin and Hetzel, associating theDebugging-oriented phasewith Level 1, which describes a chaotic, unmanaged testing environment​​.

Regularcode reviewsandarchitectural reviewsare part of theAdvanced Reviewsprocess area, which belongs toTMMi Level 4. This process area emphasizes conducting static reviews (e.g., code and design reviews) early in the lifecycle to measure product quality and adjust the testing strategy based on the insights gained from these reviews.

TMMi References:

TheAdvanced Reviewsprocess area in TMMi Level 4 aims to ensure that static testing activities such as code and architectural reviews are used to measure product quality early in the lifecycle​​.