IEEE/ACM International Conference on Automated Software Engineering (ASE)

IEEE/ACM International Conference on Automated Software Engineering (ASE)

Conference positioning

IEEE/ACM International Conference on Automated Software Engineering (ASE) is a top computer-science conference venue for automated software engineering, program analysis, testing, repair, synthesis, and AI-assisted development. It rewards an automation-for-SE paper with runnable artifact and realistic software benchmarks. Treat this skill as a fit / venue-selection / re-framing tool for conference submission strategy, not as a substitute for the current year's CFP, author kit, ethics policy, or submission portal.

Because CS conferences change deadlines, templates, page limits, review workflow, artifact rules, AI-use policy, and rebuttal formats every cycle, always verify the live official instructions before making a submission-ready recommendation. Start from the official source anchor recorded for this venue in ../../resources/conference-roster.md and ../../resources/official-source-map.md.

When to trigger

• The author names ASE / IEEE/ACM International Conference on Automated Software Engineering as the target venue.
• A manuscript in automated software engineering needs a conference-fit read before being formatted or submitted.
• The paper must be re-framed from journal style or arXiv style into a selective CS conference narrative.
• The author needs an evidence-gap, anonymity, artifact, rebuttal, or re-routing diagnosis for this venue.

Scope & topic fit

• Core fit: automated software engineering, program analysis, testing, repair, synthesis, and AI-assisted development.
• Best submissions make a precise contribution type visible: algorithm, theorem, system, dataset, benchmark, empirical finding, design artifact, tool, or socio-technical analysis.
• The paper should explain why the result matters to ASE's reviewers, not just why it is interesting to the authors' lab or product context.
• Position related work against the most recent conference-cycle papers in this venue and its closest siblings; stale comparisons are a common early-review weakness.
• If the contribution is interdisciplinary, state which part is CS research and which part is domain evidence.

Venue-specific calibration

• Reviewer lens: Treat ASE as a automated software engineering venue whose reviewers expect the scope and evidence to match its own community. Do not submit a generic CS paper until the introduction names the exact subcommunity, contribution type, and proof or empirical standard.
• Contribution hook to foreground: the venue-specific contribution bar.
• Scope vocabulary to use naturally in the abstract and introduction: automated software engineering, program analysis, testing, repair, synthesis, and AI-assisted development.
• Distinctive fingerprint for reviewer calibration: automated, software, engineering, program, analysis, testing, repair, synthesis, ai-assisted, development, venue-specific, contribution, conf, researchr.
• Official anchor domain: conf.researchr.org. Quote annual rules only after opening that source and the current-year CFP/author kit.

Close-neighbor routing guardrail

• Use this profile only when the manuscript's central contribution is genuinely in automated software engineering and the author can say why ASE reviewers are the primary audience, not merely a convenient deadline.
• Closest roster neighbors to compare before final routing: international-conference-on- software-engineering (ICSE), acm-international-conference-on-the-foundations-of-software- engineering (FSE), acm-sigsoft-international-symposium-on-software-testing-and-analysis (ISSTA), mining-software-repositories (MSR). Break ties by contribution type, evidence