Logout

Final Stages


Final Stage of Packaging For IB

(Much of this is from the Montezuma Conference)

---- Be very carful with the links!!!!!!!! Check before sending!!!!!
They want all files, including the video to be in the same zipped folder. <----

(Overall key point from past grading: Please do include the overall word count - hopefully less than 2000 words; any more than 2000 will not be read nor awarded marks.)

To get the Forms, it's from the Guidance for the development of the internal assessment part of the IB CS resources on-line.

For IA Form Head Page (see next page):

Use TextEdit to open and add the video links - Ignore rich text commands. Not a lot needs to be done as long as file names are not changed, and pdfs are used. (And do use pdfs as the format to make sure that they don't change.)

 

 

 

Final "Finishing Up" Stage

 

------> Be sure to clearly label each as being done "post" coding, as instructed by your teacher more as part of Development than as planning. How to word this, and where to put it.... ongoing question. <------

Flow Charts in Criterion C

Add in at least one flow chart demonstrating how things work in your IA.

 

Final Drafts of Various Stages

Look at the comments on the various stages handed back to you after a first draft.

Unless perfect, there will almost always be some small thing you can do to bump a
3 up to a 4 etc. on the IB scale. Plus, in some cases there may be some major
editing or revision that is needed not only to bump up the IB score, but the ISB
grade as well. Remember that the first draft and final draft are averaged together
for your total grade for each of these sections. (Which means your ISB grade will
only go up when you complete and submit these.)

 

Final UML Diagram - Optional/Possible

The UML diagram you did previously was for your own planning purposes. This
one will be added to aid others’ understanding your program. Place it in your
IA right after your other UML diagram, but clearly note the following exactly:
“this was done after completion of the program, and is included as system
documentation to enable both teacher, and moderator to get a good overview of
the solution.” You’ll use a program like “Fujaba” to automatically generate this.

 

The Code Listing Section

- Note that we will use html pages for the classes in the Appendix, which will be "printed to html" from Netbeans.

- Change the text color of the NetBeans auto-generated code to be block grey or something else we agree upon.
And make a clear note of this fact near the beginning of the code, something like this:

/*
####################################################################
####################################################################
####################################################################
####################################################################
####################################################################

*************** NOTE THAT ALL THE CODE WHICH IS ********************
*************** HIGHLIGHTED GREY BLOCK IS AUTO- ********************
*************** GENERATED FROM NETBEANS, NOT BY ********************
*************** ME. (It's mainly the GUI stuff.)********************

####################################################################
####################################################################
####################################################################
####################################################################
####################################################################
*/

- You could reduce the size of the Netbeans auto generated code, so it’s obviously smaller, but still able
to be discerned, if not terribly easily read.

- And also delete all the Netbeans auto-comments (for example “Put code here.”)

- Make your comments the darkest shade of grey.