Logout

Final Stages


Final Stage of Packaging For IB

(All this from the Montezuma Conference)

Video interview!!! <-------- (??)

---- 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 the second html link on the OOC home page, and then Guidance for the development of the internal assessment. But after checking the latest edition, use the code pasted a few pages after this.

For Dossier 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.)

Note that we will use html pages for the classes, which will be "printed to html" from Netbeans.
(Do make sure to note the color coding of the programmers' code, comments, and auto-generated code:
---> Your code - black
---> Your comments - gray
---> Netbeans auto-generated code - will be in grey boxes)

And include a comment like:

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

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

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

 

 

Final "Finishing Up" Stage

Go back to Criterion C, and add in at least one flow chart demonstrating how things work in your IA.

Do the "Post Coding UML", and be sure to label it clearly as being auto generated UML after your coding was finished.

 

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 ISP
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 ISP grade will
only go up when you complete and submit these.)

 

Final UML Diagram
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
dossier 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.
It will need to be printed on A3 paper.

 

The Code Listing Section
- Copy and paste your code from NetBeans to Microsoft Word.
- Reduce the font size enough so that it doesn’t waste paper, but is still readable.
- Change the text color of the NetBeans auto-generated code, perhaps dark blue.
(But please don’t use block highlighting; it wastes toner.) And make a clear note
of this fact near the beginning of the code,
- And reduce the size of the Netbeans 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 the comments the darkest shade of grey.

 

One File & Page Numbering
- Put all of your files together as one big Microsoft Word document.
- Insert a blank page at the beginning of the document, which will be your Table of
Contents.
- Insert page numbers. (The Table of Contents should be page 1.)
- Appendixes should numbered, and at the end of the main document.
- The Data Flow Diagram, the System Flow Chart, the UML diagrams etc. do not
need to be numbered, but need to be inserted in the correct places. [4 marks]

 

Table of Contents
See page 54 of the syllabus for what should be listed.
Plus, include other things you’ve added, particularly:
- C4 Success of the Program
- Appendixes [3 marks]
Cover Page
The way you do it for other internal assessments.
Try to think of a name for you program if you haven’t yet. [1 mark]
Other Suggested Finishing Touches
There are no ISP marks allotted for this one. But, if you’re done all the stages, and you
have a working program with at least 10 mastery aspects, then you probably have an IB
mark of between 30 and 45 out of 50. You’ve put countless hours toward this. Now you
have one last opportunity to get 5 – 10 more relatively easy marks by making a few minor
adjustments that I can see would bump up 2s to 3s and 3s to 4s according to the IB rubric.
It is important to note at this point that even an ISP rubric 18/20 might not be a 4/4 IB
mark, depending on what it was that you missed. But to get the extra full IB mark, you
probably don’t have to do much, so it is very well worth it. Just one more hour could get
you another bunch of marks. And on a project that’s worth a full 35% of a two year IB
program, that is indeed well worth your while.