Large Language Models for Analyzing Enterprise Architecture Debt in Unstructured Documentation
Organizations: Stockholm University, Stockholm, Sweden · University of Twente, Enschede, The Netherlands
Abstract
Enterprise Architecture Debt (EA Debt) arises from suboptimal design decisions and misaligned components that can degrade an organization's IT landscape over time. Early indicators, Enterprise Architecture Smells (EA Smells), are currently mainly detected manually or only from structured artifacts, leaving much unstructured documentation under-analyzed. This study proposes an approach using a large language model (LLM) to identify and quantify EA Debt in unstructured architectural documentation. Following a design science research approach, we design and evaluate an LLM-based prototype for automated EA Smell detection. The artifact ingests unstructured documents (e.g., process descriptions, strategy papers), applies fine-tuned detection models, and outputs identified smells. We evaluate the prototype through a case study using synthetic yet realistic business documents, benchmarking against a custom GPT-based model. Results show that LLMs can detect multiple predefined EA Smells in unstructured text, with the benchmark model achieving higher precision and processing speed, and the fine-tuned on-premise model offering data protection advantages. The findings highlight opportunities for integrating LLM-based smell detection into EA governance practice.
Figures & tables
| Requirement | Description |
|---|---|
| Interpreting unstructured data sources | The artifact should be able to process Word (.docx) and PDF (.pdf) files. |
| Detecting EA Smells | The artifact should recognize common architectural inefficiencies. |
| Providing recommendations | The artifact should generate an output that includes the findings and recommendations to guide enterprise architects in addressing the identified issues. |
| Data protection | Enterprise data should be protected. |
| Requirement | Description |
|---|---|
| Technical limitations | The artifact needs to be able to run on a Windows 16 GB RAM environment with CPU only. |
| Accuracy | The artifact should identify EA Smells correctly. |
| Processing time | The artifact should have an adequate processing time when analyzing documents. |
| Scalability | The artifact should be able to handle large datasets without performance degradation. |
| Adaptability | The artifact should revise prior assessments based on newly provided, potentially corrective information. |
| Usability | The artifact should be easy to use. |
| EA Smell | Short Description |
|---|---|
| Ambigious Viewpoint | Viewpoints are mixed or unclear. |
| Big Bang | Architecture changed all at once. |
| Business Process Forever | Processes kept unchanged despite need. |
| Contradiction in Input | Inputs or rules contradict each other. |
| Deficient Names | Names are unclear or misleading. |
| Efficiency Goals not Visible | No measurable performance targets. |
| Metric | Model A – Run 1 | Model A – Run 2 | Model B – Run 1 | Model B – Run 2 |
|---|---|---|---|---|
| Accuracy | 0.15 | 0.08 | 0.40 | 0.42 |
| Recall | 0.22 | 0.13 | 0.22 | 0.25 |
| False Positive Rate (FPR) | 0.95 | 1.00 | 0.09 | 0.09 |
| Precision | 0.26 | 0.19 | 0.88 | 0.89 |
| F1 Score | 0.24 | 0.15 | 0.35 | 0.39 |
| Number of Documents | Llama Prototype (Model A) | Custom GPT (Model B) |
|---|---|---|
| 1 | 120 seconds | 2 seconds |
| 10 per batch | 17 minutes | 2 seconds |
| 30 per batch | 50 minutes | Not possible |
Software Engineering
Software engineering studies how to design, build, test, deploy, and maintain reliable software systems and the processes behind them.
See all 270 papers