Research PapersREFSQ 2023

Requirements Engineering (RE) is a critical factor in developing high-quality and successful software, systems, and services. The REFSQ working conference series is an established international forum for discussing current and state-of-the-art RE practices, celebrating its 29th edition.

Please check the CfP here: https://2023.refsq.org/track/refsq-2023-papers#Call-for-Papers

Supporters

Organized by

Organized by

Organized by

Sponsored by

Supported by

Supported by

Accepted Papers

In response to the Call for Papers, we received 84 abstracts, which resulted in 78 full papers, which reviewed by three program committee members, extensively discussed among the reviewers, and then brought for additional discussion if needed and final decision at the plenary program committee meeting that was held (online) on January 17 and 18, 2023. Nine papers for which no consensus had been reached were discussed in special depth, with nine of them accepted on the condition that certain improvements be made (those underwent an additional check by a PC member before final acceptance).

Overall, 25 papers were finally accepted for publication. In particular, based on paper category, the acceptance ratios are as follows:

• Scientific Evaluation (15 pages): 20 submissions, 7 accepted (35%)

• Technical Design (15 pages): 22 submissions, 5 accepted (23%)

• Experience report papers (12 pages): 14 submissions, 5 accepted (36%)

• Vision (8 pages): 3 submissions, 2 accepted (67%)

• Research Preview (8 pages): 14 submissions, 6 accepted (43%)

The acceptance rate of full contributions was thus 29% (12/42).

List of accepted papers

Call for Papers

IMPORTANT NEWS: Submission of new papers is allowed until Nov. 18th, 2022 also for authors who did not submit a preliminary abstract by the abstract deadline (Nov. 11th, 2022). Updates of papers submitted by the deadline of Nov. 18th, 2022 are allowed until Nov. 23rd, 2022

We invite original submissions in the following categories:

• Technical design papers (15 pages incl. references) describe the design of new artifacts, i.e., novel solutions for requirements-related problems or significant improvements of existing solutions. A preliminary evaluation of the artifacts is also expected.
• Scientific evaluation papers (15 pages incl. references) investigate existing real-world problems, evaluate existing real-world implemented artifacts, or validate newly designed artifacts, e.g., by means such as case studies, experiments, simulation, surveys, systematic literature reviews, mapping studies, or action research. Check the Empirical Standards for guidelines and review criteria for each research type: https://github.com/acmsigsoft/EmpiricalStandards
• (NEW this year) Experience report papers (12 pages incl. references) describe retrospective reports on experiences in applying RE techniques in practice, or addressing RE problems in real-world contexts. These papers focus on reporting the experience in a narrative form, and give prominence to the lessons learned by the authors and/or by the participants. Experience reports include also studies in which academics interview practitioners about the application of specific RE techniques, or about RE problems in practice.
• Vision papers (8 pages incl. references) state where research in the field should be heading.
• Research previews (8 pages incl. references) describe well-defined research ideas at an early stage of investigation which may not be fully developed.

Each type of paper has its own review criteria, which are listed here: https://2023.refsq.org/track/refsq-2023-papers#Review-Criteria

Submission, Reviewing, and Publication

Contributions must be submitted to: https://easychair.org/conferences/?conf=refsq2023

Each submission in the scope of REFSQ will undergo a single-blind review process that will involve at least three members of the program committee.

The REFSQ 2023 proceedings will be published in Springer’s LNCS series.

The best papers will be invited to submit an extended version of their contribution to a Special Issue of the Requirements Engineering Journal

Formatting

All submissions must be formatted according to the Springer LNCS/LNBIP conference proceedings template (for LaTeX and Word): https://www.springer.com/gp/computer-science/lncs/conference-proceedings-guidelines. As per the guidelines, please remember to include keywords after your abstract.

Furthermore, to facilitate accurate bidding and a better understanding of the papers, each paper submitted to REFSQ 2023 is required to have a structured abstract. The imposed structure demands each abstract have exactly 4 paragraphs with the following content:

• Context and motivation: Situate and motivate your research.
• Question/problem: Formulate the specific question/problem addressed by the paper.
• Principal ideas/results: Summarize the ideas and results described in your paper. State, where appropriate, your research approach and methodology.
• Contribution: State the main contribution of your paper. What’s the value you add (to theory, to practice, or to whatever you think that the paper adds value). Also, state the limitations of your results.

Three examples of structured abstracts are given here.

Each paper category has its own review criteria. We invite authors and reviewers to check the criteria and consider their order of relevance.

Technical design papers (15 pages incl. references) describe the design of new artifacts, i.e., novel solutions for requirements-related problems or significant improvements of existing solutions. A preliminary evaluation of the artifacts is also expected.

Review Criteria (in order of relevance):

• Novelty: to what extent is the proposed solution novel with respect to the state-of-the-art? To what extent is related literature considered? To what extent did the authors clarify their contribution?
• Potential Impact: is the potential impact on research and practice clearly stated? Is the potential impact convincing? Has the proposed solution been preliminarily evaluated in a representative setting?
• Soundness: has the novel solution been developed according to recognised research methods? Is the preliminary evaluation of the solution sound? Did the authors clearly state the research questions? Are the conclusions of the preliminary evaluation logically derived from the data? Did the authors discuss the limitations of the proposal?
• Verifiability: did the authors share their software? Did the authors share their data? Did the authors provide guidelines on how to reuse their artfiacts and replicate their results? [NOTE: sharing data and software is NOT mandatory, but papers that make an effort in this direction should be adequately rewarded]
• Presentation: is the paper clearly presented? To what extent can the content of the paper be understood by the general RE public? If highly technical content is presented, did the authors make an effort to also summarise their proposal in an intuitive way?

Scientific evaluation papers (15 pages incl. references) investigate existing real-world problems, evaluate existing real-world implemented artifacts, or validate newly designed artifacts, e.g., by means such as case studies, experiments, simulation, surveys, systematic literature reviews, mapping studies, or action research. Check the Empirical Standards for guidelines and review criteria for each research stretegy: https://github.com/acmsigsoft/EmpiricalStandards

Review Criteria (in order of relevance):

• Soundness: has the novel solution been developed according to recognised research methods? Is the research method justified? Is the research method adequate for the problem at hand? Did the authors clearly state the research questions, data collection, and analysis? Are the conclusions of the evaluation logically derived from the data? Did the authors discuss the threats to validity?
• Potential Impact: is the potential impact on research and practice clearly stated? Is the potential impact convincing? Was the study carried out in a representative setting?
• Verifiability: did the authors share their software? Did the authors share their data? Did the authors provide guidelines on how to reuse their artfiacts and replicate their results? [NOTE: sharing data and software is NOT mandatory, but papers that make an effort in this direction should be adequately rewarded]
• Novelty: to what extent is the study novel with respect to the related literature? To what extent is related literature considered? To what extent did the authors clarify their contribution? To what extent does the study contribute to extend the body of knowledge in requirements engineering?
• Presentation: is the paper clearly presented? To what extent can the content of the paper be understood by the general RE public? If highly technical content is presented, did the authors make an effort to also summarise their study in an intuitive way?

Experience report papers (12 pages incl. references) describe retrospective reports on experiences in applying RE techniques in practice, or addressing RE problems in real-world contexts. These papers focus on reporting the experience in a narrative form, and give prominence to the lessons learned by the authors and/or by the participants. Experience reports include also studies in which academics interview practitioners about the application of specific RE techniques, or about RE problems in practice.

Review Criteria (in order of relevance):

• Relevance of the Application: is the application context in which the experience is carried out interesting for the RE public? Is the application context sufficiently representative? To what extent is the paper reporting a real-world experience involving practitioners? Is the experience credible?
• Relevance of Lessons Learned: are the lessons learned sufficiently insightful? Did the authors report convincing evidence, also anecdotal, to justify the lessons learned?
• Potential for Discussion: will the presentation of the paper raise discussion at the REFSQ conference? To what extent can REFSQ participants take inspiration to develop novel solutions based on the reported experience? To what extent can REFSQ participants take inspiration to perform sound empirical evaluations based on the reported experience?
• Novelty: is the context of the study in line with the current RE practice? Does the study report on a contemporary problem that RE practitioners and researchers typically face?
• Presentation: is the application context clearly presented? Are the lessons learned clearly described? To what extent can the content of the paper be understood by the general RE public?

Vision papers (8 pages incl. references) state where research in the field should be heading.

Review Criteria (in order of relevance):

• Potential Impact: will the vision impact the future research and practice in RE? Is a roadmap discussed? Is the vision sufficiently broad to affect different subfields of RE? Do the authors discuss both short-term and long-term impacts of their vision?
• Potential for Discussion: will the presentation of the vision raise the interest of the REFSQ audience? Will the vision raise discussion? Can the vision raise controversial opinions in the audience?
• Novelty: is the vision sufficiently novel with respect to existing reflections within the REFSQ community? Do the authors clarify the novelty of their vision?
• Soundness of Arguments: is the vision supported by logical arguments? Are the implications convincing?
• Presentation: is the vision presented in a compelling way? Is the vision presented in a way that can elicit reflections in the RE community?

Research previews (8 pages incl. references) describe well-defined research ideas at an early stage of investigation which may not be fully developed.

Review Criteria (in order of relevance):

• Novelty: did the research preview make you say “I heard it first at REFSQ!”? Is the idea sufficiently novel with respect to the state-of-the-art? Do the authors discuss related work and the contribution of their study?
• Soundness of the Research Plan: do the authors present a convincing research plan? Did the authors discuss the limitations and risks of their plan? Is the plan referring to sound research methods? Do the authors clarify their research questions, planned data collection, and data analysis? Did the authors perform a convincing proof-of-concept or preliminary research step?
• Potential for Discussion: will the presentation of the preview raise the interest of the REFSQ audience? Will the preview raise discussion? Will the audience be able to provide useful feedback to the authors, given the typical background of the REFSQ audience? Can the preview raise controversial opinions in the audience?
• Presentation: is the paper clearly presented? To what extent can the content of the paper be understood by the general RE public?