Mapping the Research Landscape of Capstone and Final-Year Project Assessment in Computing Education: A Bibliometric Analysis (2020–2026)
This bibliometric analysis of 156 documents from 2020 to 2026 reveals that while capstone and final-year project assessment in computing education is the most impactful research theme, it remains an emerging, fragmented field dominated by subjective methods and lacking a consolidated research front.
Original paper licensed under CC BY 4.0 (https://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 the world of university education as a massive, bustling construction site. For years, students have been building intricate, complex structures called "capstone projects"—the final, crowning achievements of their degrees in fields like computer science and technology. These aren't just simple homework assignments; they are the moment students prove they can take everything they've learned and build something real, often working in teams to create software or systems that solve actual problems. But here's the tricky part: how do you measure if these buildings are truly good? For a long time, the "inspectors" (teachers and judges) have mostly relied on their gut feelings, watching a final presentation, and asking a few people if they liked the result. It's a bit like judging a skyscraper just by how shiny the windows look from the street, without checking if the steel beams inside are strong enough to hold the weight.
To figure out if we can do better, researchers use a special tool called "bibliometric analysis." Think of this as a giant, magical mapmaker. Instead of drawing roads and rivers, this mapmaker draws connections between thousands of written research papers. It counts how many papers exist, who wrote them, who reads them, and what words they use most often. By looking at these patterns, the mapmaker can reveal hidden neighborhoods of ideas, showing us where the research community is strong and where it is empty. This study is all about mapping the neighborhood of "capstone project assessment" to see if we have enough good tools to judge these student projects fairly and accurately.
The Mapmaker's Journey: What the Paper Found
In this study, a researcher named Ailen Laguda decided to draw a map of the research landscape regarding how we grade these final-year computing projects. She looked at 156 specific research papers published between 2020 and 2026. She didn't just read them; she used a powerful computer program called VOSviewer to turn the text into a visual network, like a constellation of stars where the brightness of a star represents how often a paper is cited by others.
The "Ghost Town" of Collaboration
When Laguda looked at the map, she found something surprising: the research community is surprisingly lonely. Out of 156 papers, the average paper was cited only 3.38 times, and a huge chunk—39.1% of them—had zero citations at all. It's as if the researchers are all building their own separate houses in a vast field, rarely visiting each other. The network of authors is "sparse and fragmented," meaning there isn't one big, tight-knit group of experts working together. Instead, most authors are isolated, with only one small group of ten people working together on a single paper. This suggests that the field is still very young and hasn't yet formed a solid, unified team.
The "Hidden Gem" of Assessment
However, the map revealed a fascinating secret. While the researchers talk a lot about general topics like "computer science" or "software engineering," the specific topic of how to grade these projects is a hidden gem. The words related to assessment (like "rubric," "grading," and "evaluation") appear very infrequently in the literature. You might think that because they are rare, they aren't important. But the map showed the opposite!
These rare assessment terms carried the highest "citation impact" of any words on the map. For instance, the word "rubric" (a scoring guide) appeared only nine times, but those few papers were cited an average of 11.1 times each—far more than the common terms. It's like finding a tiny, quiet village in the middle of a noisy city that everyone secretly visits because it holds the most valuable treasure. The study suggests that while the research community doesn't write much about assessment, the little bit they do write is incredibly influential and highly valued.
The "Computer Science" Bias
The map also showed a clear bias in the terrain. The research is heavily focused on "Computer Science" (which appeared 137 times as a keyword). In contrast, related fields like "Information Technology" and "Information Systems" are barely visible on the map. It's as if the mapmakers spent all their time exploring the mountain of Computer Science and completely forgot to draw the hills of Information Technology. This is a problem because the projects in those other fields are often different—they might be more about applying technology in real businesses rather than building pure software. The tools used to grade Computer Science projects might not fit well with these other types of projects.
The Verdict: A Field Waiting to Grow
So, what does this all mean? The study concludes that the field of capstone project assessment is "emerging" but not yet "consolidated." It is a place full of potential but lacking a solid foundation. The research is "lightly cited" and "fragmented," meaning we don't have a shared set of rules or a big group of experts working together yet.
The most important takeaway is that assessment is the most impactful yet least developed theme. The community clearly cares deeply about finding better ways to grade these projects (as shown by the high citations), but they haven't produced enough research to solve the problem yet. It's a clear gap in the map. The study suggests that if we want to move away from "gut feeling" grading and toward fair, evidence-based scoring, we need to fill this gap. We need more research, more collaboration, and more tools specifically designed for the unique nature of these final-year projects, especially for fields beyond just Computer Science. The map is drawn, the treasure is located, but the road to get there is still being built.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.