Abstract
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.
Original language | Undefined |
---|---|
Pages | 493-494 |
Number of pages | 2 |
DOIs | |
Publication status | Published - May 2010 |
Event | 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010 - Cape Town, South Africa Duration: 2 May 2010 → 8 May 2010 Conference number: 32 |
Conference
Conference | 32nd ACM/IEEE International Conference on Software Engineering, ICSE 2010 |
---|---|
Abbreviated title | ICSE |
Country/Territory | South Africa |
City | Cape Town |
Period | 2/05/10 → 8/05/10 |
Keywords
- SCS-Services
- IS-Design science methodology
- IR-83379
- EWI-22392