Criteria for Authorship
Updated September 2020
Anyone listed as Author on an ACM manuscript submission must meet all the following criteria:
they have made substantial intellectual contributions to some components of the original work described in the manuscript; and
they have participated in drafting and/or revision of the manuscript and
They are aware the manuscript has been submitted for publication; and
They agree to be held accountable for any issues relating to correctness or integrity of the work
ACM requires that all published papers include the names and affiliations of all authors listed on the paper, as well as provide accurate contact information to ACM as required in the ACM rights contract. ACM does not allow anonymous authors, and any papers published in the ACM Digital Library without author names and affiliations may be retracted by ACM. ACM authors have published under actual pen names using “independent consultant” as the author's listed affiliation, but even under such circumstances ACM must be provided with contact information for such authors using a pen name, so that ACM will be able to reach all authors of published papers.
Other contributors may be acknowledged at the end of the paper, before the bibliography, with explicitly described roles, preferably using the roles found in the CASRAI Contributor Roles Taxonomy at http://casrai.org/CRediT.
Written by leading domain experts for software engineers, ACM Case Studies provide an in-depth look at how software teams overcome specific challenges by implementing new technologies, adopting new practices, or a combination of both. Often through first-hand accounts, these pieces explore what the challenges were, the tools and techniques that were used to combat them, and the solution that was achieved.
ACM Queue’s “Research for Practice” serves up expert-curated guides to the best of computing research, and relates these breakthroughs to the challenges that software engineers face every day. This installment, “The DevOps Phenomenon” by Anna Wiedemann, Nicole Forsgren, Manuel Wiesche, Heiko Gewald and Helmut Krcmar, gives an overview of stories from across the industry about software organizations overcoming early hurdles of adopting DevOps practices, and coming out on the other side with tighter integration between software and operations teams, faster delivery times for new software features, and achieving higher levels of stability.