Experiences from conducting semi-structured interviews in empirical software engineering research

By Siw Elisabeth Hove, Bente Anda. IEEE International Software Metrics Symposium, 2005

419 citations recorded by the source corpus.

Subfields: Computer Science Applications, Information Systems

View Paper: https://www.semanticscholar.org/paper/690e1d57b9c5ca3e7e348fcad257767a4a2c1011

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

In Computer Science Applications

1. Per Runeson
2. Martin Höst
3. Claes Wohlin

In Information Systems

1. Martin Höst
2. Per Runeson
3. Claes Wohlin
4. Emerson R. Murphy-Hill
5. Brittany Johnson
6. Björn Regnell
7. Paolo Tonella
8. Magnus C. Ohlsson

Citations in the corpus

• Guidelines for conducting and reporting case study research in software engineering (2009, background): “Possibly a dedicated and trained scribe may capture sufficient detail in real-time, but the recording should at least be done as a backup (Hove and Anda 2005).”
• Experimentation in Software Engineering (2012, background): “If the interview contains personal and maybe sensitive questions, for example, concerning economy, opinions about colleagues, why things went wrong, or questions related to the interviewees own competence [80], it is important that the interviewee is ensured confidentiality and that the interviewee ”
• Taxonomy of Real Faults in Deep Learning Systems (2019, background): “[14] Siw Elisabeth Hove and Bente Anda.”
• Why don't software developers use static analysis tools to find bugs? (2013, background): “By conducting “semi-structured” interviews, we aimed to achieve the flexibility needed to get as much detailed information as possible [24].”