Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Christian Neumuller

dblp:26/3575 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 2006
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 87% Empirical software engineering · 13%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software maintenance and evolution › traceability
automated traceability
0.112006
Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne · ASE 2006
Software maintenance and evolution
traceability
0.112006
Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne · ASE 2006
Empirical software engineering › software engineering research methodology
industrial case study
0.012006
Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne · ASE 2006

Methods — techniques the papers use, named apart from their topics

case study · 0.1
YearPublicationVenuePosition
2006 Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne
abstract
There is a wide consensus on the benefits of software traceability. However, traceability techniques are still not commonly used in industry $typically only in larger companies and if mandated by standards such as the CMMI or ISO 15504. Success stories in small companies are quite rare. However, small companies represent a significant share of the IT industry and a better understanding of their needs is essential for the research community. This paper presents APIS, a traceability environment we developed and introduced in a very small software company. We discuss the traceability approach and report on key lessons learned. We have found in the project that comparably simple automation techniques are surprisingly effective. We believe that the lessons learned in this project are relevant for researchers and practitioners facing similar challenges
Christian Neumuller, Paul Grünbacher
ASE1