UTP11 — Test management should be supported

There is missing support of test management issues within the current version of UTP in contradiction to the fact, that test frameworks usually are supported by a tool based or manual test management process.
One of the major tasks of test management is to decide, which test cases must be executed. In safety-critical environments, good rationale shall be given if test cases are ommited. To establish corresponding process interfaces from model based test design to test management, the test models have to be enriched with test management features.
Currently, UTP test cases are supposed to be independent of the specific configuration of the SUT. If product variants are tested, specific test cases may be required that only apply to one or several variants (but not all).
This is very important to fulfill basic regulatory affairs, e.g. IEEE 826 defining the content of test plan and test design.
Example 1: A test case attribute "priority" in the model can be used, to include the design of prioritized test sets within the model used for stakeholder review and later for test suite management in the test management tool used.
Example 2: Explicite tags for requirements as model attributes to test cases enable a traceable and efficient requirements based test design with UTP models and can be used as a basis for tool interfaces / synchronization tools between requirements engineering and test design.

Test management aspects become more and more important. UTP should target those aspects as well. Since test management is not in scope of the initial RFP of the UTP, the RTF decided to define a basic set of test management attributes in an additional non-normative annex.
The RTF defined a common set of important attributes which are reusable for a lot of test management aspects (like version, description…). Those information are grouped in a newly created stereotype called ManagedElement. As part of the resolution, an issue will be submitted to the UML, since most of those information are general purpose information and should be included in UML as well.
Additionally, some more test-specific attributes are added directly into already existing concepts to enable them for test management purposes.