Editorial: Journal-First Publication for the Software Engineering Community

Matthew B. Dwyer, David S. RosenblumIEEE Transactions on Software Engineering 2016 · DOI · OpenAlex

Abstract

This editorial introduces a new publication model for the software engineering community: the "journal-first" initiative. Launched by the editors of IEEE Transactions on Software Engineering (TSE) and ACM Transactions on Software Engineering and Methodology (TOSEM), this model allows researchers to publish original, in-depth work in journals while retaining the opportunity to present their findings at premier conferences like ICSE and ESEC/FSE.

Introduction: The Publication Dilemma

In the software engineering research community, authors have traditionally faced a binary choice. Conferences offer high visibility, immediate feedback, and networking opportunities, but they are constrained by strict page limits and rigid annual deadlines. Conversely, journals allow for greater depth, comprehensive proofs, and iterative revision cycles, yet they often lack the "big stage" impact of a conference presentation.

Historically, journals were often seen as a secondary venue for "extended versions" of conference papers. This editorial addresses the need for a "journal-first" route—a model already successful in fields like database systems—where entirely new research is published in a journal first and subsequently shared with the community through conference presentations.

The Journal-First Model

To bridge the gap between archival depth and community engagement, TSE and TOSEM have established a dedicated "Journal-First" submission category. This initiative is governed by several key policy pillars:

  • Strict Novelty Criteria: To qualify for this category, manuscripts must report entirely new contributions. They cannot be extensions of previously published conference papers (e.g., adding more data or proofs to an existing study). If a submission is found to build significantly on prior work without meeting the "journal-first" novelty bar, it is redirected to standard journal categories.
  • Rigorous Peer Review: These submissions undergo the same high-quality, multi-round peer review process as any other article in these flagship journals.
  • Conference Integration: Once a journal-first paper is accepted, the journals actively promote it to conference organizers. For a period of two years following publication, these papers are eligible for inclusion in the technical research tracks of major IEEE and ACM-sponsored conferences, such as the International Conference on Software Engineering (ICSE) and the ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE).

Strategic Insights

The core philosophy of this initiative is the decoupling of publication from presentation. By separating the medium of publication (the journal) from the act of presentation (the conference), the editors aim to create a more flexible research ecosystem.

This shift prioritizes quality over constraints. By removing the pressure of fixed deadlines and page limits, researchers are encouraged to produce more comprehensive and polished contributions that might otherwise have been truncated to fit conference requirements. This creates a mutually beneficial relationship: conferences gain access to a pool of pre-vetted, high-quality research, while authors enjoy the archival permanence of a journal alongside the networking benefits of a conference.

Pilot Results and Future Directions

The viability of this model was demonstrated through a successful pilot program coordinated with ICSE 2015 and ESEC/FSE 2015. During this pilot, seven papers identified as "journal-first" were successfully presented at these major venues, confirming that the community is receptive to this integrated approach.

Despite its success, the editors acknowledge certain limitations. Because conference organizing committees are independent of journal editorial boards, there is no absolute guarantee that a journal-first paper will be invited to a conference. Similarly, authors are not required to accept an invitation to present.

The initiative represents a significant step in maturing the software engineering publication landscape. The long-term goal is to establish stable, institutionalized relationships between journals and conferences, ensuring a steady and prestigious outlet for journal-first results. Ultimately, the success of this model rests on the community’s ability to distinguish and value the specific novelty required for this category.

Summary updated

Abstract

Presents the introductory editorial for this issue of the publication.
BibTeX
@article{dwyer2016editorial,
  author = {Matthew B. Dwyer and David S. Rosenblum},
  title = {{Editorial: Journal-First Publication for the Software Engineering Community}},
  journal = {IEEE Transactions on Software Engineering},
  year = {2016},
  doi = {10.1109/tse.2015.2500318},
}

Loading related content...

Figure