Software architecting without requirements knowledge and experience: What are the repercussions?
Journal of Systems and Software
Cross-organizational ERP management: how to create a successful business case?
Proceedings of the 2009 ACM symposium on Applied Computing
Design science as nested problem solving
Proceedings of the 4th International Conference on Design Science Research in Information Systems and Technology
An exploratory study of architectural effects on requirements decisions
Journal of Systems and Software
A method for evaluating rigor and industrial relevance of technology evaluations
Empirical Software Engineering
An iterative requirements engineering framework based on Formal Concept Analysis and C-K theory
Expert Systems with Applications: An International Journal
Hi-index | 0.00 |
This paper was triggered by concerns about the methodological soundness of many RE papers. We present a conceptual framework that distinguishes design papers from research papers, and show that in this framework, what is called a research paper in RE is often a design paper. We then present and motivate two lists of evaluation criteria, one for research papers and one for design papers. We apply both of these lists to two samples drawn from the set of all submissions to the RE’03 conference. Analysis of these two samples shows that most submissions of the RE’03 conference are design papers, not research papers, and that most design papers present a solution to a problem but neither validate this solution nor investigate the problems that can be solved by this solution. We conclude with a discussion of the soundness of our results and of the possible impact on RE research and practice.