Issue 16901: TestComponent stereotype should extend Property (uml-testing-profile-rtf)
Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de)
Nature: Clarification
Severity: Minor
Summary: In situations where components already exist which shall be reused for the test architecture, it is contra-productive that test component only extends StructuredClassifier. This requires always the creation of a completely new test component (maybe using generalization) for the test architecture.


Treating TestComponent, in addition to its current representation, similar to <<SUT>> (which extends Property) would result in more flexibility since existing classifier can be reused for being both the SUT and a TestComponent in different tets context.
This is in particular helpful for reusing existing classifier.

This way would ot restrict the situation where completely new tets component classifiers must be created (maybe though generalization from already existing classifier in the system model). Current approaches would not become invalid, in contrast, this would result in a more precise and clear test configuration.
Resolution: Deferred due to time restrictions.
Disposition: Deferred
Revised Text: 
Actions taken:
December 14, 2011: received issue
Discussion: 

End of Annotations:=====

m: webmaster@omg.org
Date: 14 Dec 2011 02:13:20 -0500
To: <issues@omg.org>
Subject: Issue/Bug Report


*******************************************************************************
Name:            Marc-Florian Wendland
Employer:        Fraunhofer FOKUS
mailFrom:        marc-florian.wendland@fokus.fraunhofer.de
Terms_Agreement: I agree
Specification:   UML Testing Profile
Section:         7.1.2.3
FormalNumber:    ptc/2011-07-19
Version:         1.1 - beta 1
Doc_Year:        2011
Doc_Month:       July
Doc_Day:         19
Page:            11f
Title:           TestComponent stereotype should extend Property
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


In situations where components already exist which shall be reused for the test architecture, it is contra-productive that test component only extends StructuredClassifier. This requires always the creation of a completely new test component (maybe using generalization) for the test architecture.


Treating TestComponent, in addition to its current representation, similar to <<SUT>> (which extends Property) would result in more flexibility since existing classifier can be reused for being both the SUT and a TestComponent in different tets context.
This is in particular helpful for reusing existing classifier.

This way would ot restrict the situation where completely new tets component classifiers must be created (maybe though generalization from already existing classifier in the system model). Current approaches would not become invalid, in contrast, this would result in a more precise and clear test configuration.