AI & ML
Agent Trajectories as Evidence for Software Quality Assurance
arXiv cs.SE0 views
arXiv:2611.22323v1 Announce Type: new Abstract: Autonomous software agents increasingly plan, implement, and test software with limited human oversight. Their decisions may introduce implicit assumptions that final code and passing tests do not adequately expose. We propose analyzing observable agent trajectories alongside software and agent specifications and AI generated artifacts as evidence for targeted quality assurance. The aim is to prioritize consequential decisions for scrutiny, investigate their possible contribution to software problems, and inform improvements to specifications and development practices. Industrial experience motivates the idea; available execution records and preliminary analysis methods make it plausible. However, trajectories alone do not establish that decisions are justified, outcomes acceptable, or corrective changes effective. We ask how this evidence can support review, diagnosis, and continuous quality improvement, and when simpler QA approaches suffice. Perspectives from requirements engineering, verification and validation, agent systems, causal inference, empirical software engineering, and human factors could help develop and evaluate the idea.
Source:https://arxiv.org/abs/2611.22323PreviousOperating an Agent-Driven Dataset Factory: Discovery, Construction, and Public ReleaseNextFormal Analysis of a Fault-Tolerant Extension of the ROSACE Flight Controller
Related posts
What Might the Next Generation of AI Look Like?
0dev.to Discuss
NVIDIA Q3 FY27 Earnings: $115.8B Revenue, $390B Supply Gamble and the Post-Jensen AI Infrastructure Test
0dev.to Discuss
Do developers actually think about code energy efficiency, or is it just about cloud bills?
0dev.to Discuss
Best AI Humanizer Tools for SEO Articles and Long-Form Blog Posts
0dev.to Productivity
Beyond Notes: 10 Hidden Power‑Ups in iPhone’s Notes App
0dev.to Productivity

I let Claude map a business process through MCP, and it writes code instead of drawing boxes
0dev.to Productivity