Experimental Design

Statement of Problem
This should be a question that you pose before you set up your experiment. It should not be a simple yes or no question.

Hypothesis
Your guess as to the result of your experiment, possibly a guess to the question posed by the Statement of the Problem. It should express how the changes to the independent variable will affect the dependent variable.

Variables
Speaking of variables, there are three different kinds of variables you should define in your lab writeup.

Controlled Variables (CV)
Things that remain the same in your experiment. You do not want to have more than one variable changing in your experiment. List a few controlled variables. For example, if you are testing to see how fast a parachute falls with different mass, list: "Height at which parachute is dropped (in meters)"

Independent Variable (IV)
This is the variable that you are changing to examine its effect on the dependent variable. There should only be one IV. Be sure to use units. Also, list the different ways you will test this. With the same experiment as above, list: "Mass of of weight, in grams (1, 2, 3, 4 grams)"

Dependent Variable (DV)
This is what changes by changing your IV. Again, define this using units. Using the same previously given experiment, this would be "Time it takes for parachute to fall, in seconds."

Control or "Standard of Comparison"
Make sure you use a control. This should show that the Independent Variable is the variable causing the action or effect in the Dependent Variable. As always, explain why you choose this as your control.

Procedure
List the steps in your experiment clearly. Draw diagrams if your explanation might be better explained with one. To cut time, "Repeat steps X to Y" can be used, but make sure it makes sense. One way to try to check your procedure is to imagine if you have not done the experiment; would you be able to run it based only on the procedure? Make sure you have a few trials for each step. Without this, a single data point may be an outlier- or it may be a real data point and you would never know.

Observations
List a few quantitative observations and a few qualitative observations. Quantitative observations are those described with numbers- i.e. the mass fell 60 cm. Qualitative observations are those that describe an observation of non-numerical data- i.e. the parachute seemed to open up more with a heavier mass. List anything that you see that might have been a problem (Parachute did not open on trial three).

Statistics
Take the common statistics - mean, mode, range, median. Explain this data and give an example of a calculation. Yes, calculating a mean is easy, but regardless, show an example. Any other additional statistics that you may find important, include them.

Once your common statistics are done, make sure to do some more. Standard deviation is a very good statistic to include. The equation for calculating standard deviation is: std dev = sqrt( average( (value - mean)^2)). For a better visual equation and an explanation of what standard deviation is (which you will need to know to explain the statistic), see Wikipedia article on Standard Deviation. Actually doing trials is necessary, as a standard deviation of a sample size of 1 is clearly stupid. A key point that is easy to miss is the deviation has to be squared. If you don't, your result will always be 0, and though this may look pretty, it should be obvious that your data does not have a standard deviation of 0.

Your table of data should be neat- a ruler helps a lot. Be sure to keep writing your units. Also be sure to keep your significant figures consistent and logical. You do not want to have a number down to three decimals when your ruler can only accurately measure to one decimal.

Graph your data. Make the graph neat, legible. Use a legend if need be. Label the axes (with units) and make a title for the graph (including units here as well is a good idea; for example, "Time in takes a parachute to fall, in seconds, vs the weight, in grams".

In Division C, you will be expected to do more with the data. One essential aspect of the graph will be to create a regression, or line of best fit. Basically, since you're not really expected to have all the tools necessary, you won't be expected to make anything but a linear regression. If you can have your calculator create an accurate logarithmic regression. more power to you, but make sure to allot the appropriate amount of time for this section. The best fit line of dubious accuracy is made by drawing a straight line with a ruler that you think seems to go as close to all the points on the graph. Once you do, find the y-intercept, and calculate the slope. Make sure to consider which outliers are significant, and which are experimental errors. If you make these kinds of judgment calls, make sure to point it out and explain it in the Analysis section.

Analysis
Look at the data and draw some reasonable conclusions about the experiment. There should be trends; point them out and explain them. Discuss your statistics and again, explain them. Guesses are okay, even if they're wrong; they show your thought process. If you have any outliers or random "bad" data points, don't ignore them - again, write about them. Was there anything you did wrong that time, or was it just a fluke?

Conclusion
Answer your Statement of the Problem. Evaluate your hypothesis. Was it correct? How would you improve the experiment's procedure, if you were given another chance. Would you run a completely different experiment, with a more accurate or visible trend? What problems did you have in the experiment, and how would you fix them?

Common Strategies
Know who is doing what before you walk in. To do well, each person should be ready to do their own section of the lab. At the start of the event, discuss possible experiments, but do not waste too much time here. You only have 50 minutes to design run and write a lab. Optimally, you come in with a few ideas in mind, but if the event supervisors throw you a very random set of materials and a very unexpected prompt, be ready.

Keep your experiment simple. Too many variables= a lot of writing. For example take my regional experience. They gave us 3 balls (different colors), two rubber bands, a foot of masking tape, a metric stick and a mini catapult. Naturally you want to do and experiment with the catapult, but the were SOOO many variables to consider. So we did a dropping experiment on how does a rubber band affect the time it takes for a ball to drop. It was simple and it paid off. During the event balls were flying EVERYWHERE people were running and looking for them not good. But for us it worked out great (we got third out of 30). So in short keep it simple it will make you a lot more likely to win. You just have to ignore your urge to mess around with the catapult.

During the event, know your jobs. Preferably, for running the experiment, there should only be two people, as the third can keep up and write the procedure and observations as the experiment is being run. Once the experiment finishes, split up the remaining portions so as to be able to finish within the time limit. A good way to split the work is to have one person start writing the conclusion, which requires no data to write, while another does the statistics. As the statistics and trends become more clear, the third person and the statistics person should work together to write a good analysis of the data.

The above is just an example of a way to split the lab to fit it in the time limit. There are, of course, other ways. However, the point is that knowing your place and your jobs will make the event a whole lot smoother.

To practice, have somebody on your team, be it a coach or another team member, put together a bunch of materials and try to run the event yourself. Do not handicap yourself by always running the same experiment at every practice.

Practice trials
Experimental Design Practice