Logout

Video Instructions


Video
:

First of all note that on page 81 of the syllabus, it states that the the length of the video is to be 2-7 minutes.

And remember that the main purpose of the video is to demonstrate that your program:
A. does indeed work as it should, and
B. works as completely as stated in your evaluation
.

(Should they mention in their video that they are SL/HL.... hmmm... not sure.)

Introduction:
- introduce yourself by way of your IB number (but not your name, as per IB rules and regulations) and your program
- you can refer to your program as i-Pond, etc. 1.0, 1.1 etc.
- briefly mention the name and role of your client
- and what you program is intended to do for them
BUT all of this introduction should be no more than 30 seconds or so.

The Main Thing:
- demonstrate that your program works by running it, inputting data etc, saving, opening, searching and so on
(As with Elsa's good example, you may want to do this in two stages: first talk about what should happen on each pane with each button etc., and then actually run though it; this way the viewer is given an overview first, and will know what to expect as you do the real run-through.)
BUT if you do it this way, the first "talk-through" should be brief and general; way briefer than the actual run through.

- make sure to include at least a few examples of your error handling, but not everything because that would take too much time and be repetitive.
Things like JOptionPane pop-ups, you can just trigger with the appropriate error, and other try/catch situations, you could show in the code itself.

Additional/Optional
- you could also choose briefly show some code; maybe just scrolling up and down through a class or two, perhaps highlighting a sophisticated algorithm you're particularly proud of
(But remember that this is not the main purpose of the video; they can look at your code listing printed out if they want to see code.)
- and you may want to show your To Do (Extensibility) list, since it is also a Criterion D thing.
- plus you could include spoken reference to extensibility possibilities as you go, in the video. Things like "...and here is where I could add feature x...", or "...extensibility here is possible because I've set up things to be built upon by....".

One other minor point, but one which can make a difference is if you are going to be clicking a lot during your video, a lot of track-pad clicks can end up sounding annoying. So it may be better to have "tap" enabled for your track pad, which is a lot less noisy. And be careful of fan noise too, so cool it down first before recording if this may be an issue.