domains / families / research / ase-topic-selection

ase-topic-selection

separate

Use when deciding whether a software-engineering project belongs at ASE (IEEE/ACM Automated Software Engineering) or should be routed to ICSE, ESEC/FSE, ISSTA, a PL venue, or an SE journal, and when distinguishing ASE by its automation-centric contribution shape, its tool/technique emphasis, and its AI4SE/SE4AI scope.

When to use

• deciding if a project belongs at ASE
• routing to ICSE, ESEC/FSE, ISSTA, PL venues, or SE journals
• distinguishing ASE by automation-centric contribution shape
• distinguishing ASE by tool/technique emphasis
• distinguishing ASE by AI4SE/SE4AI scope
• applying model-swap and re-label tests
• selecting co-located tracks like Research Papers or NIER
• performing cheap reconnaissance before committing

When not to use

• broad empirical or foundational SE contributions where the lesson is a finding
• depth in testing theory, program analysis foundations, or fault detection
• program-language or compiler advances
• new model or architecture contributions where the SE task is a benchmark
• studies too long or nuanced for the page budget

Skill page

Source