← Latest papers
💻 computer science

Towards Improving the External Validity of Software Engineering Experiments with Transportability Methods

This vision paper introduces transportability methods to Software Engineering research as a principled approach for combining experimental and observational data to overcome sampling limitations, thereby enhancing the external validity and practical applicability of controlled experiment results.

Original authors: Julian Frattini, Richard Torkar, Robert Feldt, Carlo Furia

Published 2026-04-10
📖 5 min read🧠 Deep dive

Original authors: Julian Frattini, Richard Torkar, Robert Feldt, Carlo Furia

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a chef trying to figure out if a new, fancy spice (let's call it "GenAI Spice") makes your soup taste better.

The Problem: The "Student Chef" Experiment

You want to know if this spice works for everyone in the world. But, you can't invite every single person on Earth to your kitchen. It's too expensive and takes too long.

So, you decide to run a controlled experiment. You invite a group of people to taste the soup. But here's the catch: You can only afford to invite cooking students.

  • The Experiment: You give the students the soup with the spice and the soup without it.
  • The Result: The students love the spice! They say it makes the soup amazing.
  • The Problem: Professional chefs (the "Target Population") might hate the spice. Maybe they are so experienced that the spice is too strong for them, or maybe they already know how to make the soup taste great without it.

Because you only tested on students (who are less experienced), your results are biased. You think the spice is a miracle, but in the real world, it might be a disaster. In research terms, this is a lack of External Validity—your results don't apply to the real world.

The Solution: "Transportability" (The Time-Traveling Recipe)

This paper suggests a clever way to fix this without having to invite thousands of professional chefs to your kitchen. It uses a method called Transportability.

Think of it like this:

  1. The Small Experiment: You still test the spice on your small group of students (the "Experimental Sample").
  2. The Big Data: You also have access to a massive database of professional chefs (the "Observational Data"). You don't need them to taste the soup; you just need to know who they are. You know their experience levels, their backgrounds, and how many years they've been cooking.
  3. The Magic Bridge: The paper proposes a mathematical "bridge" that connects your student results to the professional chef database.

How the Bridge Works (The Analogy)

Imagine your student group is mostly made of 18-year-olds. The real world of chefs is a mix of 18-year-olds, 30-year-olds, and 60-year-olds.

  • The Mistake: If you just average the students' scores, you are saying, "The whole world of chefs loves this spice."
  • The Transportability Fix: The method looks at the student data and says, "Okay, these 18-year-olds loved it. But we know from our big database that 60-year-old chefs are rare in our student group but common in the real world."

The method then re-weights the results. It says:

  • "The opinion of one 60-year-old chef (who is hard to find) counts more than the opinion of ten 18-year-old students (who are easy to find)."
  • It mathematically "transports" the student results to fit the shape of the real-world population.

It's like taking a photo of a small crowd of people and using a filter to make it look like a photo of the entire city, based on census data you already have.

Why This Matters for Software

In the world of Software Engineering (SE), researchers often test new tools on university students because they are easy to find. But the real world is full of senior software engineers.

  • The Issue: A new coding tool might help a student a lot, but a senior engineer might find it annoying or useless. If we only test on students, we might think the tool is great for everyone.
  • The Fix: Using this paper's method, researchers can test on students, but then use data about real engineers (like how many years they've worked) to "transport" the results. This tells us: "This tool is great for juniors, but maybe not for seniors."

The Three Steps to Make This Work

The paper outlines a roadmap for researchers to start doing this:

  1. Know Your Variables: Figure out what makes people different. Is it experience? Is it the programming language they use? (These are called "covariates").
  2. Get the Big Data: Instead of just running expensive experiments, gather data on the real world. How many senior engineers are there? What is their experience distribution?
  3. Do the Math: Use the "Transportability" formulas to combine the small experiment with the big data. This gives you a result that is accurate for the whole population, not just the people you tested.

The Bottom Line

This paper is a call to action for software researchers. It says: "Stop pretending your student experiments represent the whole world."

Instead, use the data you already have about the real world to "correct" your experiments. It's like using a GPS to navigate from your small local map (the experiment) to the entire world map (the real population), ensuring that your scientific discoveries are actually useful for everyone, not just the people in your lab.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →