← Latest papers
💻 computer science

SAKE: Software Architectural Knowledge Evaluation Benchmark for Large Language Models

This paper introduces SAKE, a standardized benchmark comprising 2,154 expert-curated questions designed to evaluate and reveal competency gaps in the software architectural reasoning capabilities of large language models across diverse categories and context lengths.

Original authors: Tiziano Santilli, Francesco Daghero, Mayhar Tourchi Moghaddam

Published 2026-06-30
📖 4 min read☕ Coffee break read

Original authors: Tiziano Santilli, Francesco Daghero, Mayhar Tourchi Moghaddam

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 hiring a new assistant to help you design a massive, complex city. You need someone who doesn't just know how to lay bricks (coding) but understands traffic flow, emergency services, zoning laws, and how to balance the budget with the need for parks (software architecture).

For a long time, we've been testing these AI assistants with simple quizzes: "Can you write a poem?" or "Can you solve a math problem?" But as the paper SAKE points out, these tests don't tell us if the AI can actually help you design a city. They might be great at reciting facts but terrible at making the tough trade-off decisions architects have to make every day.

Here is what the researchers did, explained simply:

1. The Problem: The "General Knowledge" Trap

Think of current AI benchmarks like a driver's license test where you only have to parallel park and stop at a red light. It proves you can drive a car, but it doesn't tell you if you can navigate a blizzard in the mountains or handle a flat tire on a steep hill.

The authors realized that while AI is getting good at writing code, we don't know if it understands Software Architecture. This is the "big picture" thinking: deciding if a system should be built like a skyscraper (centralized) or a village of tiny houses (microservices), and knowing the consequences of that choice.

2. The Solution: SAKE (The "Architect's Exam")

The team created SAKE (Software Architectural Knowledge Evaluation). Think of this as a specialized, high-stakes exam specifically for software architects.

  • The Questions: They wrote 2,154 multiple-choice questions. These aren't random; they were written by experts and double-checked by other experts to ensure they are fair and accurate.
  • The Topics: The exam covers eight different "neighborhoods" of knowledge:
    • The Basics: How to build things (Design Patterns like "Factory" or "Adapter").
    • The Rules: Quality rules like speed, security, and reliability.
    • The Big Picture: How to organize the whole system (Architectural Styles).
    • The Future: Even questions about the cutting edge, like Quantum Computing.
  • The Twist: Some questions are short and simple (like a flashcard), while others are long, complex stories with lots of details (like a real-world scenario).

3. The Test Drive: Putting 11 AI Models to the Test

The researchers took 11 of the smartest AI models available (both the famous paid ones and the open-source ones) and gave them this exam. They tested them in two ways:

  • Zero-Shot: "Here is the question, just answer it." (Like taking a test cold).
  • Five-Shot: "Here are five examples of how to answer similar questions, now try this one." (Like getting a study guide right before the test).

4. The Results: The "Smart but Flawed" Assistant

The results were surprising and nuanced:

  • The Good News: Overall, the AI models scored very high (around 90% to 94%). They are definitely smart and know a lot of facts.
  • The Bad News: They are uneven.
    • The "Trivia Buffs": The AI was amazing at simple facts (like "What is a Quality Attribute?"). It got almost everything right.
    • The "Strugglers": When the questions required deep reasoning or making tough trade-offs (like "Which solution is best for a system that needs to be both fast and secure?"), the scores dropped significantly.
    • The "Context" Paradox: This is the most interesting part.
      • For simple facts, giving the AI more background information (longer prompts) helped it get the answer right.
      • But for complex reasoning, giving it more information actually made it worse. It's like giving a chef a recipe with too many extra ingredients; instead of helping, it confused the chef and made the dish worse.

5. What This Means for You

The paper concludes with a simple warning: Don't trust the average score.

If you ask an AI to help you design a system, it might be a genius at remembering rules but a disaster at making the hard choices.

  • If you need a fact, the AI is great.
  • If you need a complex architectural decision, you can't just rely on the AI's "confidence." You need to check its work, especially if the question was long and complicated.

The authors released all their questions and results for free. They want this to be a "living benchmark"—a standard yardstick that the whole community can use to see if future AI models are actually getting better at the hard stuff, or just better at memorizing facts.

In short: SAKE is a reality check. It tells us that while AI is becoming a very knowledgeable librarian, it is not yet a fully trusted architect. It knows the books, but it still struggles to design the building.

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 →