ReqFusion: A Multi-Provider Framework for Automated PEGS Analysis Across Software Domains

Abstract

Requirements engineering is a vital, yet labor-intensive, stage in the software development process. This article introduces ReqFusion: an AI-enhanced system that automates the extraction, classification, and analysis of software requirements utilizing multiple Large Language Model (LLM) providers. The architecture of ReqFusion integrates OpenAI GPT, Anthropic Claude, and Groq models to extract functional and non-functional requirements from various documentation formats (PDF, DOCX, and PPTX) in academic, industrial, and tender proposal contexts. The system uses a domain-independent extraction method and generates requirements following the Project, Environment, Goal, and System (PEGS) approach introduced by Bertrand Meyer. The main idea is that, because the PEGS format is detailed, LLMs have more information and cues about the requirements, producing better results than a simple generic request. An ablation study confirms this hypothesis: PEGS-guided prompting achieves an F1 score of 0.88, compared to 0.71 for generic prompting under the same multi-provider configuration. The evaluation used 18 real-world documents to generate 226 requirements through automated classification, with 54.9% functional and 45.1% nonfunctional across academic, business, and technical domains. An extended evaluation on five projects with 1,050 requirements demonstrated significant improvements in extraction accuracy and a 78% reduction in analysis time compared to manual methods. The multi-provider architecture enhances reliability through model consensus and fallback mechanisms, while the PEGS-based approach ensures comprehensive coverage of all requirement categories.

Figures (6)

• Figure 1: ReqFusion system architecture. The Multi-LLM Orchestrator (center, highlighted) coordinates GPT-4, Claude-3, and Groq providers. The Response Merger applies cosine similarity ($>$0.85 threshold) for deduplication and consensus voting for conflict resolution.
• Figure 2: Requirements distribution in Dataset A (n=226). Functional requirements comprise 54.9% while non-functional requirements account for 45.1%.
• Figure 3: Priority distribution of extracted requirements (Dataset B, n=1,050). High-priority requirements dominate at 64.5%, reflecting the industrial nature of the tender documentation.
• Figure 4: Distribution of requirements by category (Dataset B). Compliance requirements (26.5%) dominate due to the regulatory nature of German industrial tenders.
• Figure 5: Provider performance comparison. The multi-provider consensus approach achieves the highest F1 score (0.88), outperforming all individual providers.