Criteria for Evaluation of Submissions

1. Original Ideas

2. Reality of the System

3. Lessons from the Research

4. Choices in the Solution

5. Context (Assumptions)

6. Focus of Subject

7. Presentation of the Idea

8. Writing Style

--------------------------------------------------------------------------------------------------------------------------------------

1. Original Ideas

-> Are the ideas in the paper new? – Paper contains at least one new idea.

-> How do you know? – You must be familiar with the state of the art and current research in the area covered by your paper in order to know that your work is original.

-> Can you state the new idea concisely (briefly)? – Consider you don't really understand the idea yourself, Keep the Reader in mind. – Use them in the abstract for the paper.

-> What exactly is the problem being solved? – Your reader cannot be expected to guess the problem!! – Be specific. Be sure to explain why your problem couldn't be solved just as well by previously published techniques.

-> Are the ideas significant enough to justify a paper?.  Is the work described significantly different from existing related work?

-> Is all related work related from references, and have you actually read the cited material? (Forward Citation) –How you convince the reader of the superiority of your approach if he has read a cited paper and you haven't.

-> Are comparisons with previous work clear and explicit?

-> Does the work comprise a significant extension, validation, or repudiation (rejection) of earlier but unproven ideas? – Implementation experiences supporting or contradicting a previously published paper design are extremely valuable and are candidates for publication. Designs are cheap, but implementations are expensive.

-> What is the oldest paper you referenced? The newest? – Help alert you to blind spots in your knowledge or understanding. – Papers with only OLD references repeat recently published work. – Papers with only NEW references often "rediscover" (through ignorance) old ideas. – Have a Mix of references.

--------------------------------------------------------------------------------------------------------------------------------------

2. Reality of the System

-> Does the paper describe something that has actually been implemented? Reader has a right to know at the outset (beginning) whether the system under discussion is real or not.

-> If implemented. – Practical importance of the ideas?

-> If NOT implemented – Reviewers are very doubtful (skeptical ) of design only papers unless they are of high quality.

--------------------------------------------------------------------------------------------------------------------------------------

3. Lessons from the Research

-> What have you learned from the work? – you didn't learn anything, it is a reasonable that the readers also won't.

-> What should the reader learn from the paper? – Spell out the lessons clearly. (Many people repeat the mistakes of history because they didn't understand the history book)

-> How generally applicable are these lessons? – Be sure to state clearly the assumptions on which your conclusions rest. – When stating your conclusions, it helps to state the assumptions again (reader may not have seen them).

--------------------------------------------------------------------------------------------------------------------------------------

4. Choices in the Solution

-> What were the alternatives considered at various points, and why were the choices made the way they were? – You also want to record potentially interesting side-streets e.g. Parameters in algorithm that can look for other issues.

-> Did the choices turn out to be right, and, if so, was it for the reasons that motivated them in the first place? If not, what lessons have you learned from the experience? –(This work when such and such is set).

--------------------------------------------------------------------------------------------------------------------------------------

5. Context (Assumptions)

-> What are the assumptions on which the work is based? – State the Boundaries get them all, don’t overlook generally understood assumptions.

-> Are they realistic? – For "un-implemented systems" papers , must hope to support successful implementation. – For theoretical studies assumptions must reflect reality.

--------------------------------------------------------------------------------------------------------------------------------------

6. Focus of Subject

-> Does the introductory material contain excess baggage not needed for you main development? – Avoid the temptation to describe all major characteristics of your system at the same level of depth e.g. Distributed File System ( No - Network).

-> Do you include just enough material from previously published works to enable your reader to follow your thread of argument? – Don't burden your reader unnecessarily with lengthy extracts from cited works.

--------------------------------------------------------------------------------------------------------------------------------------

7. Presentation of the Idea

-> Are the ideas organized and presented in a clear and logical way?

-> Are terms defined before they are used?

-> Is the paper finished? –Reviewer cannot tolerate the omission of important explanation or justification.

-> Are forward references kept to a minimum? e.g. “... Will be described in detail in later section. “

-> Was an abstract written first? Does it communicate the important ideas of the paper? [Write the abstract before the paper (despite tradition) and even the outline, since it focuses your attention on the main ideas you wants to convey]

--------------------------------------------------------------------------------------------------------------------------------------

8. Writing Style

-> Is the writing clear and concise (brief)?

-> Are words spelled and used correctly?

-> Are the sentences complete and grammatically correct?

-> Are ambiguity, slang, and cuteness (attractiveness) avoided?

--------------------------------------------------------------------------------------------------------------------------------------

Summary

-> These questions can help you write a better technical paper.

-> Ask these questions often as you. Organize your presentation, Write your first draft, and Refine manuscript into its final form.

--------------------------------------------------------------------------------------------------------------------------------------

Registered Address: ERES Publications, Mavilai, Karanvilai, Udayamarthandam post, 629178, Kanyakumari dist., Tamilnadu, South India