Talks and Poster Presentations (with Proceedings-Entry):
M. Heindl, S. Biffl:
"A Framework to Balance Tracing Agility and Formalism";
Talk: IFIP CEE Software Engineering Techniques Conference,
- 2007-10-14; in: "Proceeding of CEE-SET 2007",
Abstract. Software customers want both sufficient product quality and agile response
to requirements changes. Formal software requirements tracing helps to
systematically determine the impact of changes and keep track of development
artifacts that need to be re-tested when requirements change. However, full tracing
of all requirements on the most detailed level can be very expensive and
In this paper we introduce an initial "tracing activity model", a framework that
allows measuring the expected cost and benefit of tracing approaches. We apply
a subset of the activities in the model in a study to compare 3 tracing strategies,
ranging from agile "just in time" tracing to fully formal tracing, in the context
of re-testing in an industry project at a large financial service provider.
In the study a) the model was found useful to capture costs and benefits of the
tracing activities to compare the different strategies; b) a combination of upfront
tracing on a coarse level of detail and focused just-in-time detailed tracing can
help balancing tracing agility (for use in practice) in a formal tracing framework
(for research and process improvement).
Software Requirements Tracing, Re-Test, Tracing Activity Model,
Created from the Publication Database of the Vienna University of Technology.