This page gives an overview of the submission and publication guidelines. Please also refer to the full SEN Publication Terms and Conditions.
SEN submissions are now being accepted at http://sen.sigsoft.org/.
Material for publication in Software Engineering Notes (SEN) should be submitted via http://sen.sigsoft.org/.
The site allows submission of articles, reports, reviews, columns, announcements and book reviews.
Under the rubric 'articles' the submission of scientific/research articles is restricted to articles that are part of a workshop for which SEN has agreed to be the publisher. Other scientific/research articles, i.e., articles that are sent unsolicited and could have been submitted to a regular journal or workshop for review will no longer be published in SEN.
Under the rubric 'column', we welcome contributions that discuss topics of interest among SIGSOFT members and the software engineering community at large. Columns should normally not be longer than 4 pages (exceptions may be allowed on a case-by-case basis) and trigger further discussion among community members.
Under the rubric 'reports' we welcome summary reports from workshops conducted under the umbrella of ICSE, ASE, ESEC/FSE and other major SIGSOFT sponsored conferences.
Any common file format is allowed.
The following templates are available:
CFPs and Advanced Programs for SIGSoft-sponsored or in-cooperation events may be submitted as .pdf files with all fonts embedded.
Because only the abstracts of papers and reports will appear in the print issue of SEN, authors should review their abstract to make sure it reflects the key points addressed in the document, which will appear in full in the ACM Digital Library.
By submitting your article for distribution in this Special Interest Group publication, you hereby grant to ACM the following non-exclusive, perpetual, worldwide rights:
However, as a contributing author, you retain copyright to your article and ACM will make every effort to refer requests for commercial use directly to you.
Letters, abstracts, book reviews, specialized bibliographies, notices, news reports, etc., are all welcome. All contributions are considered personal rather than organizational; technical contributions are considered as unrefereed working papers. Controversy is encouraged, but personal attacks are not.
Please see the ACM webpage about plagiarism and self-plagiarism.
Plagiarism is copying words from another published paper (your own or someone else's) without proper quotes and citations. In writing, everything not quoted and cited is presumed to be new work by the author. Plagiarism disrespects both the original author (whose contributions are not acknowledged) and the reader (who is mislead about the contributions of the current paper, and will not know where to go when they want to learn more). It looks like theft of words or ideas.
Most reasons to copy text boil down to laziness. The words are already there, so copying may seem like a shortcut for anyone who is in a hurry and can't or won't put in the effort to create new words and ideas. Everyone who struggles to express themselves clearly may thinks that copying is a shortcut. As a rule, plagiarism indicates mediocre efforts and results.
So, let's go back to the real reasons for writing a technical paper. Research and technical writing are about creating and expressing new ideas. Copying repeats old ideas, which is the opposite of creativity and innovation. If something has already been published, then simply reference it and move on.
You should copy when you want to comment on another author's words, for example to agree or disagree, or to show that you admire a piece of text. In these cases, the new information is why you are copying and the original and new text should be clear. In the following two examples, the original authors can speak for themselves, and by using quotes, the reader knows which ideas are mine and which are not.
Any copied text longer than a few words should be put in quotes and given a reference. If you copy more than a full sentence, use indented paragraphs to denote a block quote. Note that copying text and then changing words here and there is not good enough. Use quotes or rewrite completely.
There are many places where copying is fine. Nobody worries about two or three words. Nobody worries about facts that are commonly known. "The U.N. is headquartered in New York." This sentence is true, and there are not very many ways to write it. And of course, there are occasional coincidences. Beyond that, do not copy text.
Plagiarism is not a game. More than one person has written a paper and then tried to republish it a second time. That is a waste of time and effort for the editors and readers. Journals are filled with papers that nobody will ever read and plagiarism just makes this situation worse. Just move on and write something new.
SEN appears quarterly (four issues a year). Please check with the editor for details on conference issues if you have a concern about the timeliness of a CFP or other contribution appearing in SEN.
Submission deadlines are 7 weeks before publication date or roughly:
Note: SEN is transitioning to an all-electronic production process. It is anticipated that the production schedule may shorten to 4 weeks, in which case, the production schedule may allow additional time for late submissions. Please check with the editor if there are any questions on meeting the submission deadline.