Perspectives on negative research results in pervasive computing
|Author:||Peltonen, Ella1; Mohan, Nitinder2; Zdankin, Peter3;|
1University of Oulu, Oulu, Finland
2Technical University Munich, Munchen, Germany
3University of Duisburg-Essen, Duisburg, Germany
4University of Edinburgh, Edinburgh, U.K.
5University of Twente, Enschede, The Netherlands
6University of Cambridge, Cambridge, U.K.
7University of Helsinki, Helsinki, Finland
8University of Bamberg, Bamberg, Germany
|Online Access:||PDF Full Text (PDF, 0.8 MB)|
|Persistent link:|| http://urn.fi/urn:nbn:fi-fe2023062658175
Institute of Electrical and Electronics Engineers,
|Publish Date:|| 2023-06-26
Not all research leads to fruitful results; trying new ways or methods may surpass state of the art, but sometimes the hypothesis is not proven, the improvement is insignificant, or the system fails because of a design error done years ago in previous works. In a systems discipline like pervasive computing, there are many sources of errors, from hardware issues over communication channels to heterogeneous software environments. However, failure to succeed is not a failure to progress. It is essential to create platforms for sharing insights, experiences, and lessons learned when conducting research in pervasive computing so that the same mistakes are not repeated. And sometimes, a problem is a symptom of discovering new research challenges. Based on the collective input of the First International Workshop on Negative Results in Pervasive Computing (PerFail 2022), co-located with the 20th International Conference on Pervasive Computing and Communications (PerCom 2022), this article presents a comprehensive discussion on perspectives on publishing negative results, useful failures, and lessons learned in pervasive computing.
IEEE pervasive computing
|Type of Publication:||
A1 Journal article – refereed
|Field of Science:||
113 Computer and information sciences
© The Author(s) 2023. This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 License. For more information, see https://creativecommons.org/licenses/by-nc-nd/4.0/.