Issue 15910:  Test Context must be a UML::BehavioredClassifier, too (uml-testing-profile-rtf)
Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de)
Nature: Clarification
Severity: Minor
Summary: Rational:
UTP spec, 1.0, section 6.3.1 TestArchitecture, subsection TestContext, subsubsection Description mentiones the following: 
"A structured classifier acting as a grouping mechanism for a set of test cases. The composite structure of a test context is 
referred to as test configuration. The classifier behavior of a test context is used for test control."


Issue:
Since a test context extends UML::StructuredClassifier solely, a test context will never have a classifier behavior or operations, representing the test cases of that test context. StructuredClassifiers do not care about behavior but about structure. In order to be able to add a classifier behavior to a test context, it is required, that test context stereotypes only those classifiers that are subclasses of UML::StructuredClassifier AND UML::BehavioredClassifier (context TestContext inv: self.base_StructuredClassifier.oclIsKindOf(StructuredClassifier) and self.base_StructuredClassifier.oclIsKindOf(BehavioredClassifier).

Even if in the current UML specification (haven't checked this thoroughly) all concrete subclasses of StructuredClassifier are subclasses of BehavioredClassifers, too, UTP should formally define this constraint since it is a crucial aspect of test context semantics
Resolution: 
Revised Text: 
Actions taken:
January 4, 2011: received issue
October 21, 2011: closed issue
Discussion: 
Resolution is to include the metaclass BehavioredClassifier as well into the normative description and semantics of TestContext.
Disposition:	See issue 16163 for disposition

End of Annotations:=====

m: webmaster@omg.org
Date: 04 Jan 2011 04:50:09 -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: 
Specification:   UML Testing Profile
Section:         6.3.1
FormalNumber:    formal/05-07-07
Version:         1.0
Doc_Year:        2005
Doc_Month:       July
Doc_Day:         07
Page:            13
Title:           Test Context must be a UML::BehavioredClassifier, too
Nature:          Clarification
Severity:        Minor
CODE:            3TMw8
B1:              Report Issue


Description:


Rational:
UTP spec, 1.0, section 6.3.1 TestArchitecture, subsection TestContext, subsubsection Description mentiones the following: 
"A structured classifier acting as a grouping mechanism for a set of test cases. The composite structure of a test context is 
referred to as test configuration. The classifier behavior of a test context is used for test control."


Issue:
Since a test context extends UML::StructuredClassifier solely, a test context will never have a classifier behavior or operations, representing the test cases of that test context. StructuredClassifiers do not care about behavior but about structure. In order to be able to add a classifier behavior to a test context, it is required, that test context stereotypes only those classifiers that are subclasses of UML::StructuredClassifier AND UML::BehavioredClassifier (context TestContext inv: self.base_StructuredClassifier.oclIsKindOf(StructuredClassifier) and self.base_StructuredClassifier.oclIsKindOf(BehavioredClassifier).

Even if in the current UML specification (haven't checked this thoroughly) all concrete subclasses of StructuredClassifier are subclasses of BehavioredClassifers, too, UTP should formally define this constraint since it is a crucial aspect of test context semantics