domains / families / research / fse-writing-style

fse-writing-style

separate

Use when revising an ESEC/FSE paper for a practitioner-grounded software-engineering contribution on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the ACM-template page budget.

When to use

• revising an ESEC/FSE paper
• stating a software-engineering contribution on the first page
• defining research-question contracts
• writing a threats-to-validity section that argues rather than recites
• ensuring evidence is proportional to the claim
• maintaining double-anonymous wording
• managing the ACM-template page budget

When not to use

• writing systems demos
• writing ML results with an SE title

Skill page

Source