Advanced Software Engineering in the Age of Artificial Intelligence: Best Practices, Challenges, and Opportunities

A Special Issue of Computers (ISSN 2073-431X) belonging to the section "AI-Driven Innovations".

Deadline for manuscript submissions: 30 April 2027 | Viewed by 1899

Editor


E-Mail Website
Guest Editor
Gina Cody School of Engineering and Computer Science, Concordia University, Montreal, QC H3G 1M8, Canada
Interests: software engineering; distributed computing; cloud-native services and architecture; applied machine learning
Special Issues, Collections and Topics in MDPI journals

Special Issue Information

Dear Colleagues,

Software engineering is undergoing a period of transformation as Artificial Intelligence (AI) increasingly influences the software lifecycle, from requirements engineering to maintenance. This Special Issue explores the intersection of two distinct but mutually reinforcing domains: AI for Software Engineering (AI4SE), which investigates how AI models can automate and optimize engineering tasks, and Software Engineering for AI (SE4AI), which addresses the rigorous architectural and quality requirements of developing intelligent systems.

As software systems grow in complexity, the industry must address the implications of AI-driven development on technical debt, cost management, and long-term maintainability. This issue seeks to bridge the gap between emerging generative capabilities and established engineering principles such as modularity, observability, architectural principles, and robust testing frameworks. We invite researchers and practitioners to submit work that provides empirical evidence, methodological advancements, and critical analysis of how AI integration impacts the software engineering discipline. Topics are in three related categories, including

I. AI for Software Engineering (AI4SE)

This category focuses on the utilization of machine learning and autonomous systems to enhance traditional engineering processes.

  • Intelligent Requirement Engineering: Methods for automated requirement extraction, conflict detection, and specification refinement.
  • Automated Software Quality Assurance: Enhancing testing protocols, static analysis, and defect prediction for large-scale, distributed systems.
  • Repository Mining and Analysis: Utilizing AI to extract insights from software repositories to improve maintenance, evolution, and technical debt management.
  • AI-Assisted Development Processes: Methodologies for integrating generative models into the CI/CD pipeline while maintaining secure and reproducible build environments.

II. Software Engineering for AI (SE4AI)

This category focuses on the application of rigorous software engineering principles to the development of robust and trustworthy AI models.

  • Architectures for Intelligent Systems: Design patterns and architectural standards for deploying AI models within distributed and cloud-native environments.
  • Trustworthiness and Explainability (XAI): Methodologies for auditing AI systems to ensure transparency, accountability, and reliability in critical domains.
  • Life-Cycle Management for Machine Learning: Applying DevOps and MLOps principles to manage the deployment, monitoring, and versioning of machine learning components.
  • Validation of Autonomous Behavior: Engineering frameworks to assess the robustness, performance, and safety of autonomous agents or learning-based systems.

III. Ethics, Sustainability, and Governance

This category examines the broader societal and operational impacts of integrating AI into software development.

  • Ethical Software Engineering: Assessing the social impact of AI-driven systems and implementing frameworks for bias mitigation and algorithmic fairness.
  • Sustainability and Resource Efficiency: Metrics and measurement models to evaluate the environmental and computational costs of AI-intensive software development.
  • Governance and Compliance: Strategies for aligning AI-integrated software engineering practices with emerging regulatory standards for data privacy and security.

Prof. Dr. Yan Liu
Guest Editor

Manuscript Submission Information

Manuscripts should be submitted online at www.mdpi.com by registering and logging in to this website. Once you are registered, click here to go to the submission form. Manuscripts can be submitted until the deadline. All submissions that pass pre-check are peer-reviewed. Accepted papers will be published continuously in the journal (as soon as accepted) and will be listed together on the special issue website. Research articles, review articles as well as short communications are invited. For planned papers, a title and short abstract (about 250 words) can be sent to the Editorial Office for assessment.

Submitted manuscripts should not have been published previously, nor be under consideration for publication elsewhere (except conference proceedings papers). All manuscripts are thoroughly refereed through a single-anonymized peer-review process. A guide for authors and other relevant information for submission of manuscripts is available on the Instructions for Authors page. Computers is an international peer-reviewed open access monthly journal published by MDPI.

Please visit the Instructions for Authors page before submitting a manuscript. The Article Processing Charge (APC) for publication in this open access journal is 1800 CHF (Swiss Francs). Submitted papers should be well formatted and use good English. Authors may use MDPI's English editing service prior to publication or during author revisions.

Keywords

  • software engineering
  • AI4SE
  • SE4AI
  • explainable AI (XAI)
  • distributed computing
  • cloud-native architecture
  • software quality
  • trustworthy systems
  • ethics in software development
  • lifecycle management

Benefits of Publishing in a Special Issue

  • Ease of navigation: Grouping papers by topic helps scholars navigate broad scope journals more efficiently.
  • Greater discoverability: Special Issues support the reach and impact of scientific research. Articles in Special Issues are more discoverable and cited more frequently.
  • Expansion of research network: Special Issues facilitate connections among authors, fostering scientific collaborations.
  • External promotion: Articles in Special Issues are often promoted through the journal's social media, increasing their visibility.
  • Reprint: MDPI Books provides the opportunity to republish successful Special Issues in book format, both online and in print.

Further information on MDPI's Special Issue policies can be found here.

Related Special Issue

Published Papers (3 papers)

Order results
Result details
Select all
Export citation of selected articles as:

Research

21 pages, 1055 KB  
Article
Beyond Traditional Metrics: Toward a Multifactorial Model for Measuring Productivity in Agile Software Teams
by Marcela Guerrero-Calvache, Giovanni Hernández and María Clara Gómez-Álvarez
Computers 2026, 15(8), 515; https://doi.org/10.3390/computers15080515 - 8 Aug 2026
Viewed by 419
Abstract
Measuring productivity in software development teams is a key process for evaluating their performance in agile environments, which are characterized by value creation, continuous adaptation, and incremental improvement. However, in the field of software engineering, although there are approaches focused on individual metrics, [...] Read more.
Measuring productivity in software development teams is a key process for evaluating their performance in agile environments, which are characterized by value creation, continuous adaptation, and incremental improvement. However, in the field of software engineering, although there are approaches focused on individual metrics, there remains a gap in the development of multifactorial models that integrate the various dimensions influencing team productivity. In response to this issue, this study proposes a multifactorial conceptual model designed to support the process of measuring productivity in agile teams. The development of the model was based on the measurement protocol proposed by Fenton and Bieman and included two main stages: design and validation. During the design phase, productivity factors were identified, and entities, properties, and empirical relationships were defined; these were represented using a Unified Modeling Language (UML) class diagram. The model was validated through expert judgment and an exploratory empirical application in higher education settings. The results demonstrate a high level of acceptance by experts, as well as the model’s viability for application in real-world scenarios, enabling the operationalization of the productivity construct in Scrum teams. In conclusion, the proposed model constitutes a significant advance in measuring productivity in agile teams by integrating multiple dimensions of performance, offering a structured, validated, and applicable framework that overcomes the limitations of traditional approaches and contributes to both the academic realm and professional practice. Full article
Show Figures

Figure 1

26 pages, 762 KB  
Article
Adaptive Fusion of Bug Report Titles and Descriptions for Automated Bug Severity Classification in Software Maintenance
by Thananchai Khamket, Jatuphum Juanchaiyaphum, Theeraya Uttha, Manasawee Kaenampornpan and Jantima Polpinij
Computers 2026, 15(7), 442; https://doi.org/10.3390/computers15070442 - 11 Jul 2026
Viewed by 434
Abstract
Bug severity classification supports software maintenance by helping developers prioritize defect resolution. Most existing approaches combine bug report titles and descriptions into a single representation, often assuming that both textual components contribute equally to severity prediction. However, concise titles and detailed descriptions may [...] Read more.
Bug severity classification supports software maintenance by helping developers prioritize defect resolution. Most existing approaches combine bug report titles and descriptions into a single representation, often assuming that both textual components contribute equally to severity prediction. However, concise titles and detailed descriptions may provide different types of severity-related information. This study investigates their relative contribution and proposes an Adaptive Title–Description Fusion (ATDF) framework that separately encodes title and description representations and adaptively estimates their contribution during feature fusion. Experiments were conducted on Mozilla Bugzilla repositories using a multiclass classification setting with five severity categories. The proposed framework was compared with title-only, description-only, direct concatenation, and standard gated fusion baselines. ATDF achieved the highest overall performance, with a Macro-F1 score of 0.771, compared with 0.756 for standard gated fusion and 0.739 for direct concatenation. Additional analyses showed that title and description contributions varied across severity categories and repositories under the current experimental setting. Overall, the findings suggest that considering the relative contribution of title and description information can provide a practical approach to improving bug severity classification while offering additional insight into title–description fusion behavior in software repositories. Full article
Show Figures

Figure 1

61 pages, 2706 KB  
Article
BLOW: A Systematic Approach to Behavior-Driven Development in a Layered Organization of Work-Centers
by Nicolas Afonso-Alonso, Juan A. Holgado-Terriza, Miguel A. Oltra-Rodríguez and Paul Stonehouse
Computers 2026, 15(7), 405; https://doi.org/10.3390/computers15070405 - 25 Jun 2026
Viewed by 539
Abstract
Agile teams often struggle to translate business requirements into maintainable, high-quality software due to the persistent ambiguity in the roles and relationships of behavior-driven development (BDD), Acceptance Test-driven Development (ATDD), and Test-driven Development (TDD). These approaches are frequently misunderstood, inconsistently applied, and only [...] Read more.
Agile teams often struggle to translate business requirements into maintainable, high-quality software due to the persistent ambiguity in the roles and relationships of behavior-driven development (BDD), Acceptance Test-driven Development (ATDD), and Test-driven Development (TDD). These approaches are frequently misunderstood, inconsistently applied, and only loosely connected within a unified delivery lifecycle. This article introduces BLOW (Behavior-Driven Development in a Layered Organization of Work-Centers), a systematic approach that establishes BDD as the coordinating methodology between ATDD (business-focused) and TDD (technology-focused). BLOW structures scenario-driven development across layered domains of accountability with clearly defined roles and responsibilities, organizing delivery through nested work-centers that transform user stories into executable specifications and production code. This approach integrates two complementary collaboration practices: the Three Amigos for discovering and formulating business scenarios, and the proposed Technical Three Amigos for linking those scenarios to Technical Domain Contexts, identifying required Enablers, and deriving technical scenarios when additional architectural support is needed. The proposed operating model emphasizes observability through executable scenarios as first-class artifacts, introducing native, test-anchored metrics that support reasoning about progress, technical effort, and value delivery within scenario-driven development. An exploratory longitudinal case study, consisting of a single-sprint proof of concept followed by an 18-month production deployment, reports patterns in which technical enablement precedes business value delivery and reusable infrastructure supports sustained growth of business scenarios over time. The findings also indicate that changes in the applied operating model are associated with measurable shifts in scenario evolution and internal quality indicators. Overall, BLOW provides a governance-compatible, end-to-end approach for organizing scenario driven development and improving alignment between stakeholder intent and technical implementation in complex software systems. Full article
Show Figures

Figure 1

Back to TopTop