Documente Academic
Documente Profesional
Documente Cultură
School
Abstract
(200 words max) - describes and summarizes your research/study
A good abstract serves the function of “selling you work. It is critical that you can write a
complete and concise description of your work to entice potential readers (and judges) into
learning more about your project. As you work on writing an abstract for your project, use the
following checklist to ensure the following points:
Describe the importance of your work, the difficulty of the area, and the impact it
might have if successful.
***Be careful not to use too much jargon. In some cases it is appropriate to put the
problem statement before the motivation, but usually this only works if most readers
already understand why the problem is important.
Approach How did you go about solving or making progress on the problem?
Did you use simulation, analytic models, prototype construction, or analysis of field
data for an actual product?
What was the extent of your work (did you look at one application program or a
hundred programs in twenty different programming languages?)
Briefly describe the data collected from doing the project. Put the result there, in
numbers. Avoid vague, hand-waving results such as "very", "small", or "significant."
Scientific:
Purpose
Hypothesis (must be testable)
- Independent variable:
- Dependent variable:
- Controlled variables(at least 2)
Engineering:
Purpose / Problem:
Criteria (explain how each is relevant to project):
Constraints (explain how each is relevant to project):
Experiment Design
o Materials (May be a bullet point list BUT be specific & explain quantity)
o Methods / Procedures: (or Phases & Prototype Description: (How you are
setting up your experiment, description of conditions, timing and number of trials
measurements) ****Critical
Use the appropriate checklist below to ensure you have included all necessary information in
your procedure/phases
***As you carried out your project, you might have realized that your original procedure (from
Proposal) lacked many details. Make sure you add those details to this procedure to reflect what
you actually did during the project.
ENGINEERING - What makes for GOOD procedure (not necessary in order)? Yes / No?
1. Did you include your preliminary design / prototype - Sketches, drawings, models
2 Did you include a description for each of the phases of the project?
4. Have you included a process of how you will evaluate success (how success is measure and
analyzed)
5. The ultimate test: Can another individual duplicate the experiment based on the
experimental procedure you have written?
1. Have you included a description and size for all experimental and control groups?
3. Have you described how to change the independent variable and how to measure that
change?
4. Have you explained how the controlled variables will be maintained at a constant value?
5. Have you specified how many times you intend to repeat the experiment (should be at least
three times), and is that number of repetitions sufficient to give you reliable data?
6. Have you included a plan to analyze your data (what data you plan to collect, how you plan to
analyze it, etc.,)
7. The ultimate test: Can another individual duplicate the experiment based on the
experimental procedure you have written?
*** Is it apparent in your procedure what are the different variables (independent, dependent,
control variables)?
Results
o Data Visualization
Bibliography/References