Professional Documents
Culture Documents
Author Guidelines: Contain Original Work
Author Guidelines: Contain Original Work
It is essential for us that authors write and prepare their manuscripts according to
the instructions and specifications listed below. The length and effectiveness of the
peer review process will largely depend upon the care used by authors in preparing
their manuscripts. Therefore, contributors are strongly encouraged to read these
instructions carefully before preparing a manuscript for submission, and to check
the manuscript for conformance before submitting it for publication.
Manuscripts preferred for publication in IJEAL are those which:
1. Contain original work – which is not published elsewhere in any medium by the
authors or anyone else and is not under consideration for publication in any other
medium.
2. Are focused on the core aims and scope of the journal – IJEAL is an
interdisciplinary peer reviewed journal that seeks both theoretically and practically
oriented research papers from the area of organizational science, business
information systems and human resources management.
3. Are clearly and correctly written – should contain all essential features of a
complete scientific paper, should be written in a clear, easy to understand manner
and be readable for a wide audience.
4. Are written in English – should be clearly and grammatically written, in an easily
readable style.
Attention to detail of the language will avoid severe misunderstandings which might
lead to rejection of the paper.
Correct language is the responsibility of the authors.
PAPER TITLE HERE
Author1, Author2
1
Affiliation Name 1
2
Affiliation Name 2
Abstract: Each paper should be preceded by an abstract that summarizes the content in approximately 150 – 200
words. This document is intended to be the template of full manuscripts to be submitted to the editor. Styles
of various types of headings and texts are installed in this document in the form of style specifications. It
should be easy for you to specify the format of your paper in accordance to our requests by using this
template.
Keywords: List of key words (not more than 5) proposed by the authors, separated by semicolons.
INTRODUCTION
It is essential for us that authors write and prepare their manuscripts according to
the instructions and specifications listed below. The length and effectiveness of the
peer review process will largely depend upon the care used by authors in preparing
their manuscripts. Therefore, contributors are strongly encouraged to read these
instructions carefully before preparing a manuscript for submission, and to check
the manuscript for conformance before submitting it for publication.
Organization of the manuscript:
General instructions for your preparation of the final manuscripts for the FPSP
2016 are described in our Call for Papers. You should remember the following
outline:
• The number of printed pages is maximum 10, including figures and tables.
• The paper size is A4 (ISO).
• Figures and tables should also be large enough to be clear under the 86% reduction.
Please use our Word template to prepare your text. All the necessary formatting is
already present in the template.
STYLE SPECIFICATIONS IN THE TEMPLATE
You can basically use all the functions in Word, particularly displayed lists, type
styles such as bold or italics, the indexing function, and the footnote function.
Only use the return key at the end of a paragraph or after headings, displayed lists,
and the like. Do not insert manual hyphenation and do not use formats such as
framing, centring, or shading.
Page Size and Margins
Use the following specifications which are already installed in the template:
• Page size: A4 (210 mm x 297 mm)
Margins:
• top, 55 mm;
• bottom, 49 mm;
• inside, 42 mm;
• outside, 38 mm; mirror margins.
• Column layout: Single column, always.
• Header and footer: header, 8 mm; footer, 8 mm.
Figure Size
When preparing your figures, size figures to fit in the page width. The line spacing
before the figure is 10 pt.
Figure Captions and Numbering
• Number the figures consecutively (e.g., Fig. 1). Figure parts should be denoted by lowercase
letters (a, b, c, etc.).
• Figure captions begin with the term Fig. in bold type, followed by the figure number, also in
bold type.
• Figure captions should be added below the figure, with the style specification as: font, Minion
Pro, 10 pt, justified; before, 6 pt; after, 12 pt.
Fig. 2 By way of example, this figure shows the figure size and lettering.
Acronyms
For the first occurrence (other than for commonly used acronyms) spell out each
word followed by the acronym in parentheses, e.g., Smart Little People’s Modelling
(SLP Modelling) and Project Based Learning (PBL).
Equations
• Equations of the type a2 + b2 = c2 can be written as normal text.
• For all other equations, please use MathType or the Microsoft equation editor, and insert the
graphic into your text file as an object. Do not create the equations with the default equation
editor.
• When entering your equation, select the appropriate style for each character from the menu. Do
not change the style settings in Style/Define. “Math” in the Style Menu covers the entries
“Function”, “Variable” and “Number”; the program will automatically style the character according
to one of these styles.
• Please ensure the different styles are defined in the program itself:
Table 1. Styles defined in the program itself.
Style Font Bold Italic
Text Times
Function Times
Variable Times ×
L.C.Greek Symbol ×
U.C.Greek Symbol
Vector-Matrix Times ×
Number Times
• Please do not insert symbols or special characters that are not part of equations as graphics or
using the formula editor if they are available as Symbol or Unicode fonts.
• Formulas/equations are numbered consecutively. The formula number is given in parentheses
as right aligned text next to the formula
(a + b)2 = a2 + b2 + 2ab
References
[1] Lynch, N. A., (1996). Distributed Algorithms, Morgan Kanfmann Publisher, San
Francisco.
[2] Miriyala, K. and Harandi, M. T., (1991). Automatic derivation of formal software
specifications from informal descriptions, IEEE Transactions on Software Engineering, Vol. 17,
no. 2, pp. 1126-1142.