Procedure advice- Bugs added to computer code (science fair)
Posted: Wed Jan 22, 2020 9:01 am
I need advice for my son's procedure on his science fair project (see project below). Does the procedure of adding three different bugs (each add one action) to the same code test the purpose and answer the question the best? Should we add more bugs or do more than 10 runs of the code on each? Seems to little to be super scientific???
Purpose: To determine the effect of a computer bug on efficient code.
Question: How much time can you actually save by eliminating all computer bugs?
Hypothesis: I predict that adding three different computer bugs to the same cod individually, will increase the time it takes to execute the code.
Variables: My Independent variable in this test, was our bugs, measured by the number of unnecessary blocks of code.
My dependent variable was the amount of time (measured to the thousandth of a second) of the bugs added to the otherwise clear and concise code.
My controlled variable was the same computer code in the same program, Scratch, and the same built in timer used for all the tests. I tested the clear performable and bug-free code, for time comparison.
Procedure: Test the time of a good computer code on Scratch (ball bouncing) Use the same computer code on Scratch and add three different bugs (lines of code that do not relate and are added to be inefficient). Run each code 10 times and records the results.
Results:
Bug 1- added average + .262 seconds
Bug 2- added average + .261 seconds
Bug 3- added average +.171 seconds
Purpose: To determine the effect of a computer bug on efficient code.
Question: How much time can you actually save by eliminating all computer bugs?
Hypothesis: I predict that adding three different computer bugs to the same cod individually, will increase the time it takes to execute the code.
Variables: My Independent variable in this test, was our bugs, measured by the number of unnecessary blocks of code.
My dependent variable was the amount of time (measured to the thousandth of a second) of the bugs added to the otherwise clear and concise code.
My controlled variable was the same computer code in the same program, Scratch, and the same built in timer used for all the tests. I tested the clear performable and bug-free code, for time comparison.
Procedure: Test the time of a good computer code on Scratch (ball bouncing) Use the same computer code on Scratch and add three different bugs (lines of code that do not relate and are added to be inefficient). Run each code 10 times and records the results.
Results:
Bug 1- added average + .262 seconds
Bug 2- added average + .261 seconds
Bug 3- added average +.171 seconds