Bibliographic record
Abstract
Summary form only given. Empirical research in software engineering collects and studies the quantitative/qualitative data in order to understand and improve the software product, software development process and software management. The empirical research methods are classified into controlled experiment, case study and survey, and the process of empirical study can be divided into experimental/case study setting, data collection, and data analysis. The protocol analysis, as one of the experimental methods, includes introspective, retrospective and think-aloud approaches. In this talk, I brief several empirical research methods in software engineering, and analyze their strengths and weaknesses. A new approach: dialog-based protocol is then introduced. A case study is conducted for evaluation purpose. At the end, the threats and opportunities of empirical research in software engineering are discussed.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.041 | 0.123 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.003 | 0.001 |
| Bibliometrics | 0.008 | 0.013 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.007 | 0.009 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.005 | 0.007 |
| Insufficient payload (model declined to judge) | 0.136 | 0.060 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".