Understanding and improving technology transfer in software engineering
Journal of Systems and Software - Special issue on invited articles on top systems and software engineering scholars
Preliminary guidelines for empirical research in software engineering
IEEE Transactions on Software Engineering
Requirements engineering paper classification and evaluation criteria: a proposal and a discussion
Requirements Engineering
Design Science, Engineering Science and Requirements Engineering
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
Guidelines for conducting and reporting case study research in software engineering
Empirical Software Engineering
Predicting build failures using social network analysis on developer communication
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Tesseract: Interactive visual exploration of socio-technical relationships in software development
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Lightweight fault-localization using multiple coverage types
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Design science as nested problem solving
Proceedings of the 4th International Conference on Design Science Research in Information Systems and Technology
A BPMN-Based Design and Maintenance Framework for ETL Processes
International Journal of Data Warehousing and Mining
| Hi-index | 0.01 |
Design scientists have to balance the demands of methodological rigor that they share with purely curiosity-driven scientists, with the demands of practical utility that they share with utility-driven engineers. Balancing these conflicting demands can be conceptually complex and may lead to methodological mistakes. For example, treating a design question as an empirical research question may lead to researcher to omit the identification of the practical problem to solve, to omit the identification of stakeholder-motivated evaluation criteria, or to omit trade-off and sensitivity analysis. This tutorial aims to clear up this methodological mist in the case of software engineering (SE) research.