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.

Werner Kobitzsch

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

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

Software engineering, systems software and programming languages · 1

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
Empirical software engineering · 56% Requirements engineering and software design · 44%

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

TopicWeightPapersLastEvidence papers
Empirical software engineering › software engineering research methodology
industrial case study
0.012001
An industrial case study of implementing software risk management · ESEC / SIGSOFT FSE 2001
Requirements engineering and software design
risk management
0.012001
An industrial case study of implementing software risk management · ESEC / SIGSOFT FSE 2001
Empirical software engineering
software project management
0.012001
An industrial case study of implementing software risk management · ESEC / SIGSOFT FSE 2001

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

riskit method · 0.0case study · 0.0
YearPublicationVenuePosition
2001 An industrial case study of implementing software risk management
abstract
Explicit risk management is gaining ground in industrial software development projects. However, there are few empirical studies that investigate the transfer of explicit risk management into industry, the adequacy of the risk management approaches to the constraints of industrial contexts, or their cost-benefit. This paper presents results from a case study that introduced a systematic risk management method, namely the Riskit method, into a large German telecommunication company. The objective of the case study was (1) to analyze the usefulness and adequacy of the Riskit method and (2) to analyze the cost-benefit of the Riskit method in this industrial context. The results of (1) also aimed at improvement and customization of the Riskit method. Moreover, we compare our findings with results of previous case studies to obtain more generalized conclusions on the Riskit method. Our results showed that the Riskit method is practical, adds value to the project, and that its key concepts are understood and usable in practice. Additionally, many lessons learned are reported that are useful for the general audience who wants to transfer risk management into new projects.
Bernd G. Freimut, Susanne Hartkopf, Jyrki Kontio, Werner Kobitzsch
ESEC / SIGSOFT FSE5