The optimal structure of an Abstract

TITLE
The title should be an accurate promise of the abstract's
contents. It should explain as much as possible about the
context and the aims of the study.
Ideally, the title should be about 10–12 words long, and should
include the scope of the investigation, the study design and the
goal.
In general, it is preferable to make the title a description of what
was investigated rather than a statement of the results or
conclusions.
The abstract's title should be easy for the reader to understand
and should not include jargon or unfamiliar acronyms or
abbreviations
Structure of ABSTRACT
 Introduction
/Background
Purpose and Aim

Method

Results

Discussion / Conclusion
Introduction and background(what is the Existing
work ,limitations…)

Introduce ur topic and cover aim and objectives.

Say the proposed methods or alorithms or techniques use to

achieve the objectives.

Mention the what you are going to find out(results) and

which tool or platform ur using.
 A good abstract should address the five
following questions :
1. "Why did you start?" – Introduction or background
2. "What did you try to do?" – Aims and objectives
3. "What did you do?" – Methods
4. "What did you find?" – Results
5. "What does it mean?" – Conclusions
1. "Why did you start?" – Introduction
or background

• You should summarise, preferably in one

sentence, the current knowledge, or state-of-
the-art, specifically in relation to the work you
are presenting.
• Research problem.
• Gap of research in the field
 BACKGROUN
D
• No more than 5 sentences here, explaining why
this study is important, what it will add to the
science, or why your project matters.
• You may cite a critical reference here if crucial to
substantiating the significance of this work.
• Content in this section should relate directly to
the purpose/aims/question.
2. "What did you try to do?" – Aims
and objectives
• Here, you should state the aim of the study,
and ideally include a short statement of the
study's hypothesis.
• A legitimate scientific study is not done "to
prove that something is true" but rather "to
find out whether it is true."
• The difference may seem small, but it makes a
huge difference. A formal hypothesis shows
that you were objective.
Purpose/aims/research question
Begin like this:
• “The purpose / aim of this
(study/project/investigation) is to…” or
• “The question guiding this study/ project/
investigation) is…” or,
• You get the picture. Three sentences at most
should cover this.
3. "What did you do?" – Methods
• In an abstract, the description of the methods
has to be concise, and much of the details of
what was done must be omitted.
• However, in a few short sentences, you can
give the reader a good idea of the design of
the study, the context in which it was done,
and the types of measurements that were
included.
 Methods
• For a research study, it should include the design,
the setting, the sample, the measurement tools, and
the analysis approach.
• For a project, should include the setting, the
composition of your team, the participants you
worked with, your project intervention, and your
evaluation strategy.
• These should be appropriate to the purpose
/aims/questions.
 4. "What did you find?" – Results
• Give the main results of the study, not just in
subjective terms ("We found device X to be
superior to device Y") but also in the form of
some real data.
• You will need to choose which findings to report
here: it should be the most important data in
your study, and the findings on which your
conclusions will be based.
• Do not include a table or figure unless you need
it to show your results.
 Results
• Here you state just the facts.
• If a research study, include simplified
demographics, primary results.
• If a project, what was done and what did the
evaluation show.
• This should flow directly from the methods and
be consistent with the purpose/ aims/questions.
 Discussion
• Relate your results directly back to your
purpose/aims /research question. This is critical.
• Did you achieve your purpose, either in your
research or project? If not, why not? How was
your question answered?
• Is the answer is what you expected? Why or why
not? What were the major limitations of the study
or project (every study/project has them, so
don’t leave this out).
5. "What does it mean?" – Conclusions
• Here, space limitations generally limit you to a
single sentence of why you think your findings are
important, and their potential implications.
• Keep your conclusions reasonable and supportable
by the findings of your study.
• Remember that if your study was restricted to
certain case or a specific device, its results may not
extend beyond these restrictions.
• Recommendation / implication
 Advice for a good abstract writing
• Use simple sentences
• Ask your Guide

• Good abstracts are easy to read, clear and concise.

 Use simple sentences
• Unless they are basic, universally accepted
abbreviations, abbreviations should be
spelled out the first time they are used in
the abstract.
• Similarly, local expressions and jargon
should be kept out of the abstract.
 Ask your Guide
• Before the abstract is submitted, it should be
double-checked for accuracy, not only of the data
reported but of the description of the methods
and all other details.
• Having one or more batchmates/friends (who
were not involved in the study) read the abstract
and offer constructive criticism can be extremely
helpful.
• PROOF READ YOUR WORK! Avoid
grammatical errors and typos. Ask someone you
trust and respect to read it and give you feedback.
 Check Yourself
• Because your thinking may have evolved as you
wrote the abstract take time to be sure the entire
abstract evolves from your stated
purpose/aim/question.
• The background discussion should be narrowly
focused; the methods have to be right for the
purpose/aim/question; and the discussion should
use the same words as found in the statement of
purpose, etc.
 The language of abstract Writing
1. Often uses the third person
2. Often uses passive voice verbs to describe the researchers’
own actions
3. Negative results and conclusions not included
4. Avoid abbreviation, jargon, other language shortcuts that may
lead to confusion
5. Avoid repetition
6. Avoids meaningless expressions
7. Avoid adjective and descriptive details
8. Avoid illustration
9. Avoid footnotes
10. Avoid preliminaries
11. Avoid superlatives
 PPT
CHAITANYA BHARATHI INSTITUTE OF
TECHNOLOGY
DEPARTMENT OF ELECTRONICS AND COMMUNICATION ENGINEERING

BATCH no
STUDENT ROLL NO-NAME

GUIDE
Dr.A.VANI
Associate Professor
ECE Dept
CBIT
Hyderabad
Tiltle of Project
ABSTRACT
Introduction
AIM or Problem Statement
Objectives
To Identify
To find
To compare
Background work or literature survey
Proposed methodology or algorithms or techniques
Expected findings or results and how ur going to
implement
Conclusions according to objectives
These are some inputs only. You discuss with ur
guide and prepare accordingly
Here are some tips on your
slide(presentation) design:
1. Keep it simple
Most of the beautiful things are simple, so why don’t you follow that!
2. Keep font big (30 px onward is preferable)
Bigger fonts make the audience to get your points well. It also helps to
read faster and makes an impact.
3. Use pictures appropriately.
Add pictures in big size if it is important. Also, don’t make pictures to
small to make impact
4. Don’t mention more than 6 points in each slide
6 points would be perfect. More points lead to clutter and poor reading.
5. Add one those points which you are good at.
This is important because it boosts your confidence. Don’t add points
which you are not good at! It’s like killing oneself.
6. Don’t use too many colours.
This creates eye distraction. Use complementary colours
and either white or black background (gradient if it
suits) are suggested.
7. Avoid too much CAPITALIZATION.
More capitalization leads to clutter and distraction.
8. Don’t use too much animation.
Animations are impressive if you wisely use it. Better to
avoid for technical presentations.
9. Don’t use sound effects.
This trend is outdated and avoid it any cost
Some tips on Q & A, after the presentation:
• Ask yourself possible questions on your content and keep
answers ready.
• Learn to say NO rather confusing answers.
• Ask your teammate to help out by giving hints. That is
what teamwork is.
• Confess the truth, if examiners prove that “It is ready-made
project”, Say “Thank You” even if they made you cry!
• It always helps out to give a dry run either before your
friends, internal guides or mentally with yourself.
Remember
“The more you sweat in practice, the less you bleed in
battle!”