english | deutsch

SEMINAR EMPIRICAL SOFTWARE ENGINEERING

empricialslide-shadow

COURSE MANAGEMENT

  • Registration in STINE (Modul InfM-EMSE)
  • Course material in Moodle
    • To login you need to use the UHH-kennung (e.g., used for Eduroam, or the Studium Mail-Address)
    • The username of this login typically looks like this “inny700” (four letters followed by three numbers)

LEVEL

Master Seminar (Informatics, ITMC, Intelligent Adaptive Systems, Information Systems). Part of the Module “EMSE: Empirical Software Engineering”.

LECTURER

Prof. Dr. Walid Maalej

TEACHING ASSISTANTS

SEMINAR DESCRIPTION

This seminar has a special focus on empirical methods. We will introduce both qualitative and quantitative methods such as surveys, interviews, observations, content analysis, and experiments and discuss potential applications in software projects. In particular, the seminar discusses the application of empirical methods to software comprehension, collaboration, and knowledge sharing in software projects, requirements engineering, and software architecture.

This seminar will represent the exercise part of the module. We will combine the scientific literature survey, case-based teaching method with a gamification approach.

PREREQUISITES:

The seminar requires the active participation in two courses:

SEMINAR GROUPS (UNDER CONSTRUCTION)

You will have to actively participate in one of the following seminar groups.

GROUP DATE START END ROOM MINCOMMSY ROOM
EMSE Gr. 1 Monday 12:00 14:00 D-220 Seminar EMSE Gr. 1
EMSE Gr. 2 Monday 12:00 14:00 C-221 Seminar EMSE Gr. 2
EMSE Gr. 3 Monday 12:00 14:00 D-125/D129 Seminar EMSE Gr. 3

PRELIMINARY SYLLABUS AND LIST OF PAPERS (CASES)

DATE
EMSE GR. 1
DATE
EMSE GR. 2
DATE
EMSE GR. 3
PAPER/TOPIC  
01.04.

Introduction, Organization, Overall Goals

08.04.

Presentation and Scientific Skills (presented by Lecturers)

15.04.

Simulation, Trial Session (conducted by Lecturers)

29.04.

Paper 1: Swapneel Sheth, Gail E. Kaiser, Walid Maalej: Us and them: a study of privacy requirements across North America, Asia, and Europe.
ICSE 2014: 859-870

06.05.

Paper 2: Hyunmin Seo, Caitlin Sadowski, Sebastian G. Elbaum, Edward Aftandilian, Robert W. Bowdidge:
Programmers’ build errors: a case study (at google).
ICSE 2014: 724-734.

13.05.

Paper 3: Andrew J. Ko, Robert DeLine, and Gina Venolia: Information Needs in Collocated Software Development Teams.
ICSE ’07: 344-353.

20.05.

Paper 4: Meiyappan Nagappan, Thomas Zimmermann, and Christian Bird. 2013. Diversity in software engineering research. ESEC/FSE 2013: 466-476.

27.05

Paper 5: Patrice Caire, Nicolas Genon, Patrick Heymans, Daniel Laurence Moody:
Visual notation design 2.0: Towards user comprehensible requirements engineering notations.
RE 2013: 115-124.

03.06.

Paper 6: Elmar Juergens, Florian Deissenboeck, Benjamin Hummel, and Stefan Wagner: Do code clones matter? ICSE ’09: 485-495

17.06.

Paper 7: Emitza Guzman, Walid Maalej: How Do Users Like this Feature? A Fine-Grained Sentiment Analysis of App Reviews. RE 2014: 153-162

24.06.

Paper 8: Barthélémy Dagenais and Martin P. Robillard: Creating and evolving developer documentation: understanding the decisions of open source contributors. In FSE ’10: 127-136.

01.07.

Paper 9: Laura Inozemtseva and Reid Holmes. Coverage is not strongly correlated with test suite effectiveness. In ICSE 2014: 435-445.

08.07.

Paper 10: Kim, Miryung, Thomas Zimmermann, and Nachiappan Nagappan: “A field study of refactoring challenges and benefits.
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering. ACM, 2012.