Reliability of Large Language Models for Design Synthesis: An Empirical Study of Variance, Prompt Sensitivity, and Method Scaffolding
This empirical study evaluates the reliability of three large language models in synthesizing object-oriented UML designs from natural language, finding that while preference-based prompting improves adherence to design principles, it cannot fully eliminate non-determinism or overcome significant model-dependent variations in design quality.
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 boss trying to hire an architect to design a new building. You give the architect a simple description: "I need a hospital where patients get billed based on their insurance, and a weather station that sends updates to different devices."
You have three different architects on your team: Architect A (ChatGPT), Architect B (Claude), and Architect C (Gemini). You want to know: Can these architects actually design a solid, logical building, or are they just drawing random shapes that look like buildings?
This paper is a report card on how well these "AI Architects" perform when asked to do real design work, not just copy-paste.
The Big Problem: "Translation" vs. "Synthesis"
The researchers found a major difference between two types of work:
- Translation: The AI reads your words and draws a box for every noun. If you say "Patient," it draws a box labeled "Patient." This is easy.
- Design Synthesis: The AI understands the logic. It knows that "Patients" should be grouped under a "Person" category, or that "Billing" should be flexible enough to handle different insurance types without breaking. This is hard.
The study asked: Can AI move beyond just drawing boxes to actually thinking like an engineer?
The Three Ways They Asked the AI
To test this, the researchers tried three different ways of giving instructions (prompts):
- The "Just Do It" Approach (Standard): They gave the AI the problem description and said, "Draw the diagram."
- Result: The AI often drew shallow, messy diagrams. It missed the big picture.
- The "Rule Book" Approach (Rule-Injection): They gave the AI the problem plus a list of strict rules like "You must use encapsulation" or "You must use the Strategy pattern."
- Result: Surprisingly, this didn't help much. Sometimes, giving the AI too many rules just confused it, and it started making up fake connections (hallucinations).
- The "Show, Don't Just Tell" Approach (Preference-Based): This was the researchers' new idea. Instead of just listing rules, they showed the AI examples of a bad design and a good design, and said, "I prefer the good one."
- Result: This worked the best! It helped the AI understand the spirit of good design without needing to memorize a rulebook.
The Three Architects' Personalities
The study discovered that the type of AI matters just as much as the instructions.
- Architect A (ChatGPT): When given the right "scaffolding" (the preference examples), this architect became very predictable. Once it figured out the plan, it stuck to it. However, it sometimes made the same small mistake over and over.
- Architect B (Claude): This architect was the most consistent. If you asked it to draw the same building ten times, it would draw almost the exact same thing every time. It was stable, but sometimes it was too rigid and missed the "abstract" parts of the design.
- Architect C (Gemini): This architect was the most unpredictable. Ask it to draw the same building twice, and you might get two completely different blueprints. It was great at some things but very shaky on others. If you need reliability, this one is risky.
The "Complexity Trap"
When the researchers made the task harder (moving from a simple billing system to a complex sensor network), all the architects struggled.
- They could handle the basics.
- But when the design required "invisible" logic (like realizing that a sensor needs to notify multiple devices automatically), they mostly failed. They couldn't "guess" the hidden patterns that a human expert would see immediately.
The Main Takeaways
- AI is getting better at drawing, but still learning to think. They can translate words into diagrams, but they struggle to infer the deep logic of software architecture.
- The "How" you ask matters, but the "Who" matters more. Using the "Show, Don't Just Tell" method helped, but picking the right AI model (like Claude for stability or ChatGPT for structure) was even more important.
- Reliability is key. In software, if an AI draws a different building every time you ask, you can't trust it to build your house. The study shows that while AI is powerful, it's not yet a "dependable partner" for critical design work without human supervision.
In short: AI architects are talented interns. They can draw the walls, but they still need a senior human architect to check the blueprints, ensure the logic holds up, and pick the right intern for the job.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.