← Latest papers
💻 computer science

LLM-Driven Cost-Effective Requirements Change Impact Analysis

The paper proposes ProReFiCIA, an LLM-driven approach that effectively and cost-efficiently automates requirements change impact analysis, achieving up to 95.8% recall with minimal engineer review effort when enhanced by domain knowledge via RAG.

Original authors: Romina Etezadi, Sallam Abualhaija, Chetan Arora, Lionel Briand

Published 2026-07-22
📖 5 min read🧠 Deep dive

Original authors: Romina Etezadi, Sallam Abualhaija, Chetan Arora, Lionel Briand

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 the conductor of a massive, chaotic orchestra where every musician is playing a different instrument, but they are all reading from a single, ever-changing sheet of music. In the world of software, this sheet of music is called a "requirements document." It lists everything the computer program must do, from "play a sound when a button is pressed" to "keep the satellite safe from space radiation." But here's the tricky part: software is never finished. Clients change their minds, technology evolves, and new rules appear. When someone says, "Hey, let's change this one rule," it's like asking the conductor to swap a violin for a drum. The problem? That one swap might accidentally break the rhythm for the entire brass section, the percussion, and the choir, even if they never touched the violin.

This is the nightmare of "Change Impact Analysis." It's the detective work of figuring out exactly which other parts of the software will break or need fixing when one tiny piece changes. Traditionally, humans have to do this detective work manually. They read the new request, scan hundreds of pages of old rules, and try to guess the connections. It's slow, it's boring, and it's easy to miss a clue. If you miss a connection, the software might crash later, costing millions or even endangering lives. Recently, a new kind of "super-brain" called a Large Language Model (LLM) has entered the scene. Think of an LLM as a robot that has read almost every book on the internet; it's great at understanding language and spotting hidden connections between ideas that a human might miss. But can this robot actually do the detective work better than a tired human, without getting confused by the sheer volume of text?

This paper introduces a new method called ProReFiCIA (which stands for Prompt-Refinement-Filtering for Change Impact Analysis) to answer that question. The researchers, a team from universities in Canada, Luxembourg, Australia, and Ireland, wanted to see if they could use these AI super-brains to automatically find the "broken dominoes" in a software system when a change happens. They didn't just ask the AI to guess; they built a clever three-step process to make sure the AI was both thorough and careful.

First, they treated the AI like a student taking a test. They tried 64 different ways of asking the question (called "prompts") to see which style of instruction helped the AI understand the task best. They tested five different AI models, including heavy hitters like GPT-4o and LLaMa, on real-world data from a satellite company and a mobile app service. They found that not all AI models are created equal; some were consistent and reliable, while others were a bit erratic. They discovered that the best results came from a specific combination of a powerful AI model (GPT-4o) and a very specific way of asking the question.

But the AI wasn't perfect on the first try. Sometimes it missed a few important connections, and sometimes it got a little too excited and flagged things that weren't actually broken. To fix this, the researchers added two "post-processing" steps, which are like a second pair of eyes checking the AI's work.

  1. Refinement: They asked the AI to look at the requirements it didn't pick the first time, giving it a second chance to spot anything it might have missed. This is like telling a detective, "You missed the window; go check it again."
  2. Filtering: They then used a smart sorting system to rank the AI's suggestions by how confident it was. If the AI was only 50% sure about a connection, they used a special logic checker to see if it made sense. If it didn't, they tossed it out. This step was crucial for keeping the list of "suspects" short and manageable for the human engineers.

The results were impressive. When they tested this system on a new, unseen set of satellite requirements (a very complex and realistic test), the system successfully identified 85.7% of the truly impacted requirements. Even better, it only asked the human engineers to review 3.0% of the total list of requirements. This means the human only had to look at a tiny fraction of the work to catch almost all the problems. The researchers also tried feeding the AI a "cheat sheet" of domain knowledge (like Wikipedia articles about satellites) to see if it would help. This boosted the success rate even higher to 95.8%, with the human review cost only rising slightly to 3.4%.

The paper explicitly argues against the idea that you need to train the AI on massive amounts of specific data to make it work. Instead, they showed that with the right "prompt engineering" (asking the right questions) and a little bit of smart filtering, a pre-trained AI can do the job effectively without needing a huge training budget. They also found that simply asking the AI to check requirements one by one (iteratively) was a bad idea; it created too many false alarms. It was much better to let the AI see the whole picture at once, thanks to its large memory window.

In short, the paper suggests that we don't need to replace human engineers with robots. Instead, we can use these AI tools as a highly efficient "first pass" filter. The AI does the heavy lifting of scanning thousands of pages to find the likely trouble spots, and the human engineer just has to double-check a tiny, curated list of the most probable issues. This approach saves time, reduces the risk of missing critical errors, and keeps the cost of software maintenance low, proving that with the right strategy, AI can be a cost-effective partner in keeping our complex digital world running smoothly.

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 →