domains / families / research / socc-writing-style

socc-writing-style

separate

Use when revising an ACM SoCC paper for a cloud-scale problem an operator recognizes on the first page, a contribution at the systems-and-data intersection, evidence measured on a real or realistic deployment with tail latency and cost as first-class, dual-anonymous wording, and disciplined use of the acmart 12-page budget.

When to use

• revising an ACM SoCC paper
• framing cloud-scale problems in operator terms
• positioning contributions at systems-and-data intersection
• reporting tail latency and cost metrics
• pairing claims with measured evidence
• stating limitations honestly
• maintaining dual anonymity
• managing the 12-page budget

When not to use

• pure-OS results with a cloud title
• benchmarks with no systems contribution
• papers reporting only mean metrics
• papers with untuned baselines
• papers lacking external validity statements

Skill page

Source