Data Science and Empirical Software Engineering

Empirical Software Engineering (ESE) roots back to the 1970s and has since then gained growing recognition as the standard approach to scientific inquiry in the context of software engineering. Many different quantitative and qualitative research methods

  • PDF / 13,268,375 Bytes
  • 520 Pages / 439.42 x 683.15 pts Page_size
  • 27 Downloads / 237 Views

DOWNLOAD

REPORT


Contemporary Empirical Methods in Software Engineering

Contemporary Empirical Methods in Software Engineering

Michael Felderer • Guilherme Horta Travassos Editors

Contemporary Empirical Methods in Software Engineering

Editors Michael Felderer Department of Computer Science University of Innsbruck Innsbruck, Austria

Guilherme Horta Travassos Department of Systems Engineering and Computer Science, COPPE Federal University of Rio de Janeiro Rio de Janeiro, Brazil

ISBN 978-3-030-32488-9 ISBN 978-3-030-32489-6 (eBook) https://doi.org/10.1007/978-3-030-32489-6 © Springer Nature Switzerland AG 2020 Chapter 17 is licensed under the terms of the Creative Commons Attribution 4.0 International License (http://creativecommons.org/licenses/by/4.0/). For further details see licence information in the chapter. This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. The use of general descriptive names, registered names, trademarks, service marks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. The publisher, the authors, and the editors are safe to assume that the advice and information in this book are believed to be true and accurate at the date of publication. Neither the publisher nor the authors or the editors give a warranty, expressed or implied, with respect to the material contained herein or for any errors or omissions that may have been made. The publisher remains neutral with regard to jurisdictional claims in published maps and institutional affiliations. This Springer imprint is published by the registered company Springer Nature Switzerland AG. The registered company address is: Gewerbestrasse 11, 6330 Cham, Switzerland

Foreword

As the name of the field suggests, software engineering is expected to be an engineering discipline. However, it is not governed, to the same extent, by underlying mathematical models as many other engineering disciplines, in particular, those addressing physical artifacts as in electrical engineering or mechanical engineering. Thus, mathematics is insufficient to conduct research and improve in software engineering, although it is vital for some sub-areas within software engineering. There are several reasons for this insufficiency. First of all, the software is invisible (Brooks 1987). We can read the code, but we cannot see it in use. We can only observe the effect of the software being executed. Furthermore, software engineering is intrinsically complex since it is, to a considerable extent, dependent on the knowledge and capab