Issue 16000: TestRequirements shall be defined (uml-testing-profile-rtf) Source: Fraunhofer FOKUS (Mr. Marc-Florian Wendland, marc-florian.wendland(at)fokus.fraunhofer.de) Nature: Enhancement Severity: Minor Summary: The UTP contains a stereotype <<TestObjective>>, connects either a test context of test case to any model element, expressing the purpose/objective of the test case or the test context. However, most standards related to testing define standalone specifications of such a test case's target in forms of test purposes (ETSI) or test requirements (IEEE/ISQTB). It would be good to have a dedicated stereotype <<TestRequirement>> to express the test case descriptions, similar to system requirements (for example stereotype <<Requirement>> in SysML). It should have atleast an ID, a name, a description and a priority Resolution: Merged with issue #15931 Disposition: see resolution of issue #15931 for disposition Revised Text: Actions taken: January 31, 2011: received issue January 7, 2013: closed issue Discussion: Deferred due to time restrictions End of Annotations:===== m: webmaster@omg.org Date: 31 Jan 2011 10:04:54 -0500 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 Section: n/a FormalNumber: formal/05-07-07 Version: 1.0 Doc_Year: 2005 Doc_Month: July Doc_Day: 07 Page: n/a Title: TestRequirements shall be defined Nature: Enhancement Severity: Minor CODE: 3TMw8 B1: Report Issue Description: The UTP contains a stereotype <>, connects either a test context of test case to any model element, expressing the purpose/objective of the test case or the test context. However, most standards related to testing define standalone specifications of such a test case's target in forms of test purposes (ETSI) or test requirements (IEEE/ISQTB). It would be good to have a dedicated stereotype <> to express the test case descriptions, similar to system requirements (for example stereotype <> in SysML). It should have atleast an ID, a name, a description and a priority.