Bulletin of the Novosibirsk computing center:
Authors’ instructions
Irina Adrianova, Olga Drobyshevich
Abstract. The abstract should be set in 9-point font size. There should be two blank (10-point) lines before and after the abstract. This document is in the required format.
Keywords: authors’ instructions, formatting
Introduction
This instruction file for Word users may be used as a template. You should make sure that the Word and the PDF files are identical and correct.
1.   Paper preparation
The printing area is 125 mm × 196 mm. The text should be justified to occupy the full line width, so that the right margin is not ragged, with words hyphenated as appropriate. Please fill pages so that the length of the text is no less than 180 mm, if possible. 
Use 10-point type for the name(s) of the author(s) and 9-point type for the abstract and keywords. For the main text, please use 10-point type and single-line spacing. We recommend the use of Times. Italic type may be used to emphasize words in running text. Bold type and underlining should be avoided. 
Headings. Headings should not be capitalized and should, with the exception of the title, be aligned to the left. The font sizes are given in Table 1.  
Table 1.  Font sizes of headings. Table captions should always be positioned above the tables
Heading level	Example	Font size and style	
Title (centered)	Bulletin of NCC …	14 point, bold	
1st-level heading	1. Paper preparation	12 point, bold	
2nd-level heading	1.1. Figures	10 point, bold	
3rd-level heading	Headings.  Text follows …	10 point, bold	
4th-level heading	Remark.  Text follows …	10 point, italic	
Lemmas, Propositions, and Theorems. The numbers accorded to lemmas, propositions, and theorems, etc. should appear in consecutive order, starting with Lemma 1, and not, for example, with Lemma 11. 
1.1.   Figures 
Please check that the lines in line drawings are not interrupted and have a constant width. Grids and details within the figures must be clearly legible and may not be written one on top of the other. Line drawings should have a resolution of at least 800 dpi (preferably 1200 dpi). The lettering in figures should have a height of 2 mm (10-point type).  Figures should be numbered and should have a caption which should always be positioned under the figures, in contrast to the caption belonging to a table, which should always appear above the table. Please center the captions between the margins and set them in 9-point type (Figure 1 shows an example). The distance between text and figure should be about 18 pt, the distance between figure and caption about 12 pt. 
To ensure that the reproduction of your illustrations is of a reasonable quality, we advise against the use of shading. The contrast should be as pronounced as possible. 

Figure 1. Planarity rule
1.2.   Formulas
Displayed equations or formulas are centered and set on a separate line (with an extra line or halfline space above and below). Displayed expressions should be numbered for reference. 
x + y = z .	(1)	

Please punctuate a displayed equation in the same way as ordinary text but with a small space before the end punctuation. 
1.3.   Footnotes
The superscript numeral used to refer to a footnote appears in the text directly after the word to be discussed. Footnotes should appear at the bottom of the normal text area, with a line of about 5cm set immediately above them. 
1.4.   Citations
The list of references is headed “References” and is not assigned a number. The list should be set in small print and placed at the end of your contribution, in front of the appendix, if one exists. An example is given at the end of this information sheet. For citations in the text please use square brackets and consecutive numbers: [1], [2], [3], etc.

Acknowledgments. The heading should be treated as a 3rd level heading and should not be assigned a number.
References
1. Anureev I.S. Operational ontological approach to formal programming language specification // Programming and Computer Software. – 2009. – Vol. 35, No. 1. – P. 35–42.
2. Anureev I.S. Operational semantics development for procedural programming languages based on conceptual transition systems // Bulletin NCC. Series: Computer Science. – 2015. – Vol. 38. – P. 1–28.
3. Gurevich Y. Abstract state machines: an overview of the project. foundations of information and knowledge systems (FoIKS) //  Lect. Notes Comput. Sci. – 2004. – Vol. 2942. – P. 6–13.
4. Parnas D.L. Really rethinking formal methods // Computer. IEEE Computer Society. – 2010. –Vol. 43, No. 1. – P. 28–34.