Options
Now showing
1 - 6 of 6
-
PublicationEvaluation of the SPES XT modeling framework( 2016)
;Diebold, Philipp ;Daun, Marian ;Heuer, AndréIn software engineering, emprirical evaluations play a major role in discovering the advantages and disadvantages of newly developed methods, techniques, and tools. -
PublicationEmpirical practice in software engineering( 2013)
;Guzman, Liliana ;Jung, Jessica ;Lampasona, ConstanzaSteinbach, SilkeExperimental software engineering has been defined as the scientific approach to systematically evaluating software technologies by referring to predefined hypotheses using sound empirical methods. The purpose of this chapter is to give an overview of the history, current practice, and future of empirical practice in Software Engineering. In particular, based on what we have learned from 20 years of research in empirical software engineering, we describe the empirical approach we are currently using in terms of a scientific approach to applied research and as a means for systematic evaluation. -
PublicationOverview of the SPES Evaluation Strategy( 2012)Löwen, UlrichTo assess the impact of a technology on certain objectives, such as the technology inherent benefit or efficiency, systematic evaluations based on scientifically sound criteria have to be planned and conducted.
-
PublicationEvaluation summary( 2012)
;Jung, JessicaLampasona, ConstanzaDecision makers in embedded system development require evidence about technologies to enable them to make an informed decision when new development technologies are to be introduced. -
PublicationInnovative man machine interfaces and solutions to support totally blind people( 2011)
;Choras, Michal ;D'Antonio, Salvatore ;Iannello, Giulio ;Kozik, Rafal ;Miesenberger, KlausWoloszczuk, AdamIn this paper we present innovative MMI solutions to support social inclusion of totally blind people. We propose to use dedicated harness and mobile devices (e.g. smartphones) to support Instrumental Activities of Daily Living (IADL). -
PublicationReporting experiments in software engineering( 2008)
;Ciolkowski, MarcusPfahl, DietmarBackground: One major problem for integrating study results into a common body of knowledge is the heterogeneity of reporting styles: (1) It is difficult to locate relevant information and (2) important information is often missing. Objective: A guideline for reporting results from controlled experiments is expected to support a systematic, standardized presentation of empirical research, thus improving reporting in order to support readers in (1) finding the information they are looking for, (2) understanding how an experiment is conducted, and (3) assessing the validity of its results. Method: The guideline for reporting is based on (1) a survey of the most prominent published proposals for reporting guidelines in software engineering and (2) an iterative development incorporating feedback from members of the research community. Result: This chapter presents the unification of a set of guidelines for reporting experiments in software engineering. Limitation: The guideline has not been evaluated broadly yet. Conclusion: The resulting guideline provides detailed guidance on the expected content of the sections and subsections for reporting a specific type of empirical study, i.e., experiments (controlled experiments and quasi-experiments).