The specific practice "Establish the Organization’s Test Process Database" is found within the Test Lifecycle and Integration process area, which is part of TMMi Level 3. This process area aims to establish standardized test processes across the organization, including maintaining a test process database that holds process-related information and data for reuse and continuous improvement.
TMMi References:
The Test Lifecycle and Integration process area is responsible for establishing and maintaining organizational test process assets, including the test process database.
Question # 35
Which of the following statements is TRUE with respect to TMMi Levels 4 and 5 in an Agile context?
Options:
A.
Because Agile projects tend to focus on defect detection rather than defect prevention, Process area 5.1 Defect Prevention is less relevant when assessing an Agile organisation for TMMi level 5.
B.
Process area 4.3 Advanced Reviews is less relevant in an Agile context because quality tends to be a team effort and verification and validation tend to be discussed at team meetings, not in formal reviews.
C.
When considering the achievement of specific goals in process area 5.3 Test Process Optimization in an Agile context, the deployment of new testing technologies and test improvements do not have to be made across the whole organization, since Agile teams are autonomous and can decide which improvements suit their way of working best.
D.
Agile projects normally do not use operational profiles or usage models of a product on which to base statistically valid inferences to help create a representative sample of tests, thus the TMMi level 5 specific goal “Testing is performed using Statistical Methods” is considered not relevant in an Agile context.
In an Agile context, some practices from TMMi levels 4 and 5 might be considered less relevant or adjusted to fit the Agile methodology. Specifically, at TMMi level 5, testing with statistical methods may indeed be less relevant. In Agile projects, operational profiles or usage models, which are essential to perform statistically valid testing, are often not utilised. Agile methodologies focus more on incremental development and continuous feedback loops, which do not typically rely on statistical sampling methods. Therefore, the statement that "Agile projects normally do not use operational profiles or usage models of a product on which to base statistically valid inferences to help create a representative sample of tests, thus the TMMi level 5 specific goal 'Testing is performed using Statistical Methods' is considered not relevant in an Agile context" is true.
Question # 36
Which test level can NOT be improved using the TMMi model?
Options:
A.
Static testing, e.g., reviews
B.
Component testing
C.
User acceptance testing
D.
All levels of testing can be within the scope of a TMMi based test process improvement programme.
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 static and dynamic techniques. Therefore, all levels of testing can be improved using the TMMi model.
[Reference:The TMMi document clearly states, "TMMi addresses all test levels (including static testing)"., ]