home Co-Located with:ICSE27
date Date: April 27, 2027 (tentative)
date Location: Dublin (Ireland)
registration Submission: November 13, 2026

Scope

The engineering of green software-intensive systems is critical in our drive towards a sustainable, smarter planet. The goal of green software engineering is to apply green principles to the design and operation of software-intensive systems. Green and self-greening software systems have tremendous potential to decrease energy consumption. Moreover, software can and should be re-thought to address sustainability issues using innovative business models, processes, and incentives. Monitoring and measuring the greenness of software is critical towards the notion of sustainable and green software. Demonstrating improvement is paramount for users to achieve and effect change. Analysis of the sustainability of a specific software system requires software that aids developers in weighing the four dimensions of sustainability---economic, social, environmental, and technical---with their attendant trade-offs. The software engineering community must assume leadership in this important challenge. In this workshop, we will explore the theme of “green software engineering for software sustainability” with a goal towards creating actionable outcomes that will affect how software engineering is practiced and taught in the future, in order to help organizations prioritize their sustainability objectives.

Topics

GREENS 2027 seeks contributions addressing, but not limited to, the following topics related to sustainable software systems and green software engineering:

  • Energy-efficient choices for architecture and design patterns, algorithms, data structures, programming languages, language runtime and infrastructure.
  • Architectural implications (architectural tactics, architectural styles, design patterns and anti-patterns) for green and sustainable software
  • Practices for sustainability-aware software engineering
  • Metrics and measures for sustainability-aware software engineering
  • Sustainability-aware architectures in context (e.g., cloud-edge continuum)
  • Teaching and training of skills and competencies in sustainability-aware software engineering
  • Sustainable computing from a software engineering and software-intensive system perspective
  • Applied, or experimented with, software engineering methodologies at all levels (from requirements elicitation to architecture design, coding, testing, and maintenance)
  • Meta-analyses, and syntheses of studies to build theories on green and sustainable software; conceptual reflections related to software sustainability
  • Progress on the various dimensions of software sustainability and their interplay
  • Software adaptation for sustainability
  • Tools to support sustainability-aware decision-making
  • Sustainability of emerging computing technologies (AI systems, edge devices, generative AI-enabled applications)
  • Green AI, lighter, less data-intensive, and less energy-consuming AI models and architectures
  • Sustainable Large Language Models (LLMs) for software code
  • Green Agentic AI
  • Reduction of software organizations’ compute-heavy workloads
  • Cloud and energy efficiency
  • Standards on the environmental sustainability of software and AI software

Important Dates

  • Paper Submission: November 13, 2026
  • Notification: December 11, 2026
  • Camera-Ready: January 29, 2027
  • Workshop Date: April 27, 2027

Submission Types

Participants are invited to submit four types of contributions:

  • Emerging research papers (up to 8 pages): Contributions offering novel research results, addressing challenging real-world problems with innovative ideas. Submissions should clearly describe the challenges and problems tackled, the relevant state of the art, the solution being offered, and the potential benefits of the contribution, from an academic or industrial perspective.
  • Position papers (up to 5 pages): Contributions outlining forward-looking ideas or thought-provoking reflections that call for further discussion and research in the community. These describe a specific position or opinion of the authors or provide a well-reasoned and motivated vision.
  • Extended abstracts (up to 2 pages): These abstracts propose novel research topics for discussion in the community, addressing challenging problems from an academic or industrial perspective. The motivation for the topic is grounded in the literature or practical experience.
  • Registered reports (6 pages + 2 pages for references): Detailed study designs submitted for feedback before study execution, with a clear path toward a full paper in ACM TOSEM. See details below.

Submission Guidelines

All papers must be submitted electronically via the HotCRP submission system by the submission deadline and must not have been published before or be submitted for review elsewhere while under consideration at GREENS.

The paper format of the Workshop's papers must follow the IEEE formatting guidelines . LaTeX users must use \documentclass[10pt,conference]{IEEEtran} without including the compsoc or compsocconf options. Submissions must strictly conform to the IEEE formatting instructions specified above. Alterations of spacing, font size, and other changes that deviate from the instructions may result in desk rejection without further review.

All papers will go through a single-anonymous submission process, i.e., authors' names, institutions, and contact details should appear on the first page.

Submissions will be reviewed on the basis of technical quality, relevance, significance, and clarity by the program committee members. The workshop proceedings will be published in ICSE 2027 Companion proceedings.

Registered Reports & Expected Timeline

A registered report (RR) focuses on the significance of the research question and the quality of the planned study design before the study is executed. For GREENS, an RR can be understood as a full research paper without the Results and Discussion sections (stage-1 publication).

RRs are intended to support early feedback on the study design, reduce risks such as outcome-driven reporting or bias against negative results, and provide a structured path toward a full journal paper after study execution (stage-2 publication). They are especially suitable for confirmatory and quantitative studies, but exploratory or qualitative studies can also be submitted when the study design is clear and reviewable.

For a more detailed introduction to registered reports in software engineering, see Ernst and Baldassarre (2023) . For details on how ACM TOSEM handles RRs, please refer to the ACM TOSEM Registered Report Track .

RRs at a Glance

  • Stage-1 submission: Detailed study design (full paper without Results and Discussion sections)
  • Page limit: 6 pages + 2 pages for references
  • GREENS outcome: Reject, accept with revisions, or accept as is
  • Publication: Accepted stage-1 submissions will appear in the ICSE 2027 Companion proceedings
  • Post-workshop path: Revised stage-1 submission to the ACM TOSEM Registered Report Track, followed by study execution and stage-2 submission

The detailed GREENS 2027 RR process is as follows:

  1. GREENS solicits RR stage-1 submissions, i.e., study design descriptions (deadline: see above).
  2. GREENS reviewers who agree to review RR submissions also agree to review the stage-2 submissions at TOSEM later on, i.e., the full papers written after study execution.
  3. Each RR stage-1 submission at GREENS receives one of three outcomes: reject, accept with revisions, or accept as is (notification: see above).
  4. Accepted RR stage-1 submissions are published in the ICSE Companion proceedings (camera-ready deadline: see above).
  5. At the GREENS workshop, accepted RR stage-1 submissions are presented and discussed, with the goal of further improving the planned study.
  6. Authors revise the RR stage-1 paper after the workshop and submit it to the ACM TOSEM RR Track (deadline: approximately 4 weeks after the workshop).
  7. Reviewer contact details for each accepted RR submission are forwarded to TOSEM.
  8. TOSEM invites the reviewers. If no changes were requested, they greenlight the submission; otherwise, reviewers check the updates. The stage-1 submission is not published again at TOSEM.
  9. Once the RR stage-1 submission is accepted at TOSEM, it forms an agreement: if the authors follow the approved study design and reasonably explain any deviations, the final paper can be accepted regardless of whether the results are positive, negative, or inconclusive.
  10. Authors execute the study and extend the stage-1 submission with the results and discussion into a full research paper (stage-2 submission).
  11. Authors submit the stage-2 submission to TOSEM. The same reviewers are invited. It is treated internally as a major revision (deadline: approximately 10 weeks after the stage-1 RR acceptance; extension upon request to TOSEM).
  12. Stage-2 reviews focus on whether the approved study design was followed, whether deviations are justified, and whether the final paper clearly presents and discusses the results. A rejection will only be used if the authors deviated strongly from their initial study design without reasonable justifications.

Organizing Committee

Steering Committee:

Workshop Chairs:

Web Chair:

Program Committee (Tentative)

  • Vasilios Andrikopoulos – University of Groningen, Netherlands
  • Pablo Antonino – Fraunhofer Institute for Experimental Software Engineering (IESE), Germany
  • Stefanie Betz – Furtwangen University & LUT University, Germany/Finland
  • Coral Calero – University of Castilla-La Mancha, Spain
  • Rafael Capilla – Rey Juan Carlos University, Spain
  • Ruzanna Chitchyan – School of Computer Science, University of Bristol, United Kingdom
  • Shaiful Chowdhury – University of Manitoba, Canada
  • Luiz Cruz – Delft University of Technology, Netherlands
  • João Paulo Fernandes – New York University Abu Dhabi, United Arab Emirates
  • Alcides Fonseca – Large-Scale Informatics Systems Laboratory (LASIGE), University of Lisbon, Portugal
  • Geerd-Dietger Hoffmann – Green Coding Solutions, Germany
  • Tamar Eilam – IBM Research, USA
  • Max Hort – Simula Research Laboratory, Norway
  • Maria Kechagia – National and Kapodistrian University of Athens, Greece
  • Maja Kirkeby – Roskilde University, Denmark
  • Olivier Le Goaër – University of Pau, France
  • Grace Lewis – Carnegie Mellon University, Software Engineering Institute (SEI), USA
  • Silverio Martínez-Fernández – Polytechnic University of Catalonia (Universitat Politècnica de Catalunya - BarcelonaTech), Spain
  • Marco Miozzo – Centre Tecnològic de Telecomunicacions de Catalunya, Spain
  • Henry Muccini – University of L'Aquila, Italy
  • Stefan Naumann – Trier University of Applied Sciences, Germany
  • Adel Noureddine – University Paris Nanterre, France
  • Wellington de Oliveira Junior – Universidade Lusófona, Portugal
  • Fabio Palomba – University of Salerno, Italy
  • Pooja Rani – University of Zurich, Switzerland
  • June Sallou – Wageningen University & Research, Netherlands
  • João Saraiva – University of Minho, Portugal
  • Tushar Sharma – Dalhousie University, Canada
  • Jieke Shi – Singapore Management University, Singapore
  • Maria Spichkova – Royal Melbourne Institute of Technology (RMIT University), Australia
  • Roberto Verdecchia – University of Florence, Italy