CSEG3060 · Research Methodology in Computer Science
Systematic, narrative, scoping and meta-analytical methods
Given my research question, which review method can legitimately answer it?
Unit III · Lecture 2 of 8 · 60 minutes · CO2
Dr. Mohsin Furkh Dar · School of Computer Science, UPES
→ / Space next · ← back · O overview · N speaker notes · F full screen
Learning objectives · CO2
Define and distinguish the four approaches: systematic, narrative, scoping, meta-analytical
Identify the methodological steps each approach requires
Evaluate which approach suits a given CS research question
Apply reporting standards — PRISMA, PRISMA-S, PRISMA-ScR
Critically appraise published reviews for methodological rigour
Foundations
CS research output roughly doubles every five years. Expert intuition alone can no longer guarantee coverage — which is why protocolised methods migrated into the discipline.
Foundations
A pre-specified plan stating the research question, inclusion/exclusion criteria, search strategy, data-extraction method and synthesis approach. The primary defence against post-hoc bias.
PICO — Population, Intervention, Comparison, Outcome · systematic reviews and meta-analyses
PEO — Population, Exposure, Outcome · qualitative phenomena
PCC — Population, Concept, Context · scoping reviews
Systematic reviews and meta-analyses
Search reporting
Scoping reviews
Approach 1 of 4
Published or institutionally archived before screening begins, fixing criteria in advance.
IEEE Xplore, ACM DL, Scopus, Web of Science, ScienceDirect, plus backward and forward citation chasing.
Two-phase screening; quality appraisal of every included study using validated instruments (JBI, CASP).
Standardised extraction forms; transparent reporting via a PRISMA flow diagram.
In computing the canonical procedural reference is Kitchenham & Charters (2007), Guidelines for performing Systematic Literature Reviews in Software Engineering — itself the product of a systematic review across seven digital libraries.
Approach 1 of 4
Worked counts: 3,142 identified → 2,801 excluded on title/abstract → 294 excluded at full text → 47 included. Every exclusion at eligibility must carry a stated reason.
Approach 2 of 4
Short, opinion-driven
Evaluative, argumentative stance
Current developments and future directions
Where it appears in CS: survey articles in ACM Computing Surveys; tutorials in IEEE Transactions introducing an emerging sub-field; the framing chapter of a thesis.
Flexible · theoretically deep · viable for emerging topics · 2–8 weeks
Susceptible to selection bias · hard to replicate · often methodologically opaque
Approach 3 of 4
Optional stage 6 — stakeholder consultation. Practitioners routinely identify grey literature and deployment concerns absent from indexed venues.
PCC — Population/Participants · Concept · Context. Reported under PRISMA-ScR.
Approach 4 of 4 · part 1
Continuous outcomes — standardised mean difference
Binary outcomes — odds ratio from a 2×2 table
Feasibility condition. Studies must report commensurable outcomes with dispersion statistics. Incompatible metrics make pooling illegitimate, not merely difficult.
Applications in CS: empirical software engineering (pair programming and defect density) · educational data mining (intelligent tutoring) · HCI (interface design and task-completion time).
Approach 4 of 4 · part 2
Assumes a single true effect; all divergence is sampling error.
Assumes true effects vary; adds between-study variance τ² to every weight.
Fixed effect asks what is the effect? Random effects asks what is the average of a distribution of effects?
CS studies differ in datasets, hardware, hyperparameters and participants — so random effects is the appropriate default. Fixed effect under real heterogeneity gives intervals that are too narrow.
Approach 4 of 4 · part 3
I² < 25% · low heterogeneity
25% ≤ I² < 75% · moderate
I² ≥ 75% · high — demands subgroup analysis or meta-regression, not a louder pooled claim
The preferential publication of statistically significant results. Diagnosed by funnel-plot asymmetry; tested formally by Egger's regression.
A symmetric funnel: precise studies cluster near the pooled estimate, imprecise ones fan out below. A missing lower-left corner indicates small negative studies that were run but never published.
CS-specific pressure: benchmark culture rewards improvements over null results, so negative findings on a popular architecture are systematically under-published.
Choosing an approach
| Dimension | Systematic | Narrative | Scoping | Meta-analysis |
|---|---|---|---|---|
| Research question | Specific, focused | Broad, contextual | Broad, exploratory | Specific, quantitative |
| Protocol | Pre-specified | Optional | Optional | Pre-specified |
| Search strategy | Exhaustive | Selective | Comprehensive, iterative | Exhaustive |
| Quality appraisal | Mandatory | Informal | Not required | Mandatory |
| Synthesis | Qualitative or quantitative | Qualitative (thematic) | Descriptive mapping | Quantitative pooling |
| Reproducibility | High | Low | Moderate | High |
| Output | Evidence-based conclusions | Conceptual synthesis | Conceptual map | Pooled effect size |
| Typical duration | 6–24 months | 2–8 weeks | 3–6 months | 3–12 months |
Fastest diagnostic pair: Is the question broad or precise? Are the outcome metrics commensurable? These two answers isolate the correct method almost every time.
Practical application
| Step | What you do | Bias risk |
|---|---|---|
| 1–2 Question and protocol | PICO/PEO; fix strings, databases, criteria, appraisal tools | A question so narrow it guarantees a pre-decided answer |
| 3–4 Search and screen | IEEE Xplore, ACM DL, Scopus, ScienceDirect, Scholar; two-phase screen | Single-database reliance; over-restrictive terms; unjustified date limits |
| 5–6 Extract and appraise | Standardised forms; JBI or CASP checklists, two reviewers | Extraction drift; weak studies treated as equal evidence |
| 7–8 Synthesise and report | Thematic synthesis, pooling where legitimate, PRISMA 2020 | Selective citation; silent method reclassification |
Boolean search string
Case study
| Approach | What you actually do | What you legitimately obtain |
|---|---|---|
| Narrative | Synthesise seminal deep-learning IDS work by expert judgement | Conceptual framing; dominant architectures identified |
| Systematic | Exhaustive PRISMA-governed search across CS databases | Reproducible evidence across 47 primary studies |
| Scoping | Map all ML applications across cybersecurity subdomains | Gaps surfaced — adversarial robustness in real deployments |
| Meta-analysis | Pool F1-scores and detection rates across comparable studies | Quantitative estimate of average improvement |
A mature programme uses them in sequence: scoping to locate a defensible gap → systematic to answer it rigorously → meta-analysis where metrics permit pooling.
Pooling F1 across NSL-KDD, CICIDS2017 and a proprietary trace invites exactly the heterogeneity that inflates I². Report it, stratify by dataset, and resist a single triumphant number.
Consolidation
Numerical practice. Three studies: d = 0.45 (SE 0.10), d = 0.62 (SE 0.15), d = 0.38 (SE 0.08). Compute fixed-effect weights wi = 1/SEi², the pooled effect, Q and I², then interpret the heterogeneity.
Method follows from the research question, the available evidence and the intended inference — never from convenience or prestige.