Research PapersCHASE 2022

Accepted Papers

Call for Papers

Human beings are variously active, aloof, balanced, baffled, clever, complex, daring, defensive, ecstatic, embarrassed, fascinated, fatigued, gifted, green, handy, horrified, idealistic, idealizing, jargoning, jaded, keen, Kantian, likable, laborious, masterful, muttering, neat, neglecting, observant, offendable, paramount, pale, quick, quiet, rational, relieved, scant, scentful, talented, taciturn, unafraid, ubiquitous, vigorous, vague, wary, whimsical, x-ray-y, xenophilic, yodeling, yonder, zealous, and zigzagging. And they cooperate for developing software. At CHASE, researchers believe software engineering can learn a lot from investigating how those humans do this or might do this. We find out what they do and what might help them to do it better.

Topics can be anything human-related in software engineering, such as:

• Social, emotional, and cognitive aspects of software development, whether at the levels of individual, pair, group, team, organization, or community.
• Roles, practices, conventions, patterns of behavior, whether in technical or non-technical activities and whether in generic or specialized domains.
• Issues of leadership, self-organization, cooperation, management, socio-technical (in)congruence, stakeholder groups, participation.
• The role of tools, whether existing, prototypical, or simulated.
• Meta-research about any of these.

CHASE welcomes research using any research method that is appropriate for the purpose, if it is focused on learning about cooperative and human aspects of software engineering. The research should predominantly study humans, not technology.

Important Dates

• Abstract submission: 13 January, 2022, AoE (submitting an abstract is not mandatory)
• Paper submission: 18 January, 2022, AoE
• Notification: 8 March, 2022
• Camera-ready submission: 31 March, 2022, AoE
• CHASE conference: May 18-19, 2022

Evaluation criteria for full papers

1. CHASE is a high-quality outlet. Full papers must present mature research. They must clearly state a contribution and provide strong argumentation why that contribution is relevant and valid.
2. CHASE expects and values relevance. Clearly argue what is novel about your contribution and how it can help software engineering.
3. CHASE requires soundness. All research requires assumptions. An assumption can be reliable, reasonable, risky, or ridiculous. Soundness means to allow only reliable assumptions to remain implicit. State all reasonable assumptions. State and thoroughly discuss all risky assumptions. Be especially careful when interpreting or generalizing. CHASE will accept risky assumptions or conjectures as long as a) they are clearly marked as such, b) they are needed to enable higher relevance, and c) you convince the reviewers they are often true. Future research may show when and when not they are true.
4. CHASE is human-oriented, so we expect an easy-to-digest write-up: We recommend to: use a structured abstract (Background, Objective, Method, Results, Conclusion); define key terms; write concisely; consider using color, symbols, boxes; provide tables and figures to reduce prose; provide cross-references; do not repeat sentences between abstract, introduction, and conclusion. Strong research with a weak presentation may well be rejected.

Tracks (submission types)

• Full papers (up to 10 pages total), as described above.
• Emerging results papers (4-5 pages total): concise presentations of work with yet-too-little data, yet-incomplete analysis, or too-narrow scope. Evaluation criteria 2 and 4 apply, evaluation criterion 3 must be fulfilled as well as is possible in the reduced space. Discussion of related work can be kept short.
• Vote Items papers (2 pages total) present a single idea, often a conjecture, for focused feedback from the community. Must have a short abstract and exactly three sections in the body: “Background”, “Information, Idea, Arguments”, and “Vote” only. Subsections are allowed. “Information, Idea, Arguments” presents the idea, “Vote” presents one (and only one) single-choice or multiple-choice question with at most 7 choices for voting. See the example Vote Item for illustration. Conference participants will be asked to vote, either in a vote item short-presentation session or outside. CHASE will coordinate use of a common voting system. Evaluation criteria 2 and 4 apply, except that abstract structure matches section structure. Prefix the title with “Vote Item:”.
• Journal-First presentations (abstract with appended article DOI URL only, no PDF): Strong CHASE-ish software engineering works that have appeared as Open Access articles in what few pertinent high-quality journals we have in the field no earlier than January 2021, for presentation at the conference. Prefix the title with “Journal First:”. Works that are not Open Access do not qualify. It does not matter whether the whole journal is Open Access or not. Evaluation will focus on criterion 2 and will use criterion 4 as a proxy for expected presentation quality.

Reviewing process

• Submissions will be reviewed by three reviewers.
• CHASE uses double-blind reviewing, but reviewers are allowed to sign their reviews if they want to. Authors must not directly identify themselves: They must not print their names on initial submissions and must refer to their own work in the third person throughout – the goal is to allow reviewers to ignore who you are. See also “Double-Anonymous Submissions” in the ICSE 2022 Q&A page. Supplementary material must also conform to the double-blind policy; consider the advice at https://ineed.coffee/5205. Obviously, Journal-First submissions are exempt from these requirements.
• Reviewers must respect the “Invalid Criticisms” item lists of the ACM Empirical Standard for the respective research methods used. Authors should make sure they describe their methods choices such that it points to the standard(s) they deem most appropriate for their work.

Submission process and submission Link

Submit via Easychair at https://easychair.org/conferences/?conf=chase2022 before the submission deadline.

Use the official “ACM Primary Article Template” from the ACM Proceedings Template page. LaTeX users should use the sigconf option, as well as the review (to produce line numbers for easy reference by the reviewers) and anonymous (omitting author names) options:

\documentclass[sigconf,review,anonymous]{acmart}

\acmConference[CHASE 2022]{CHASE '22: Proceedings of the 15th International Conference on Cooperative and Human Aspects of Software Engineering (CHASE)}{May 21–22, 2022}{Pittsburgh, PA, USA}

Submissions must comply with the ACM Policy and Procedures on Plagiarism and the IEEE Plagiarism FAQ. In particular, papers (and likewise Journal-First presentations) submitted to CHASE 2022 must not have been published elsewhere and must not be under review elsewhere while under review for CHASE. The submission must also comply with the authorship policy of the ACM and the authorship policy of the IEEE.

Publication and Presentation

• Authors of accepted papers are encouraged to share preprints of their work.
• Upon acceptance, all authors of accepted papers will be asked to complete a Copyright form and will receive further instructions for preparing their camera-ready versions.
• At least one author of each paper must register and present the paper at the conference; otherwise the paper will be excluded from both the program and the proceedings. Authors of accepted papers will receive further instructions about paper presentations.
• All accepted papers will be published in the conference electronic proceedings, which will also be available in the ACM and IEEE Digital Library. The official publication date is the date the proceedings are made available in the ACM or IEEE Digital Libraries. This date may be up to two weeks prior to the first day of ICSE 2022. The official publication date affects the deadline for any patent filings related to published work.
• Purchasing additional pages in the proceedings is not possible.

Program committee

See https://conf.researchr.org/committee/chase-2022/chase-2022-program-committee.