The quality of questionnaire based software maintenance studies
ACM SIGSOFT Software Engineering Notes
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
A case study in root cause defect analysis
Proceedings of the 22nd international conference on Software engineering
Daily build and feature development in large distributed projects
Proceedings of the 22nd international conference on Software engineering
Architecture Design Recovery of a Family of Embedded Software Systems
WICSA1 Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1)
An Experiment on Lead-Time Impact in Testing of Distributed Real-Time Systems
METRICS '01 Proceedings of the 7th International Symposium on Software Metrics
How Effective Developers Investigate Source Code: An Exploratory Study
IEEE Transactions on Software Engineering
Studying Software Engineers: Data Collection Techniques for Software Field Studies
Empirical Software Engineering
When Software Engineers Met Research Scientists: A Case Study
Empirical Software Engineering
Triangulation as a basis for knowledge discovery in software engineering
Empirical Software Engineering
A practitioner's guide to light weight software process assessment and improvement planning
Journal of Systems and Software
Software Process and Product Measurement
Qualitative research on software development: a longitudinal case study methodology
Empirical Software Engineering
Requirements engineering tools: Capabilities, survey and assessment
Information and Software Technology
Hi-index | 0.00 |
As the demand for empirical evidence for claims of improvements in software development and evolution has increased, the use of empirical methods such as case studies has grown. In case study methodology various types of triangulation is a commonly recommended technique for increasing validity. This study investigates a multiple data source case study with the objective of identifying whether more findings, trustworthier findings and other findings are made using multiple data source triangulation, than had a single data source been used. The case study investigated analyses key lead-time success factors for a software evolution project in a large organization developing eBusiness systems with high-availability high throughput transaction characteristics. By tracing each finding in that study to the individual evidences motivating the finding, it is suggested that a multiple data source explorative case study can have a higher validity than a single data source study. It is concluded that a careful case study design with multiple sources of evidence can result in not only better justified findings than a single data source study, but also other findings. Thus this study provides empirically derived evidence that a multiple data source case study is more trustworthy than a comparable single data source case study.