<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>P058 - Testing of Component-Based Systems and Software Quality 2004</title>
<link href="http://dl.gi.de/handle/20.500.12116/28483" rel="alternate"/>
<subtitle/>
<id>http://dl.gi.de/handle/20.500.12116/28483</id>
<updated>2026-07-21T13:35:40Z</updated>
<dc:date>2026-07-21T13:35:40Z</dc:date>
<entry>
<title>Testing in the component age</title>
<link href="http://dl.gi.de/handle/20.500.12116/28501" rel="alternate"/>
<author>
<name>Winter, Mario</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/28501</id>
<updated>2019-10-11T10:37:54Z</updated>
<published>2004-01-01T00:00:00Z</published>
<summary type="text">Testing in the component age
Winter, Mario
Beydeda, Ksami; Gruhn, Volker; Mayer, Johannes; Reussner, Ralf; Schweiggert, Franz
At the end of the last century, quality and especially reusability problems of object-oriented software cropped out. As a remedy, nowadays component based software development resounds throughout the developer communities. Nevertheless the special aspects of testing component based systems often remain overlooked. After characterizing the main differences between object-oriented and componentbased software, this paper firstly surveys some basic concepts of component development and software testing. Then applicable techniques for specification and black-box testing of components are depicted, and particularly contract-based test case specification for component interfaces is emphasized. On this groundwork, some new testing levels and testing roles which have to be played in component based software development are proposed. The paper ends with some prospects on appropriate testing tools.
</summary>
<dc:date>2004-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Measuring the effectiveness of software testing</title>
<link href="http://dl.gi.de/handle/20.500.12116/28500" rel="alternate"/>
<author>
<name>Sneed, Harry M.</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/28500</id>
<updated>2019-10-11T10:37:54Z</updated>
<published>2004-01-01T00:00:00Z</published>
<summary type="text">Measuring the effectiveness of software testing
Sneed, Harry M.
Beydeda, Ksami; Gruhn, Volker; Mayer, Johannes; Reussner, Ralf; Schweiggert, Franz
In 1978 Harry Sneed set up the first commercial software test laboratory in Budapest charging DM 75,- per test case and DM 100,- for each error found. The laboratory was used to test the Integrated Transport Steuerung system of the German railroad and the BS2000 operating system of Siemens. Today, some 26 years later, managers are looking for a means to justify the cost of testing. While working as a test consultant for a Viennese software house from 1998 until 2003, Harry Sneed conceived a set of metrics for measuring the effectiveness of the test operations there. These metrics were intended to measure the performance of the test department, but they are equally valid for measuring test operations anywhere. In fact, with these metrics it should be possible to convert software testing from an art as perceived by Glenford Meyers in 1975 to a science as defined by Lord Kelvin in 1875. The metrics were obtained using the Goal/Question/Metric Method of Basili and Rombach and were refined through three years of practical application. In effect, they are a continuation of the test measurement work Sneed began as a young test entrepreneur in 1978. They are supported by a set of tools designed for both static and dynamic analysis as well as for evaluating the results of both. Working as a test team leader at the Wirtschaftskammer in Vienna, Sneed applied these metrics to successfully predict the test effort required to test a complex web application. From this presentation the attendants will be exposed to the experience of 30 years of software testing.
</summary>
<dc:date>2004-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>A strategy to improve component testability without source code</title>
<link href="http://dl.gi.de/handle/20.500.12116/28496" rel="alternate"/>
<author>
<name>Ribeiro Rocha, Camila</name>
</author>
<author>
<name>Martins, Eliane</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/28496</id>
<updated>2019-10-11T10:37:53Z</updated>
<published>2004-01-01T00:00:00Z</published>
<summary type="text">A strategy to improve component testability without source code
Ribeiro Rocha, Camila; Martins, Eliane
Beydeda, Ksami; Gruhn, Volker; Mayer, Johannes; Reussner, Ralf; Schweiggert, Franz
A software component must be tested every time it is reused, to guarantee the quality of both the component itself and the system in which it is to be integrated. To reduce testing costs, we propose a model to build highly testable components by embedding testing and monitoring mechanisms inside them. The approach is useful to component developers, who can use these built-in test capabilities in the testing phase, as well as to component users, who can verify whether the component fulfills its contract. Our approach proposes the insertion of built-in mechanisms directly into intermediate code, allowing its use even in COTS components.
</summary>
<dc:date>2004-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Safety assessment of systems embedded with COTS components by PIP technique</title>
<link href="http://dl.gi.de/handle/20.500.12116/28499" rel="alternate"/>
<author>
<name>Chen, Luping</name>
</author>
<author>
<name>May, John</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/28499</id>
<updated>2019-10-11T10:37:53Z</updated>
<published>2004-01-01T00:00:00Z</published>
<summary type="text">Safety assessment of systems embedded with COTS components by PIP technique
Chen, Luping; May, John
Beydeda, Ksami; Gruhn, Volker; Mayer, Johannes; Reussner, Ralf; Schweiggert, Franz
The difficulties to assess reliability of systems that use COTS components are sometimes compounded by the inaccessibility of some COTS codes. This paper develops an approach of Perturbation of Interface Parameters (PIP) to simulate failures of COTS components. It is to validate the use of PIP as a fault-injection technique to test COTS components and surrounding systems. Tests of a nuclear protection system will be presented to demonstrate that PIP can be used to assess and aid safety designs in COTS based software.
</summary>
<dc:date>2004-01-01T00:00:00Z</dc:date>
</entry>
</feed>
