Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Report
Data sources: ZENODO
addClaim

Agile7 Code Platform (ACP) - Software Architecture Whitepaper

Authors: Max Meinhardt;

Agile7 Code Platform (ACP) - Software Architecture Whitepaper

Abstract

Overview The Agile7 Code Platform (ACP) is an AI-driven, IDE-integrated software engineering platform designed to maintain continuous alignment between business requirements, their software architecture models and supporting scripts, and generated code through end-to-end traceability and configurable alignment metrics. ACP combines Model-Driven Engineering (MDE), Business Requirements Validation (BRV), AI-assisted code generation, and requirements-to-models-to-code alignment validation-driven development workflows to help organizations reduce architectural drift, improve software quality, and maintain business-to-code alignment throughout the software development lifecycle. Vision ACP aims to transform software development by treating business requirements, models, and their supporting scripts as authoritative development artifacts while using AI to generate, validate, and regenerate software implementations. The platform is designed to support modern software engineering practices through: AI-driven software generation and regeneration IDE-integrated development workflows End-to-end requirements-to-code traceability Business Requirements Validation (BRV) Continuous architecture validation Incremental code generation LLM-agnostic architecture Key Architectural Concepts AI-Driven Architecture ACP integrates AI into its core architecture through a Prompt-Based Build Engine that transforms requirements, software project models (currently UML), and supporting scripts into software implementations while remaining independent of specific LLM providers. IDE-Integrated Development ACP is designed to integrate directly into developer workflows through IDE plugins and supporting web services. Architects and engineers work with models and supporting scripts as primary development artifacts while using the ACP IDE plugin to perform modeling, validation, traceability analysis, code generation, and regeneration activities. End-to-End Traceability ACP maintains alignment between: Business Requirements Product Requirements Documents (PRDs) Software Project Model Diagrams (Phase 1 = UML via plantuml) and their supporting scripts Generated Code This traceability enables software implementations to be continuously validated against business and architectural intent. Business Requirements Validation (BRV) BRV provides traceability and validation between business requirements, software project model diagrams and their supporting scripts, and generated implementations to help ensure that software remains aligned with stakeholder objectives. Requirements Fidelity Score (RFS) RFS measures how closely software project model diagrams and their supporting scripts align with business requirements and use cases that are input into the BRV website portal by product managers. The manager can set percentage-based business-to-software project model and software project-to-code alignment values as the minimum that are acceptable for code development and/or release repository check-in actions. Code Fidelity Score (CFS) CFS validates generated code against approved software project model diagrams and supporting artifacts to help prevent architectural drift and implementation divergence. Model-Driven Integrity ACP treats business requirements, software project model diagrams, and their supporting scripts as the authoritative source of truth. To preserve alignment and traceability, software changes are intended to originate from approved models and scripts rather than from direct modifications to generated code. Generated code is continuously validated against these artifacts through automated validation and CI/CD workflows. Code that cannot be traced back to approved requirements, models, and scripts may fail validation, requiring updates to the underlying artifacts and regeneration of the affected code. This approach helps maintain business requirements-to-model-to-code alignment while reducing architectural drift, documentation divergence, and manual coding inconsistencies by preventing the IDE user from checking-in directly-modified AI-generated code into its repository. Incremental Code Generation ACP supports subsystem-based and incremental code generation, enabling large-scale systems to be generated, validated, and regenerated efficiently while minimizing unnecessary LLM compute. LLM-Agnostic Design ACP is designed to support multiple Large Language Models through abstraction layers and standardized prompt templates, reducing dependency on any single AI provider.

Powered by OpenAIRE graph
Found an issue? Give us feedback