Objects Falling

What is acceleration due to gravity?

When you drop an object, the speed that it falls increases the further it falls. This is because gravity is making the object accelerate towards the earth. Oddly enough the mass of the object has no bearing on this; a feather speeds up just as much as a rock! (as long as you are in a vacuum and there is no air slowing the object down.) A long time ago it was proven that this acceleration is a fixed number that is actually 9.81 m/s². This number is usually given the short form g:

g = 9.81 m/s²

Here is the problem

Create a program that assumes a person is on top of a cliff that is 100 m high. The user enters in the number of seconds (which represents the number of seconds since they released the object) and the program calculates how high the object currently is above ground. You should use the following formula:

H = 100 - (1/2)*gs²

Two Part Assignment

• This is a 2 week assignment:
  • Week 1 hand in DESIGN AND TEST CASES ONLY
  • Week 2 hand in EVERYTHING (INCLUDING ABOVE)
• Each week ENSURE you include the Marking Rubric

Things to note

• If you are not sure on any part of the problem, just ask me and I will give you additional information
• You must do the program in Python first (get a 3+). You can get a 4+ by doing the program in another programming language after talking with me.
• See Marking Rubric below
• Ensure you work through (in order):
  • GUI design
  • Top-down
  • Flow-chart
  • Pseudo-code
  • Test cases
  • Final, debugged, commented code
  • Github link
• Remember to think, Input – Process – Output, when designing your program

• The final assignment MUST be in one (1) *.pdf file when you are submitting each part
  • Part A:
    • Document Name
      • ensure it is the assignment #, course code and your full name
    • Cover Page
      • this will include the assignment #, course code and your full name
    • Checklist
      • documenting the parts of the assignment that are to be included and stating that you have included them
    • Design Document(s):
      • this includes GUI Design, Top-down Design, Flow-chart(s) and Pseudo-code
    • Test Cases:
      • at least three (3) test cases (maybe more if it is needed!) done by some other method than your (or some else's) program
    • Marking Rubric:
      • ensure you include the correct assignment marking rubric
      • ensure you "merge" it with your document, but do not just paste it onto a page at the end
  • Part B:
    • Document Name
      • ensure it is the assignment #, course code and your full name
    • Cover Page
      • this will include the assignment #, course code and your full name
    • Check List
      • documenting the parts of the assignment that are to be included and stating that you have included them
    • Design Document(s):
      • this includes GUI Design, Top-down Design, Flow-chart(s) and Pseudo-code
    • Test Cases:
      • at least three (3) test cases (maybe more if it is needed!) done by some other method than your (or some else's) program
    • Screen Shots:
      • screen shot for each test case you have from above, proving your program actually works
    • Github:
      • Clickable link to your Github repo
    • Code:
      • you must get ALL of the code into your document (in a logical order) as plain text
    • Marking Rubric:
      • ensure you include the correct assignment marking rubric
      • ensure you "merge" it with your document, but do not just paste it onto a page at the end