Testing often accounts for more than 50% of the required effort during system development. However, testing is often not well integrated with other development phases. One reason for this is that designers, developers and testers all use different languages and tools, making it difficult to communicate with each other and to exchange documents. The UML 2.0 Testing Profile bridges the gap between designers and testers by providing a means to use UML for test specification and modeling. This allows the reuse of UML design documents for testing and enables test development in an early system development phase. The testing profile provides support for UML based model-driven testing. This paper presents the concepts defined in the UML 2.0 Testing Profile and explains their usage by applying those to an example of a simplified Automated Teller Machine (ATM).
%0 Generic
%1 Baker
%A Baker, Paul
%A Dai, Zhen Ru
%A Grabowski, Jens
%A Haugen, Øystein
%A Lucio, Serge
%A Samuelsson, Eric
%A Schieferdecker, Ina
%A Williams, Clay E.
%D 2008
%K 20100923 Grey-BoxTesting TestSpecification TTCN-3 TestDesign JUnit TestLanguages Black-BoxTesting UMLProfile
%T The UML 2.0 Testing Profile
%X Testing often accounts for more than 50% of the required effort during system development. However, testing is often not well integrated with other development phases. One reason for this is that designers, developers and testers all use different languages and tools, making it difficult to communicate with each other and to exchange documents. The UML 2.0 Testing Profile bridges the gap between designers and testers by providing a means to use UML for test specification and modeling. This allows the reuse of UML design documents for testing and enables test development in an early system development phase. The testing profile provides support for UML based model-driven testing. This paper presents the concepts defined in the UML 2.0 Testing Profile and explains their usage by applying those to an example of a simplified Automated Teller Machine (ATM).
@misc{Baker,
abstract = {Testing often accounts for more than 50% of the required effort during system development. However, testing is often not well integrated with other development phases. One reason for this is that designers, developers and testers all use different languages and tools, making it difficult to communicate with each other and to exchange documents. The UML 2.0 Testing Profile bridges the gap between designers and testers by providing a means to use UML for test specification and modeling. This allows the reuse of UML design documents for testing and enables test development in an early system development phase. The testing profile provides support for UML based model-driven testing. This paper presents the concepts defined in the UML 2.0 Testing Profile and explains their usage by applying those to an example of a simplified Automated Teller Machine (ATM).},
added-at = {2010-09-23T16:27:23.000+0200},
author = {Baker, Paul and Dai, Zhen Ru and Grabowski, Jens and Haugen, Øystein and Lucio, Serge and Samuelsson, Eric and Schieferdecker, Ina and Williams, Clay E.},
biburl = {https://www.bibsonomy.org/bibtex/22d2db4a343ef9def775474afd505666c/lama},
citeseerurl = {http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.69.3680},
file = {:Baker,TheUml2.0TestingProfile.PDF:PDF},
interhash = {5808768a275b0d585310018d8255ef84},
intrahash = {2d2db4a343ef9def775474afd505666c},
keywords = {20100923 Grey-BoxTesting TestSpecification TTCN-3 TestDesign JUnit TestLanguages Black-BoxTesting UMLProfile},
timestamp = {2010-09-23T16:27:23.000+0200},
title = {The UML 2.0 Testing Profile},
year = 2008
}