IEEE Transactions on Software Engineering paper format
- Length limit
- See author guide
- Layout
- Two-column
- Abstract
- 100–200 words
- References
- Numbered
- Citation style
- ieee
- LaTeX class
- IEEEtran
Regular paper (IEEE Computer Society journal rules)
Length guidance checked 2026-10-27.
Page length and reference limits vary by journal and all include abstracts, references and author biographies (this journal's own page limit is not recorded here). Regular-paper abstract 100 to 200 words, with no mathematical expressions or references.
Template sections
- Abstract
- Introduction
- Related Work
- Methodology
- Experiments
- Conclusion
- References
Camera-ready back matter: Acknowledgments.
Labrix formats references for this venue in its ieee style by default; any of 10,000+ CSL styles can be selected instead.
Questions
How long is the abstract for IEEE Transactions on Software Engineering?
IEEE Transactions on Software Engineering abstract guidance: 100–200 words.
Which citation style does IEEE Transactions on Software Engineering use?
Labrix formats IEEE Transactions on Software Engineering references in the ieee style by default.
Which LaTeX class does IEEE Transactions on Software Engineering use?
Labrix's IEEE Transactions on Software Engineering template starts from \documentclass[conference]{IEEEtran}.
Which sections does a IEEE Transactions on Software Engineering manuscript need?
Labrix's IEEE Transactions on Software Engineering template includes these sections: Abstract, Introduction, Related Work, Methodology, Experiments, Conclusion, References.
Does IEEE Transactions on Software Engineering require a limitations section?
Labrix's IEEE Transactions on Software Engineering spec does not list a limitations section as required.
Does IEEE Transactions on Software Engineering require an ethics or broader-impact statement?
Labrix's IEEE Transactions on Software Engineering spec does not list an ethics or broader-impact statement as required.