a short briefing was conducted on the 26th April 2017 during ICOCI 2017 as part of the efforts to improve the quality of manuscripts sent to Journal of ICT.

1. JOURNALProfessor Dr Zulikha Jamaludin
Universiti Utara Malaysia
zulie@uum.edu.my
A workshop session ICOCI 2017
ARTICLE
CONVERTING A CONFERENCE ARTICLE INTO A

2. ZULIKHA BINTI JAMALUDIN
PhD (Computer Science) USM Malaysia
MSc (Computer Science) University of Exeter, England
BSc (Computer Science) University of Lancaster, England
zulie@uum.edu.my
LIFETIME MEMBER OF EMERALD LITERATI
LISTED IN SCOPUS AUTHOR DIRECTORY SINCE 2003

3. WHY
PUBLISH?
Research is complete
only when the results
are shared with the
scientific community
(first sentence of Chapter
1, Publication Manual of
the APA)
Scientific journals
are the repository
of the accumulated
knowledge in a field

4. HAVE YOU HEARD OF
UUM
DENT
“…PUT A
UNIVERSE”
IN THE

5. THE STRUCTURE OF A
PAPER
RESEARCH

6. THE STRUCTURE TITLE
ABSTRACT
INTRODUCTION
BODY
DISCUSSION
REFERENCES
GENERAL
PARTICULAR
PARTICULAR
GENERAL

7. WHAT TO CHANGE
HOW MUCH CHANGES

8. …varies from journal to journal. In CS, the
informal rule is that the journal version
should have at least 40% new content
(including new experiments, new
algorithms, …), and this new content
should be identified clearly in a cover
letter/email.

9. …work based on reviewers comments

10. https://www.bookdepository.com/Writing-Your-Journal-Article-Twelve-Weeks-Wendy-Laura-
Belcher/9781412957014
SOME GUIDELINES CAN BE OBTAINED FROM…

11. CHOOSING THE
TITLE PhD
Staf
Dana
CoE
SCOPUS

17. Easy to understand
Precise
Attractive

18. Which of these two titles make you read the paper?
Check your grammar especially in the TITLE!

19. Reviewersguide…

20. ABSTRACT=SUBSTANCETHE MESSAGE TO DELIVER

21. Take a couple of journals in your
field that you are targeting. Scan
all the abstracts over the past few
issues. Analyse them: look closely
at all first and last sentences. The
first sentence (usually) gives the
rationale for the research
(issue/problem), and the last
asserts a 'contribution to
knowledge'.

22. KEYWORDS
SELECTION
NOTESON
long tail
keywords
Keywords
appear in the
article title &
abstract
Use sparingly
in the body –
not overstated
Try use  http://keywordtool.io/

23. HEADINGS &
SUBHEADINGS
DO NOT
resembles those in
technical report/thesis

24. A GOOD
Introduction
Do not
reach back
too far!

25. A TEMPLATE FOR AN
Introduction
“In studying <1- the semantic meaning of the
topic>, these keywords is operationally defined as
<2- the OD of the keywords appeared in the title>.
As such <3-major problems/gap> will be examined.
In order to do so, <4- the variables related to major
problems> must be investigated. So that in the end
<5- the claim or the significance> can be
shown/proven.“
Note:
Items 2, 3, 4 – can be more than one variable.

26. The editorial board will choose based on the urgency and
the importance of the study, which can be clearly seen in
the INTRODUCTION

27. LITERATURE REVIEW/
BACKGROUND
NOTEON
Warmly
acknowledge
Be generous
“In his inspiring paper, Ali
(2009) shows.... We
develop his foundation in
the following ways...”
Accurate

28. Be Highly SELECTIVE
Ensure that they support our points (RQs)
Choose the most recent
Use correct formatting
Do not try to impress by over-
referencing
LITERATURE REVIEW/
BACKGROUND
NOTESON
GUIDE:
Theoretical and application
type of papers: Cite some
60 papers
Review papers: Cite some
200 papers.

29. FORMATTING
STYLES
NOTESON
Strictly adhere to the journal’s
style and format,e.g. Citation &
reference format such as APA
High quality tables and figures,
i.e. saved as high resolution files.
Follow detailed instructions

30. …refer to the hand-out
MORE INFO
…have some added value in the journal paper with
respect to your already accepted conference paper.
Typically extended versions take the results in the
initial paper a few steps further. Ideally, extended
versions are more thorough with regards to theory
but may alternatively including a new set of
experiments to corroborate the original work
published, shown at a conference

31. Thank