From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=192.134.164.83; helo=mail2-relais-roc.national.inria.fr; envelope-from=caml-list-owner@inria.fr; receiver= Authentication-Results: plum; dmarc=pass (p=none dis=none) header.from=inria.fr Authentication-Results: plum.tunbury.org; dkim=pass (1024-bit key; unprotected) header.d=inria.fr header.i=@inria.fr header.a=rsa-sha256 header.s=dc header.b=FIy1gg42; dkim=fail reason="signature verification failed" (1024-bit key) header.d=inria.fr header.i=@inria.fr header.a=rsa-sha256 header.s=dc header.b=oJXpUA8g; dkim-atps=neutral Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by plum.tunbury.org (Postfix) with ESMTPS id 5FE9CB80123 for ; Tue, 12 Nov 2024 19:13:58 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:message-id:in-reply-to:references: mime-version:subject:reply-to:sender:list-id:list-help: list-subscribe:list-unsubscribe:list-post:list-owner: list-archive; bh=giIf2AsNYmlXK2cf6+8lrcYr/079F/Ey/AwRblh2m6w=; b=FIy1gg428gczdIaFcw/+rYEXizazsJWBzfP68UHlHNi/nTl01HdSP4nB v/3CFFe9htvFLn387AUYdYbNl8ZUf4VO4ZDY2K3GWS4WpWKsP7zIwcBL/ kDnW0bSc7FBFQC42wl/fy+/cY1/x6SjVEK5y1+Zr/RqZv6pE0g4ORypZq w=; Received-SPF: Pass (mail2-relais-roc.national.inria.fr: domain of caml-list-owner@inria.fr designates 128.93.162.160 as permitted sender) identity=mailfrom; client-ip=128.93.162.160; receiver=mail2-relais-roc.national.inria.fr; envelope-from="caml-list-owner@inria.fr"; x-sender="caml-list-owner@inria.fr"; x-conformance=spf_only; x-record-type="v=spf1"; x-record-text="v=spf1 include:mailout.safebrands.com a:basic-mail.safebrands.com a:basic-mail01.safebrands.com a:basic-mail02.safebrands.com ip4:128.93.142.0/24 ip4:192.134.164.0/24 ip4:128.93.162.160 ip4:128.93.162.3 ip4:128.93.162.88 ip4:89.107.174.7 mx ~all" Received-SPF: None (mail2-relais-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@sympa.inria.fr) identity=helo; client-ip=128.93.162.160; receiver=mail2-relais-roc.national.inria.fr; envelope-from="caml-list-owner@inria.fr"; x-sender="postmaster@sympa.inria.fr"; x-conformance=spf_only Authentication-Results: mail2-relais-roc.national.inria.fr; spf=Pass smtp.mailfrom=caml-list-owner@inria.fr; spf=None smtp.helo=postmaster@sympa.inria.fr; dkim=hardfail (signature did not verify [final]) header.i=@inria.fr X-IronPort-AV: E=Sophos;i="6.12,148,1728943200"; d="scan'208,217";a="193466377" Received: from prod-listesu18.inria.fr (HELO sympa.inria.fr) ([128.93.162.160]) by mail2-relais-roc.national.inria.fr with ESMTP; 12 Nov 2024 20:13:57 +0100 Received: by sympa.inria.fr (Postfix, from userid 20132) id D5011E0D21; Tue, 12 Nov 2024 20:13:56 +0100 (CET) Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 570DBE00B7 for ; Tue, 12 Nov 2024 20:13:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=inria.fr; s=dc; h=date:from:to:message-id:in-reply-to:references:subject: mime-version; bh=giIf2AsNYmlXK2cf6+8lrcYr/079F/Ey/AwRblh2m6w=; b=oJXpUA8giE2ZFESnMEd0swdcPAXwMRaAcHIjgFgmvCDdjIpL3+MQBfye c8GerK5xgVrsvTqHZLiKbBYrxXsbIfnjF4tfe6ty4Fv/3Hd9B3YAa5D91 vH/TEjIdl40b91o1udNESt2CsJOUGkZoADBx7ZgacwdeMMvSpKrRY2JAz o=; X-IronPort-AV: E=Sophos;i="6.12,148,1728943200"; d="scan'208,217";a="193466364" X-MGA-submission: =?us-ascii?q?MDG4sJLZqzSO9Qm+t3dwz0AbX+WACyumAOoyOt?= =?us-ascii?q?osOZokALqHP5SKlecOs6DOTJAFFU2dDfVOzSG+L1e3xATZsgn67emaht?= =?us-ascii?q?FccNxoW71eYjRmA0kMhB1P+qZQluoNPKJrjCfsQ5acSOSTJdrcA6XlJV?= =?us-ascii?q?r9KmlCBcOan867WDC0GheoLA=3D=3D?= Received: from zcs2-store6.inria.fr ([128.93.142.9]) by mail2-relais-roc.national.inria.fr with ESMTP; 12 Nov 2024 20:13:54 +0100 Date: Tue, 12 Nov 2024 20:13:54 +0100 (CET) From: Gwen =?iso-8859-1?Q?Sala=FCn?= To: caml-list@inria.fr Message-ID: <1105676587.10280210.1731438834150.JavaMail.zimbra@inria.fr> In-Reply-To: <873134949.10280152.1731438793206.JavaMail.zimbra@inria.fr> References: <1189830282.8031417.1727366403752.JavaMail.zimbra@inria.fr> <295988495.10094571.1731427411416.JavaMail.zimbra@inria.fr> <1162161683.10100256.1731427521408.JavaMail.zimbra@inria.fr> <2135772802.10110533.1731427615645.JavaMail.zimbra@inria.fr> <1403243621.10132379.1731427739685.JavaMail.zimbra@inria.fr> <870746417.10228625.1731430020299.JavaMail.zimbra@inria.fr> <768910743.10229249.1731430086257.JavaMail.zimbra@inria.fr> <873134949.10280152.1731438793206.JavaMail.zimbra@inria.fr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_2b2e7be4-eebb-434f-9e47-ec3e3aace711" X-Originating-IP: [88.174.152.45] X-Mailer: Zimbra 10.0.9_GA_4654 (ZimbraWebClient - FF128 (Mac)/10.0.9_GA_4654) Thread-Topic: Final Call for Papers: FORMALISE 2025 - EXTENDED DEADLINES Thread-Index: dQ2r7SghqkFmzM+mngZpBtXMIS+w8XGUPUevvBBShOF+MOFdvrzd5LyB5Fx8rLN/bwoBcFuU896FVyjhdC01IqVKuw7/oFH0uMTqvd2YPs2Rio12J8K18VXaMnP1CUxv1KkoAaCYIWFLtr59YmIAzw== Subject: [Caml-list] Final Call for Papers: FORMALISE 2025 - EXTENDED DEADLINES Reply-To: Gwen =?iso-8859-1?Q?Sala=FCn?= X-Loop: caml-list@inria.fr X-Sequence: 19200 Errors-To: caml-list-owner@inria.fr Precedence: list Precedence: bulk Sender: caml-list-request@inria.fr X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: Archived-At: --=_2b2e7be4-eebb-434f-9e47-ec3e3aace711 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Call for Papers: FORMALISE 2025=20 13th International Conference on Formal Methods in Software Engineering=20 27 and 28 April, 2025=20 co-located with ICSE 2025 (April 27-May 3, 2025), Ottawa, Canada=20 https://conf.researchr.org/home/Formalise-2025=20 Overview=20 Historically, formal methods academic research and practical software devel= opment have had limited mutual interactions =E2=80=94 except possibly in sp= ecialized domains such as safety-critical software. In recent times, the ou= tlook has considerably improved: on the one hand, formal methods research h= as delivered more flexible techniques and tools that can support various as= pects of the software development process: from user requirements elicitati= on, to design, implementation, verification and validation, as well as the = creation of documentation. On the other hand, software engineering has deve= loped a growing interest in rigorous techniques applied at scale.=20 The FormaliSE conference series promotes work at the intersection of the fo= rmal methods and software engineering communities, providing a venue to exc= hange ideas, experiences, techniques, and results. We believe more collabor= ation between these two communities can be mutually beneficial by fostering= the creation of formal methods that are practically useful and by helping = develop higher-quality software.=20 Originally a workshop event, since 2018 FormaliSE has been organized as a c= onference co-located with ICSE. The 13th edition of FormaliSE will also tak= e place as a co-located conference of ICSE 2025.=20 Areas of interest include but are not limited to:=20 *=20 requirements formalization and formal specification;=20 *=20 approaches, methods and tools for verification and validation;=20 *=20 formal approaches to safety and security related issues;=20 *=20 analysis of performance and other non-functional properties based on formal= approaches;=20 *=20 scalability of formal method applications=20 *=20 integration of formal methods within the software development lifecycle (e.= g., change management, continuous integration, regression testing, and depl= oyment)=20 *=20 model-based engineering approaches;=20 *=20 correctness-by-construction approaches for software and systems engineering= ;=20 *=20 application of formal methods to specific domains, e.g., autonomous, cyber-= physical, intelligent, and IoT systems;=20 *=20 formal methods for AI-based systems (FM4AI), and AI applied in formal metho= d approaches (AI4FM);=20 *=20 formal methods in a certification context=20 *=20 case studies developed/analyzed with formal approaches=20 *=20 experience reports on the application of formal methods to real-world probl= ems;=20 *=20 guidelines to use formal methods in practice;=20 *=20 usability of formal methods.=20 Important dates :=20 *=20 Abstracts due: 18 November 2024 (AoE) - EXTENDED DEADLINE=20 *=20 Submissions: 25 November 2024 (AoE) - EXTENDED DEADLINE=20 *=20 Notifications: 13 January 2025=20 *=20 Camera ready copies: 5 February 2025=20 *=20 FormaliSE conference: 27-28 April 2025=20 Paper submission guidelines=20 We accept papers in three categories:=20 *=20 Full research papers describing original research work and results. We enco= urage authors to include validation of their contributions by means of a ca= se study or experiments. We also welcome research papers focusing on tools = and tool development.=20 *=20 Case study papers discussing a significant application that suggests genera= l lessons learned and motivates further research, or empirically validates = theoretical results (such as a technique's scalability).=20 *=20 Research ideas papers describing new ideas in preliminary form, in a way th= at can stimulate interesting discussions at the conference, and suggest fut= ure work.=20 All papers submitted to the FormaliSE 2025 conference must be written in En= glish, must be unpublished original work, and must not be under review or s= ubmitted elsewhere at the time of submission. Submissions must comply with = the FormaliSE's lightweight double-anonymous review process (see below).=20 Full research papers and case study papers can take up to 10 pages includin= g all text, figures, tables and appendices, but excluding references. Resea= rch ideas papers can take up to 4 pages, plus up to 1 additional page solel= y for references.=20 To avoid that authors waste time fitting their papers into the stated limit= at the expense of presentation clarity, paper lengths slightly exceeding t= he stated limit will still be considered, provided that the reviewers find = that the presentation is of high quality.=20 All submissions must be in PDF format and must conform to the IEEE conferen= ce proceedings template, specified in the IEEE Conference Proceedings Forma= tting Guidelines (i.e., title in 24pt font and full text in 10pt type): htt= ps://www.ieee.org/conferences/publishing/templates.html=20 In LaTeX, use \documentclass[10pt,conference]{IEEEtran} without including t= he compsoc or compsocconf options.=20 To submit a paper to FormaliSE 2025 use this HotCRP link: https://formalise= 25.hotcrp.com/=20 Lightweight Double-Blind Review Process for Papers=20 As in recent editions, FormaliSE 2025 will use a lightweight double-anonymo= us process. Authors must omit their names and institutions from the title p= age, cite their own work in the third person, and omit acknowledgments that= may reveal their identity or affiliation. The purpose is reducing chances = of reviewer bias influenced by the authors=E2=80=99 identities. The double-= anonymous process is, however, lightweight, which means that it should not = pose a heavy burden for authors, nor should make a paper's presentation wea= ker or more difficult to review. Also, advertising the paper as part of you= r usual research activities (for example, on your personal web-page, in a p= re-print archive, by email, in talks or discussions with colleagues) is per= mitted without penalties.=20 Paper selection=20 Each paper will be reviewed by at least three program committee members tha= t will judge its overall quality in terms of its soundness, significance, n= ovelty, verifiability, and presentation clarity.=20 FormaliSE 2025 will adopt a lightweight response process: if all the review= ers of a given paper agree that a clarification from the authors regarding = a specific question could move the paper from "borderline" to "accept", the= chairs will relay the reviewers' questions to the authors by email, and th= en share their reply with the reviewers in HotCRP. The goal of lightweight = responses is reducing the chance of random decisions on borderline papers. = Hence, they will only be used for a minority of submissions; most papers wi= ll not require such an author response. Nevertheless, we would ask the corr= esponding authors of all submissions to make sure that they are available t= o answer questions by email upon request.=20 Artifact Evaluation=20 Reproducibility of experimental results is crucial to foster an atmosphere = of trustworthy, open, and reusable research. To improve and reward reproduc= ibility, FormaliSE 2025 continues its Artifact Evaluation (AE) procedure. A= n artifact is any additional material (software, data sets, machine-checkab= le proofs, etc.) that substantiates the claims made in the paper and ideall= y makes them fully reproducible.=20 Submission of an artifact is optional but encouraged for all papers where i= t can support the results presented in the paper. Artifact review is single= -anonymous (the paper corresponding to an artifact must still follow the do= uble-anonymous submissions requirements) and will be conducted concurrently= with the paper reviewing process. Artifacts will be handled by a separate = Artifact Evaluation Committee, and the Artifact Evaluation process will be = set up such that the anonymization of the corresponding papers will not be = compromised. Accepted papers with a successfully evaluated artefact will be= awarded the [EAPLS badges ( [ https://eapls.org/pages/artifact_badges/ | h= ttps://eapls.org/pages/artifact_badges/ ] ) that apply (among "Functional",= "Reusable", and "Available"). Awarded badges are to be added to the camera= -ready version of the paper.=20 Artifacts will be assessed with respect to their consistency with the resul= ts presented in the paper, their completeness, their documentation, and the= ir ease of use. The Artifact Evaluation will include an initial check for t= echnical issues; authors of artifacts may be contacted by email within the = first two weeks after artifact submission to help resolve any technical pro= blems that prevent the evaluation of an artifact if necessary.=20 The results of an artifact evaluation will not be available to the reviewer= s of the corresponding paper; hence, they will not affect the paper's accep= tance decision. However, reviewers will know whether a paper has submitted = *any* artifacts; this piece of information may be taken into account to dec= ide whether the paper should be accepted. Thus, if there are justifiable re= asons why a paper's artifacts cannot be submitted, they should be pointed o= ut in the paper so that the reviewers can appreciate them and adjust their = expectations accordingly.=20 Detailed guidelines for preparation and submission of artifacts will be des= cribed in a dedicated page in FormaliSE 2025's website.=20 Publication=20 All accepted papers are published as part of the ICSE 2025 Proceedings in t= he ACM and IEEE Digital Libraries.=20 At least one author of each accepted paper is required to register for the = conference and present the paper at the conference =E2=80=94 physically or,= if the circumstances do not allow so, virtually. Failure to register an au= thor will result in a paper being removed from the proceedings.=20 General Chairs=20 *=20 Stefania Gnesi, Istituto di Scienza e Tecnologie dell=E2=80=99Informazione,= Italy=20 *=20 Nico Plat, Thanos, The Netherlands=20 Program Chairs=20 *=20 Anastasia Mavridou, KBR / NASA Ames Research Center, USA=20 *=20 Gwen Sala=C3=BCn, University Grenoble Alpes, France=20 Artifact Evaluation Chairs=20 *=20 =C3=81kos Hajdu, Meta, UK=20 *=20 Lina Marsso, University of Toronto, Canada=20 Social Media Chair=20 *=20 Quentin Nivon, University Grenoble Alpes, France=20 Program committee=20 *=20 Bernhard Aichernig, TU Graz, Austria=20 *=20 Toshiaki Aoki, Japan Advanced Institute of Science and Technology, Japan=20 *=20 Kyungmin Bae, Pohang University of Science and Technology, Korea=20 *=20 Domenico Bianculli, University of Luxembourg, Luxembourg=20 *=20 Simon Bliudze, INRIA Lille - Nord Europe, France=20 *=20 Giovanna Broccia, ISTI - CNR, Italy=20 *=20 Radu Calinescu, University of York, UK=20 *=20 Pablo Castro, National University of Rio Cuarto, Argentina=20 *=20 Zhenbang Chen, NUDT, China=20 *=20 Nancy Day, University of Waterloo, Canada=20 *=20 Francisco Dur=C3=A1n, University of M=C3=A1laga, Spain=20 *=20 Marie Farrell, University of Manchester, UK=20 *=20 Carlo A. Furia, USI Lugano, Switzerland=20 *=20 Fatemeh Ghassemi, University of Tehran, Iran=20 *=20 Divya Gopinath, KBR/ NASA Ames Research Center, USA=20 *=20 Yann-Ga=C3=ABl Gu=C3=A9h=C3=A9neuc, Concordia University, Canada=20 *=20 Paula Herber, University of M=C3=BCnster, Germany=20 *=20 Marieke Huisman, University of Twente, The Netherlands=20 *=20 Fuyuki Ishikawa, National Institute of Informatics, Japan=20 *=20 Xiaoqing Jin, Apple Inc., USA=20 *=20 Violet Ka I Pun, Western Norway University of Applied Sciences, Norway=20 *=20 Oleksandr Kolchyn, Glushkov Institute of Cybernetics, Ukraine=20 *=20 Ant=C3=B3nia Lopes, University of Lisbon, Portugal=20 *=20 Larissa Meinicke, University of Queensland, Australia=20 *=20 Camilo Rocha, Pontificia Universidad Javeriana, Colombia=20 *=20 Cristina Seceleanu, M=C3=A4lardalen University, Sweden=20 *=20 Arpit Sharma, EECS Department, IISER Bhopal, India=20 *=20 Allison Sullivan, University of Texas, Arlington, USA=20 *=20 Heike Wehrheim, University of Oldenburg, Germany=20 --=_2b2e7be4-eebb-434f-9e47-ec3e3aace711 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

=
Call for Papers: FORMALISE 202= 5
<= div style=3D"font-family:'arial' , 'helvetica' , sans-serif;font-size:12pt;= color:#000000">

13th International = Conference on Formal Methods in Software Engineering

27 and 28 Apri= l, 2025

 co-located with ICSE 2025 (April 2= 7-May 3, 2025), Ottawa, Canada

https://conf.researchr.org/home/Form= alise-2025


Overview

Historically, formal methods academic research and practical software = development have had limited mutual interactions =E2=80=94 except possibly = in specialized domains such as safety-critical software. In recent times, t= he outlook has considerably improved: on the one hand, formal methods resea= rch has delivered more flexible techniques and tools that can support vario= us aspects of the software development process: from user requirements elic= itation, to design, implementation, verification and validation, as well as= the creation of documentation. On the other hand, software engineering has= developed a growing interest in rigorous techniques applied at scale.


The Forma= liSE conference series promotes work at the intersection of the formal meth= ods and software engineering communities, providing a venue to exchange ide= as, experiences, techniques, and results. We believe more collaboration bet= ween these two communities can be mutually beneficial by fostering the crea= tion of formal methods that are practically useful and by helping develop h= igher-quality software.


Originally a workshop event, since 2018 FormaliSE has bee= n organized as a conference co-located with ICSE. The 13th edition of Forma= liSE will also take place as a co-located conference of ICSE 2025.

Areas of inte= rest include but are not limited to:


  • requirements formalization and formal s= pecification;

  • approaches, methods and tools for veri= fication and validation;

  • formal approaches to safet= y and security related issues;

  • <= p dir=3D"ltr" style=3D"line-height:1.38;margin:0px">analysis of performan= ce and other non-functional properties based on formal approaches;
  • scalability of formal method applications

  • integration of formal methods within the software development lifecycl= e (e.g., change management, continuous integration, regression testing, and= deployment)

  • model-based engineering approaches;

  • correctness-by-construction approaches for software and= systems engineering;

  • application of formal methods = to specific domains, e.g., autonomous, cyber-physical, intelligent, and IoT= systems;

  • formal methods for AI-based systems (FM4= AI), and AI applied in formal method approaches (AI4FM);

  • formal methods in a certification context

  • case = studies developed/analyzed with formal approaches

  • ex= perience reports on the application of formal methods to real-world problem= s;

  • guidelines to use formal methods in practice;

  • usability of formal methods.


Important dates:

  • Abstracts= due: 18 November 2024 (AoE) - EXTENDED DEADLINE

  • Sub= missions: 25 November 2024 (AoE) - EXTENDED DEADLINE

  • <= span style=3D"font-size:11pt;font-family:'arial' , sans-serif;color:#000000= ;background-color:transparent;font-weight:400;font-style:normal;font-varian= t:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"= >Notifications: 13 January 2025

  • =

    Camera ready copies:= 5 February 2025

  • FormaliSE conference: 27-28 April 2= 025


Paper submission guidelines
We accept papers = in three categories:

    <= li dir=3D"ltr" style=3D"list-style-type:disc;font-size:11pt;font-family:'ar= ial' , sans-serif;color:#000000;background-color:transparent;font-weight:40= 0;font-style:normal;font-variant:normal;text-decoration:none;vertical-align= :baseline;white-space:pre">

    Full research papers describing original research work and = results. We encourage authors to include validation of their contributions = by means of a case study or experiments.  We also welcome research pap= ers focusing on tools and tool development.

  • Case stu= dy papers discussing a significant application that suggests gener= al lessons learned and motivates further research, or empirically validates= theoretical results (such as a technique's scalability).

  • Research ideas papers describing new ideas in preliminary fo= rm, in a way that can stimulate interesting discussions at the conference, = and suggest future work.


All papers submitted to the FormaliS= E 2025 conference must be written in English, must be unpublished original = work, and must not be under review or submitted elsewhere at the time of su= bmission. Submissions must comply with the FormaliSE's lightweight double-a= nonymous review process (see below).



To avoid that a= uthors waste time fitting their papers into the stated limit at the expense= of presentation clarity, paper lengths slightly exceeding the stated limit= will still be considered, provided that the reviewers find that the presen= tation is of high quality.

All submissions must be in PDF format = and must conform to the IEEE conference proceedings template, specified in = the IEEE Conference Proceedings Formatting Guidelines (i.e., title in 24pt = font and full text in 10pt type): https://www.ieee.org/conferences/publishi= ng/templates.html 

In LaTeX, use \documentclass[10pt,conference= ]{IEEEtran} without including the compsoc= or compsocconf options. 


To subm= it a paper to FormaliSE 2025 use thisHotCRP link: https://formal= ise25.hotcrp.com/

Lightweight Doub= le-Blind Review Process for Papers
As in recent e= ditions, FormaliSE 2025 will use a lightweight double-anonymous process. Au= thors must omit their names and institutions from the title page, cite thei= r own work in the third person, and omit acknowledgments that may reveal th= eir identity or affiliation. The purpose is reducing chances of reviewer bi= as influenced by the authors=E2=80=99 identities. The double-anonymous proc= ess is, however, lightweight, which means that it should not pose a heavy b= urden for authors, nor should make a paper's presentation weaker or more di= fficult to review. Also, advertising the paper as part of your usual resear= ch activities (for example, on your personal web-page, in a pre-print archi= ve, by email, in talks or discussions with colleagues) is permitted without= penalties.

Paper selection=
Each paper will be reviewed by at least three program c= ommittee members that will judge its overall quality in terms of its soundn= ess, significance, novelty, verifiability, and presentation clarity.=

FormaliSE 2025 will adopt a lightweight r= esponse process: if all the reviewers of a given paper agree that a clarifi= cation from the authors regarding a specific question could move the paper = from "borderline" to "accept", the chairs will relay the reviewers' questio= ns to the authors by email, and then share their reply with the reviewers i= n HotCRP. The goal of lightweight responses is reducing the chance of = random decisions on  borderline papers. Hence, they will only be used= for a minority of submissions; most papers will not require such an author= response. Nevertheless, we would ask the corresponding authors of all subm= issions to make sure that they are available to answer questions by email u= pon request.

Artifact Evaluation
Reproducibility of experimental results is crucial= to foster an atmosphere of trustworthy, open, and reusable research. To im= prove and reward reproducibility, FormaliSE 2025 continues its Artifact Eva= luation (AE) procedure. An artifact is any additional material (software, d= ata sets, machine-checkable proofs, etc.) that substantiates the claims mad= e in the paper and ideally makes them fully reproducible.

Submission of an artifact is optional but encouraged= for all papers where it can support the results presented in the paper. Ar= tifact review is single-anonymous (the paper corresponding to an artifact m= ust still follow the double-anonymous submissions requirements) and will be= conducted concurrently with the paper reviewing process. Artifacts will be= handled by a separate Artifact Evaluation Committee, and the Artifact Eval= uation process will be set up such that the anonymization of the correspond= ing papers will not be compromised. Accepted papers with a successfully eva= luated artefact will be awarded the [EAPLS badges (https://eapls.org/pages/artifact_badges/= ) that apply (among "Functional", "Reusable", and "Available"). Awarded= badges are to be added to the camera-ready version of the paper.

Artifacts will be assessed with respect to t= heir consistency with the results presented in the paper, their completenes= s, their documentation, and their ease of use. The Artifact Evaluation will= include an initial check for technical issues; authors of artifacts may be= contacted by email within the first two weeks after artifact submission to= help resolve any technical problems that prevent the evaluation of an arti= fact if necessary.

The results of a= n artifact evaluation will not be available to the reviewers of the corresp= onding paper; hence, they will not affect the paper's acceptance decision. = However, reviewers will know whether a paper has submitted *any* artifacts;= this piece of information may be taken into account to decide whether the = paper should be accepted. Thus, if there are justifiable reasons why a pape= r's artifacts cannot be submitted, they should be pointed out in the paper = so that the reviewers can appreciate them and adjust their expectations acc= ordingly.

Detailed guidelines for p= reparation and submission of artifacts will be described in a dedicated pag= e inFormaliSE 2025's website.

Publication
All accepted papers are publ= ished as part of the ICSE 2025 Proceedings in the ACM and IEEE Digital Libr= aries.

At least one author of each = accepted paper is required to register for the conference and present the p= aper at the conference =E2=80=94 physically or, if the circumstances do not= allow so, virtually. Failure to register an author will result in a paper = being removed from the proceedings.

General Chairs

  • Stefania Gnesi, Istituto di Scie= nza e Tecnologie dell=E2=80=99Informazione, Italy

  • Ni= co Plat, Thanos, The Netherlands


Program Chairs

  • Anastasia Mavridou, KBR / NASA Ames Rese= arch Center, USA

  • Gwen Sala=C3=BCn, University Grenob= le Alpes, France


Artifact Evaluation Chairs

  • =C3=81kos Hajdu, Meta, UK

  • <= span style=3D"font-size:11pt;font-family:'arial' , sans-serif;color:#000000= ;background-color:transparent;font-weight:400;font-style:normal;font-varian= t:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"= >Lina Marsso, University of Toronto, Canada


Social Media Chair

  • Quentin Nivon, University Gre= noble Alpes, France


Program committee

  • Bernhard Aichernig, TU Graz, Austria

  • Toshiaki Aoki, Japan Advanced Institute of Science and Technology, Ja= pan 

  • Kyungmin Bae, Pohang University of Scien= ce and Technology, Korea 

  • <= p dir=3D"ltr" style=3D"line-height:1.38;margin:0px">Domenico Bianculli, U= niversity of Luxembourg, Luxembourg 

  • Simon Bli= udze, INRIA Lille - Nord Europe, France

  • Giovanna Bro= ccia, ISTI - CNR, Italy

  • Radu Calinescu, University= of York, UK 

  • Pablo Castro, National University= of Rio Cuarto, Argentina 

  • =

    Zhenbang Chen, NUDT,= China

  • Nancy Day, University of Waterloo, Canada

  • Francisco Dur=C3=A1n, University of M=C3=A1laga, Spain<= /span>

  • Marie Farrell, University of Manchester, UK 

  • Carlo A. Furia, USI Lugano, Switzerland  &nb= sp;

  • Fatemeh Ghassemi, University of Tehran, Iran&nbs= p;

  • Divya Gopinath, KBR/ NASA Ames Research Center, U= SA 

  • Yann-Ga=C3=ABl Gu=C3=A9h=C3=A9neuc, Concord= ia University, Canada

  • Paula Herber, University of M= =C3=BCnster, Germany 

  • Marieke Huisman, Universi= ty of Twente, The Netherlands 

  • Fuyuki Ishikawa,= National Institute of Informatics, Japan 

  • Xiao= qing Jin, Apple Inc., USA

  • Violet Ka I Pun, Western N= orway University of Applied Sciences, Norway

  • Oleksan= dr Kolchyn, Glushkov Institute of Cybernetics, Ukraine 

  • Ant=C3=B3nia Lopes, University of Lisbon, Portugal 

  • Larissa Meinicke, University of Queensland, Australia 

  • Camilo Rocha, Pontificia Universidad Javeriana, Colom= bia

  • Cristina Seceleanu, M=C3=A4lardalen University, = Sweden 

  • Arpit Sharma, EECS Department, IISER Bh= opal, India 

  • Allison Sullivan, University of Te= xas, Arlington, USA

  • Heike Wehrheim, University of Ol= denburg, Germany 


--=_2b2e7be4-eebb-434f-9e47-ec3e3aace711--