HTML Presentation of Style Sheet For SEN

Fairly similar to the real thing!

SEN Paper Title is Arial Bold 14 centered. It is style "Title"

SEN Paper author name(s) are Arial 12 centered, style "Author"

Author affiliation is style "Author" (be concise)

<You must include your email address too but it is 10pt>


This note explains and illustrates the style guidelines for articles to be published in Software Engineering Notes. These guidelines deal mostly with production layout and are focused on achieving some reasonable sort of uniformity across submissions.

Content, of course, is important. We encourage authors to write in the active voice, using short clear sentences. We believe all con-tributions (in general) should include the following sections:

  1. Introduction (which includes:
    • a brief description of the problem this paper is addressing,
    • a summary of the contribution of the paper, and
    • an outline of how the paper is organized.
  2. A comparison to previous work
  3. An example, or description of how these ideas have been used (obviously not applicable to all papers).

We will evaluate all submissions with these guidelines in mind.


SEN, author guidelines, Word

Document Format

Please use the following formats for your article:

  1. File/Page Setup… paper size is letter (not A4).
  2. File/Page Setup… margins are top: 0.75 inches, bottom: 0.562, left: 0.5, and right: 0.4
  3. Format/Columns… use two-column format with equal column width at 3.73 and spacing of 0.13 Format Columns menu.
  4. Please do not use headers and footers. The editor will add these.
  5. Use footnotes, not endnotes. All footnotes should be numbered to begin with 1 at the start of a section.
  6. The document should noot use any macros, as they will not be executed (for security and virus protection)

Styles To Use

Please use Styles in Word to control your document. Using the Word Style mechanism lets us get a consistent look and feel to the magazine with the least changes to your article, and that makes it less likely we'll introduce errors. Do not format your article using spaces, tabs, or blank paragraphs to get the spacing you want. Please format the paper using the styles we provide rather than creating your own styles wherever possible; and, ignore the Word built-in styles (such as Heading 1, Heading 2, and Heading 3).

SEN defines these styles in Word:

  • Title
  • Author
  • Text
  • Section header
  • sub-heading
  • sub-heading (level 2)
  • list
  • figure label
  • code

Section, subsection and second-level section headings all are sen-tence-capitalized. They may be numbered if you like; but be con-sistent throughout the article. (Exception: do not number the Abstract or References section headings.)

Section text is Times New Roman 10 and is style "text." Text is in two columns, right justified and hyphenated. Sentences are sepa-rated by one space after the period.

The 'text' style and others use paragraph formatting for space-before and space-after to allow the editor control over paragraph packing; therefore, please do not use blank paragraphs to space text elements. Also, do not indent the first line of the paragraphs, with style overrides, tabs, or spaces; this will be adjusted during production layout according to the magazine style guidelines

Subsection Heading. This is Arial 10 Italic

The style for the subsection header is "sub-heading"

Second-level subsection heading. Times New Roman 10 Bold.

The style for the second-level subsection is "sub-heading level 2".


List items get the "list" style, which is bulleted with no indent. You may change the bullets to numbers if you want (or apply the list-numbered style). List items have the bullet/number to indicate item start, so they get a paragraph space-following of 0 pt. The last item in a list gets a space-following paragraph format of 6 pt. If you must se a sub-list, use outline numbering or changing bullet styles to indicate the list levels

Figures, Tables , Pictures, and Images

Whenever possible, please choose a format which Word will use, such as a picture (using Insert picture), table, an object, equation object, text object, or image. This lets us manipulate the objects easily during page layout, if needed. Note: in order to save space, text in art and tables may be formatted using 8 point fonts.

Page 2...

Art Drawing Tools

When creating line or screen art, avoid using the Microsoft Draw tool directly in Word. The Word drawing tools draw directly on the page, and so if the text shifts the art created directly in Word will no longer be in the location you planned. Instead, create your art in a drawing tool and import it into Word rather. Be ready to supply the art as separate files in a widely supported format.


The name/caption of the figure/table appears beneath the fig-ure/table, capitalized like a sentence. The caption is in "figure label" style. We will ensure the caption does not move to a different column from the figure, and you may apply "keep with next" paragraph style to the paragraph marker for the art. Use the captions to amplify or summarize the art, not just label it; for example, "Example of proposed coding styles" is weaker than "Proposed style is easier to follow." Figure 1 shows our approach.

Controlling art placement

Art (figures, tables, etc.) can be pasted in-line and will then stay in-line with the text. However, if the art is too tall for the remaining column space, or needs to span columns due to its width, this won't work well. In these cases, enclose the art and the caption together in a frame or a text box. (Text boxes are available only in recent editions of Word; frames are available in older version and must be used even in newer versions to enclose some elements.)

If you don't frame the art we will try to keep it as you placed it. But, this may end up with the art at the top of the next column or some other place.

If you use the framing technique in some versions of Word, the text will often want to flow under the art (which is confusing!). To fix this with a Frame, set the wrapping to None (right click on the Frame Autoshape border); with a Text box, set the wrapping to Top&Bottom. Set the caption inside the Frame or Text Box to en-sure they move together - see Figure 1 for an example of this ap-proach. Because the text flows independently of the art you should avoid using "below" and "above" when referring to art; just use "as in Figure 1" rather than "as in Figure 1, below."

When saving a text box element to Word 6.0/95 format, Word de-faults Wrapping setting to None and on a subsequent document load, the None setting takes effect. When this setting is None, the

text flows behind the art and it looks like you're losing text, and the frame positioning will change. If this happens, check that the Wrapping setting is what you expect.


It is acceptable to use partial-column art and allow the text to wrap to it (using a Tight or Square Wrapping setting) as is done with Table 1.

Code and Pseudo-code

Code is formatted with the "code" style: monospaced 9 pt, non-hyphenated, with a tab every 0.33". Use the tabs to indent blocks of code. Use paragraph keep-with -next formatting to keep to-gether code lines that shouldn't be separated.

program A
// a sample program
   while (!halted)

Definitions and Equations

Indicate the start of a definition with Definition and a number (if appropriate); indicate equation numbering with an equation number in parentheses, right-justified:

Definition 3. The total effort F(y)is the sum of the partial efforts yk:



Please spell check your papers before submitting them. The editor will accept papers using American or British English spellings (organization or organisation).


If your paper is copyrighted please acquire permission to reprint the paper. The permission to reprint should be submitted on a separate sheet. The SEN Editor will format it in the document.


A reference should cited in the text using a number [1], and should follow the ACM format as shown in the example [1]. URLs can be included as citations as well. To save space, references may be formatted in 8 point size

[1] Divitini, M., G. Omodei Salé, A. Pozzoli, and C. Simone (1993): Supporting the Dynamics of Knowledge Sharing within Organizations. In COOCS'93- Conference on Organizational Computing Systems, Milpitas, CA, November 1-4, 1993, ed. S. Kaplan. ACM Press, pp. 178-183.