Score
Designs and specifies middleware components and architectures and develops integration interfaces and configuration artifacts to connect application and infrastructure layers. Evaluates and validates candidate middleware for functional correctness, performance, reliability, security, and compatibility, and produces selection justifications and deployment/configuration plans.
This study addresses the lack of systematic comparative analysis among open-source message-oriented middleware systems, which hinders informed selection by developers. Through a comprehensive literature review and feature engineering, the authors conduct a structured evaluation of ten mainstream systems across 42 functional dimensions—encompassing 134 fine-grained attributes—including critical aspects such as transaction support, active messaging, and multi-tenancy. The work presents the first publicly available, extensively annotated dataset of message middleware features, offering fine-grained insights into their capabilities. This resource not only highlights the pivotal role these systems play in supporting cloud-native applications but also establishes a verifiable benchmark and actionable guidance for future optimization and community-driven development.
This study addresses the proliferation of functional redundancy in service-oriented architectures caused by heterogeneous clients, which undermines system evolvability and maintainability. To mitigate this issue, the authors propose a novel reference architecture that synergistically integrates metadata-driven mechanisms with pattern languages. By leveraging metadata management and a plugin-based design, the approach effectively constrains service redundancy while enhancing reuse capabilities. The work innovatively combines metadata mechanisms and pattern languages in architectural construction and validates its efficacy through a triangulated evaluation method incorporating scenario-based assessment and real-world case studies. Empirical results demonstrate that the majority of system changes during evolution require no code modifications—only configuration adjustments or the addition of pluggable components—thereby significantly improving architectural stability and reuse efficiency.
This study addresses the lack of systematic guidance for enterprise software teams in choosing between monolithic and microservices architectures. The work proposes a decision-making framework that integrates technical and organizational factors, evaluating the trade-offs of each architecture across dimensions such as scalability, reliability, deployment efficiency, and organizational complexity. The assessment is grounded in system scale, business requirements, operational maturity, and long-term maintainability. Through architectural pattern analysis, a structured evaluation model, and multiple case studies, the authors develop a practical selection methodology tailored to real-world engineering contexts. This approach offers enterprises clear architectural evolution pathways and actionable guidelines aligned with their developmental stages, thereby significantly enhancing the rationality and sustainability of system design decisions.
To address performance overhead escalation and transaction boundary degradation arising from process decomposition during monolith-to-microservices migration, this paper proposes a lightweight, trace-based what-if analysis method. The approach comprises three stages: execution trace collection and rewriting, performance-sensitive call-chain simulation, and abstract modeling of transaction boundaries—enabling rapid, quantitative assessment of non-functional property changes induced by service decomposition alternatives. Its core innovation lies in introducing the first trace-rewriting analysis paradigm prioritizing usability and speed, requiring neither source-code modification nor deployment in production-like environments. Evaluated on industrial case studies, the method completes each scenario assessment in seconds—achieving two orders-of-magnitude improvement in analysis efficiency—and thereby significantly facilitates high-frequency, low-friction iteration over service boundaries and informed trade-off decisions.
Current RESTful API design quality assessment relies heavily on manual inspection, lacking early, automated validation mechanisms for non-functional requirements—particularly interoperability, modularity, and maintainability. Method: This paper proposes an OpenAPI-based static analysis approach that implements a configurable rule engine. It formalizes 75 design principles derived from scholarly literature and industry standards into structured, machine-checkable constraints, enabling customizable rule activation/deactivation and traceable feedback to align requirements engineering with architectural governance. Contribution/Results: Following the design science research paradigm, we developed and evaluated a prototype tool. Empirical evaluation and expert review demonstrate that the method significantly improves API design compliance and consistency, achieving 82% automation coverage. It effectively supports continuous architectural governance in agile development environments, bridging the gap between design-time assurance and operational API lifecycle management.
本文提出了一种基于仓库的实现方法,通过自动接口更新和一致性检查减少有人和无人飞行器软件开发中跨域不一致问题。
This work addresses the challenge of reliably conveying intent, requirements, and constraints in human–AI–tool collaborative software development by proposing a specification-centric Bosque API (BAPI) ecosystem. The system introduces a highly expressive specification language that, for the first time, enables cross-language interoperability, automated test generation, formal verification, and execution sandboxing across the entire API lifecycle—from requirement definition and implementation to invocation and validation. By providing end-to-end specification guarantees, BAPI significantly enhances system correctness, security, and the efficiency of human–AI collaboration, offering a novel infrastructure for software development in the era of AI agents.
AI-assisted development tools enable rapid prototyping of services but often lack awareness of architectural constraints, infrastructure dependencies, and organizational standards required in production environments. Consequently, generated artifacts may exhibit brittle behavior and limited deployability. We propose a retrieval-augmented scaffolding approach that combines platform-based code generation with agentic clarification loops to expose and resolve architectural constraint ambiguities. By combining template retrieval with structured interaction, the method embeds production-relevant considerations during service scaffolding. Evaluation indicates improved architectural consistency and deployability compared to general-purpose AI code generation workflows, suggesting that constraint-aware retrieval is essential for aligning AI-assisted service development with production software engineering practices.
This study addresses the widespread yet often insecure integration of AI components into software systems, which frequently overlooks critical security risks and can lead to malicious behaviors or data breaches. Through semi-structured interviews with 22 industry practitioners, the work systematically uncovers a pervasive neglect of security considerations during AI component selection and integration, revealing that functional performance overwhelmingly dominates decision-making while security is rarely evaluated. Drawing on established practices from traditional software supply chain security, the paper adapts and extends these principles to the AI context, proposing a set of lifecycle-spanning security-by-design guidelines. It further offers actionable recommendations tailored for developers, model providers, and researchers to foster more secure AI integration practices.
While large language models (LLMs) can generate executable multi-service application environments, they often deviate from the architectural and security requirements essential for production deployment. This work proposes a method to automatically generate Dockerfiles and Docker Compose configurations solely from code repositories, evaluating deployment fidelity through end-to-end HTTP testing and structural comparison. It explicitly distinguishes between functional correctness and fidelity to deployment intent, deriving a minimal set of explicit deployment specifications that cannot be inferred automatically from source code alone. Experiments successfully reproduce the topology and dependencies of three heterogeneous multi-service systems, confirming functional feasibility; however, critical production-grade features—such as network isolation and multi-stage builds—are consistently absent, revealing fundamental limitations in current LLMs’ ability to model deployment intent.
研究通过FDE-Bench评估了LLM代理在配置部署环境中的能力,使用136个任务测试其构建、就绪性、行为及符合规格的能力。