Call for papers

Advancing Technical Credit as a first-class software engineering concept.

Technical Credit describes the long-term engineering value created by deliberate architectural and development decisions aligned with anticipated business needs. Examples include modular designs, explicit design rationale, robust automation pipelines, stable APIs, and other investments that make future system evolution less costly and less risky.

IWTC 2027 invites researchers and practitioners to share perspectives, discuss early empirical findings, explore ways to measure and operationalize Technical Credit, and examine tooling strategies for its creation, visibility, tracking, and recognition.

We welcome contributions from software architecture, architecture knowledge management, requirements engineering, software metrics, empirical software engineering, technical debt, AI for software engineering, and related communities.

Topics of interest

Three research dimensions, connected to software architecture practice.

Measurement

Make Technical Credit observable.

Contributions may investigate indicators that capture the presence and value of Technical Credit, including whether existing software quality metrics can be reused or adapted.

  • Indicators for modularity, extensibility, evolvability, and business alignment.
  • Qualitative and quantitative approaches for assessing credit-generating decisions.
  • New measurement models for long-term engineering value.
Tooling

Embed Technical Credit into everyday workflows.

Contributions may explore lightweight tool support that makes Technical Credit visible where architectural and engineering decisions are made and validated.

  • Support in Architecture Decision Records, pull requests, and CI/CD pipelines.
  • Annotation schemes, prompts, signals, and stakeholder-facing visualizations.
  • AI coding agents for creating, identifying, tracking, and quantifying Technical Credit.
Evidence

Understand how Technical Credit appears in practice.

Contributions may study how teams recognize, enact, communicate, protect, or lose Technical Credit across organizational and business contexts.

  • Empirical studies of Technical Credit in industrial settings.
  • Adoption enablers, barriers, incentives, and communication patterns.
  • Connections with architectural governance, technical debt management, and sustainability.
Architecture

Connect the concept to ICSA themes.

Contributions may connect Technical Credit to novel software architecture research, AI for software architecture, and socio-technical architecture and governance.

Submission and author instructions

Position papers and active workshop participation.

The workshop proposal plans for approximately 10 to 15 position papers of up to four pages, aligned with the Technical Credit themes and the workshop goal of building a shared research agenda.

Accepted papers are expected to contribute to the workshop discussion, not only to present finished results.

Paper type

Position papers of up to four pages.

Formatting

Submissions must follow the IEEE conference proceedings format and abide by the single-anonymous submission process.

Originality

All submissions must be original work and must not have been previously published, nor be under consideration for publication elsewhere.

Submission site

All contributions should be submitted before the submission deadline using ICSA's EasyChair online submission site.

Review process

Each submission will be reviewed by two experienced reviewers.

Presentation format

Accepted authors will prepare 2 to 3 slides and present the core idea in a two-minute lightning talk.

Workshop format

Authors will take part in breakout groups and plenary discussion aimed at shaping a community roadmap.

Registration

At least one author of each accepted paper must register and present at the workshop.

Important dates

Submission timeline.

To be defined

Abstract submission

To be defined.

To be defined

Paper submission

To be defined.

To be defined

Notification

To be defined.

To be defined

Camera ready

To be defined.

To be defined

Workshop date

To be defined.

Program committee

Program committee.

To be defined

Program committee

To be defined.

Organizers

The workshop organizing team.

Alessio Bucaioni
Associate Professor of Computer Science, Mälardalen University

Alessio Bucaioni

Workshop organizer and co-author of the initial Technical Credit publications.

Ian Gorton
Professor of the Practice and Director of Mobility Programs, Khoury College of Computer Sciences, Northeastern University

Ian Gorton

Workshop organizer and co-author of the initial Technical Credit publications.

Patrizio Pelliccione
Professor in Software Engineering and Computer Science, Gran Sasso Science Institute; Adjunct Professor, University of Bergen

Patrizio Pelliccione

Workshop organizer and co-author of the initial Technical Credit publications.