Issue 15644: Scheduler seems to be a tool concept (uml-testing-profile-rtf) Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de) Nature: Clarification Severity: Significant Summary: Rational: Scheduler is a predefined interface defining operations used for controlling the tests and the test components. None of the operations of the Scheduler are available to the UML specifier. Issue: The usage of the scheduler is not clear. Scheduler seems to be a pure tool concept. Section 6.3.1 Test Architecture, Subsection Scheduler says the following: Scheduler is a predefined interface defining operations used for controlling the tests and the test components. None of the operations of the Scheduler are available to the UML specifier. The implementation of the predefined interface will determine the detailed semantics. The implementation must make sure that the scheduler has enough information to keep track of the existence and participation of the test components in every test case. The test context itself will ensure the creation of a scheduler. Hence, the scheduler cannot be used within the test model as it is not visible to the UML elements. The specification should separate between model elements and interfaces to the test execution system, which can be seen as technical issues. Resolution: Revised Text: Actions taken: September 27, 2010: received issue October 21, 2011: closed issue Discussion: Scheduler is not part of the profile (of any test specification model) and confuses reader. It is a dedicated tool concept and will be moved into the Annex. Disposition: See issue 16163 for disposition End of Annotations:===== m: webmaster@omg.org Date: 27 Sep 2010 07:38:19 -0400 To: 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 (UTP) Section: 6.3.1 FormalNumber: formal/2005-07-07 Version: 1.0 Doc_Year: 2007 Doc_Month: July Doc_Day: 07 Page: 12 Title: Scheduler seems to be a tool concept Nature: Clarification Severity: Significant CODE: 3TMw8 B1: Report Issue Description: Rational: Scheduler is a predefined interface defining operations used for controlling the tests and the test components. None of the operations of the Scheduler are available to the UML specifier. Issue: The usage of the scheduler is not clear. Scheduler seems to be a pure tool concept. Section 6.3.1 Test Architecture, Subsection Scheduler says the following: Scheduler is a predefined interface defining operations used for controlling the tests and the test components. None of the operations of the Scheduler are available to the UML specifier. The implementation of the predefined interface will determine the detailed semantics. The implementation must make sure that the scheduler has enough information to keep track of the existence and participation of the test components in every test case. The test context itself will ensure the creation of a scheduler. Hence, the scheduler cannot be used within the test model as it is not visible to the UML elements. The specification should separate between model elements and interfaces to the test execution system, which can be seen as technical issues.