Download iSQI.TMMi-P_Syll2.1.VCEplus.2024-11-13.59q.tqb

In the TMMi framework, a Specific Goal is unique to a particular process area and represents the essential outcomes that must be achieved for that process area. In contrast, a Generic Goal applies across multiple process areas and ensures that the processes are institutionalised, managed, and aligned with broader organisational objectives. Generic Goals help maintain consistency and effectiveness of processes across the organisation, while Specific Goals focus on the particular needs of an individual process area.Reference: 'Generic goals are called 'generic' because the same goal statement appears in all process areas. Specific goals describe unique characteristics of a process area'.

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.Reference: 'Expected components describe practices that are critical to achieving goals. These practices must either be implemented as described or replaced with acceptable alternatives'.

Sub-practices are informative components within the TMMi model. Informative components provide additional details or guidance to help organisations understand how to approach the required and expected components.Sub-practices are not mandatory, but they offer ideas or methods that can assist with the implementation of specific practices. Other examples of informative components include example work products, notes, and references.Reference: 'Sub-practices are a detailed description that provides guidance for interpreting and implementing a specific practice. Sub-practices are informative components'.

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.Reference: 'The TMMi process areas provide support and a more detailed specification, especially of what is required to establish a defined verification and validation process'. 

To improve the quality of test cases and reduce defects in production, addressing the practice of 'Identify and Prioritize Test Conditions' under Specific Goal 1 (SG 1) of the Test Design and Execution process area is essential.This specific practice involves identifying conditions based on an analysis of the test items and prioritising them based on risk and other factors. By improving the identification and prioritisation of test conditions, organisations can ensure that they focus on the most critical aspects of the system, thereby increasing the effectiveness of their testing efforts and reducing defects in production.Reference: 'SP 1.1 Identify and prioritize test conditions... Test conditions are identified and prioritized using test design techniques based on an analysis of the test items as specified in the test basis'.

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.Reference: 'TMMi Level 2 Test Planning SG 3 Establish Test Estimates is key for addressing issues related to inaccurate test estimations'.

CMMI and TMMi complement each other in many ways. While CMMI focuses on improving broader software development processes, TMMi specifically addresses testing. Implementing CMMI provides value to test organizations by enabling a structured and continuous improvement approach that can incorporate TMMi as part of the overall process.CMMI's continuous representation allows organizations to implement specific process areas related to testing (like verification and validation) and integrate TMMi practices for continuous improvement in their testing processes. Organizations following TMMi may also refer to CMMI practices for complementary process improvements in areas such as configuration management, planning, and performance measurement.TMMiReference:TMMi outlines how CMMI's process areas, such as Verification and Validation, provide critical value for testing organizations.CMMI's structure supports continuous process improvement that aligns well with TMMi's structured approach to test process maturity.

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.TMMiReference: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 be versatile and applicable across all test levels (including static and dynamic testing) and all types of development methodologies, such as waterfall, Agile, and DevOps. It provides comprehensive coverage of the testing process, ensuring that all critical aspects of testing---such as lifecycle processes, techniques, infrastructure, and organization---are addressed.TMMi is not limited to specific development methods or organizational sizes; it is lifecycle-independent and can be used effectively with various development approaches, making it widely applicable in both small and large organizations.TMMiReference:TMMi covers all test levels, including both static testing (such as reviews) and dynamic testing at multiple stages, and is applicable across different software development lifecycles.

Advanced Reviews is a TMMi Level 4 process area. At TMMi Level 4 (Measured), organizations focus on making testing a quantifiable process, using metrics and measurements to evaluate and improve product quality and the testing process. Advanced Reviews involve more structured and formalized review processes that are integrated with the dynamic testing approach to measure and improve product quality earlier in the lifecycle.The Test Policy and Strategy is part of Level 2.Defect Prevention is part of Level 5.Test Lifecycle and Integration is part of Level 3.TMMiReference:TMMi defines Advanced Reviews as a Level 4 process area aimed at improving product quality through more rigorous and measurable review processes.