<?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>P023 - Software Management 2002: Progress through Constancy</title>
<link href="http://dl.gi.de/handle/20.500.12116/30120" rel="alternate"/>
<subtitle/>
<id>http://dl.gi.de/handle/20.500.12116/30120</id>
<updated>2026-07-22T22:10:59Z</updated>
<dc:date>2026-07-22T22:10:59Z</dc:date>
<entry>
<title>Management des Testprozesses von Anfang an – Das W-Modell</title>
<link href="http://dl.gi.de/handle/20.500.12116/30139" rel="alternate"/>
<author>
<name>Spillner, Andreas</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/30139</id>
<updated>2019-11-14T12:43:39Z</updated>
<published>2002-01-01T00:00:00Z</published>
<summary type="text">Management des Testprozesses von Anfang an – Das W-Modell
Spillner, Andreas
Spitta, Thorsten; Borchers, Jens; Sneed, Harry M.
In software development, 30 to 40 % of all software activities are testing related. That is why it is critical to launch testing activities at the beginning of the project rather than after the coding is completed. While new software development models such as the Rational Unified Process and eXtreme Programming (XP) continue to be popular with practitioners, the V-model has gained particularly wide acceptance. Based on the V-model, this paper describes a model that shows how the tasks for testing relate to the tasks in the development model. This model – the W-model – further clarifies the priority of the tasks and the dependence between the development and testing activities. Although as simple as the V-model, the W-model makes the importance of testing and the ordering of the individual testing activities clear. It also clarifies that testing and debugging are not the same thing.
</summary>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Unterstützung der Release-Planung mittels priorisierten Use Cases</title>
<link href="http://dl.gi.de/handle/20.500.12116/30140" rel="alternate"/>
<author>
<name>Küng, Peter</name>
</author>
<author>
<name>Krause, Heinrich</name>
</author>
<author>
<name>Worms, Carl F.</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/30140</id>
<updated>2019-11-14T12:43:39Z</updated>
<published>2002-01-01T00:00:00Z</published>
<summary type="text">Unterstützung der Release-Planung mittels priorisierten Use Cases
Küng, Peter; Krause, Heinrich; Worms, Carl F.
Spitta, Thorsten; Borchers, Jens; Sneed, Harry M.
Requirements represent essential input for software projects and, thus, need to be defined clearly. Unfortunately requirements often are not prioritised systematically. As a consequence, it is not determined in the early phases of a project which functions (or functional requirements) are going to be covered by which release. This paper suggests a technique to prioritise requirements and to assign them to software releases. Special emphasis is given on the fact that cost and benefit of each functional requirement are taken into consideration before a decision is taken.
</summary>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Themenzentrierte Interaktion in IT-Projekten</title>
<link href="http://dl.gi.de/handle/20.500.12116/30137" rel="alternate"/>
<author>
<name>Müller, Thomas</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/30137</id>
<updated>2019-11-14T12:43:38Z</updated>
<published>2002-01-01T00:00:00Z</published>
<summary type="text">Themenzentrierte Interaktion in IT-Projekten
Müller, Thomas
Spitta, Thorsten; Borchers, Jens; Sneed, Harry M.
In IT-Projekten wird methodisch geplant, entworfen und entwickelt. Doch die Art und Weise, wie man im Team zusammenarbeitet, bleibt meist dem Zufall überlassen – mit manchmal katastrophalen Folgen: Motivationsverlust und Konflikte können den Projekterfolg ernsthaft gefährden. Das muss nicht sein: Themenzentrierte Interaktion (TZI) ist eine bewährte Methode, um die Zusammenarbeit von Menschen in Projekten effizient und anregend zu gestalten – auch in der nüchternen Welt der Informationstechnologie. Was TZI ist und wie man sie in IT-Projekten sinnvoll nutzt, das beschreibt der folgende Beitrag.
</summary>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>SPiCE in action – Experiences in Tailoring and Extension</title>
<link href="http://dl.gi.de/handle/20.500.12116/30135" rel="alternate"/>
<author>
<name>Völcker, Christian</name>
</author>
<author>
<name>Cass, Ann</name>
</author>
<author>
<name>Sutter, Philipp</name>
</author>
<author>
<name>Stienen, Hans</name>
</author>
<author>
<name>Dorling, Alec</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/30135</id>
<updated>2019-11-14T12:43:38Z</updated>
<published>2002-01-01T00:00:00Z</published>
<summary type="text">SPiCE in action – Experiences in Tailoring and Extension
Völcker, Christian; Cass, Ann; Sutter, Philipp; Stienen, Hans; Dorling, Alec
Spitta, Thorsten; Borchers, Jens; Sneed, Harry M.
Experiences are reported in the use of ISO 15504 both in tailoring the standard for particular industrial sectors and in expanding the process assessment approach into new domains. In particular, three projects are discussed: SPiCE for SPACE, a ISO/IEC TR 15504 [IS98a] conformant method of software process assessment developed for the European space industry, SPiCE-9000 for SPACE, an assessment method for space quality management systems, based on ISO 9001:2000 [IS00], and NOVE-IT, a project of the Swiss federal government to establish and assess processes covering IT procurement, development, operation, and service provision. All three of these projects use the concepts of process assessment from ISO 15504; however, in each case, different strategies to apply the international standard were selected. Some of the issues faced in these different domains are described and their resolutions presented.
</summary>
<dc:date>2002-01-01T00:00:00Z</dc:date>
</entry>
</feed>
