Checkpoints wasn't too bad, though it was annoying after completing the entire book, redoing the VCAA questions in the actual past papers...
I got a 42 raw (ranked no 1 in SACs), which probably doesn't give me as much authority as someone with a 50 raw. Having said that, I'll try and go over what I did, what was effective, and what I probably should have done if I had my time over again.
SACsI hated IT SACs. Granted they were fairly easy work, but they were (unnecessarily) long and tedious, and in many cases diverted a large proportion of my time from my Unit 1/2 subjects (Hopefully this new study design reduces the workload). Having said that, I was able to gain decent unit marks (feel free to correct me on the use of the word 'decent' to describe my unit marks), which I think helped to make up for my poor exam result to give me a 42 raw study score.
I liked to take the case study and criteria, read it thoroughly and use that to establish what was expected for submission. I would also constantly clarify with the teacher what, and how much of a certain requirement was appropriate, to ensure I was completely satisfying the requirements. One mistake I made was not looking up what a structure chart was before creating one, and I lost 1.5 of the 3 marks available for that.
You will usually find that the actual product you need to produce is only a small component in the marks awarded. Some of my friends produced some fantastic solutions, but ended up wasting time that could have been better used getting their documentation up to scratch. My advice would be to make sure you produce a simple, but accurate/functional solution, and cover all bases in detail with everything else. The SACs are long enough to help commit to memory concepts you will need to know in your exam, so it will help you if you put the work in during your SACs.
Exam PreparationThe best thing you can do is find as many practice exams (even those of dubious quality), complete
each paper in exam conditions (which for half of the papers I did not do, mainly due to tiredness/waning focus/occasional interruptions), and harshly mark your answers compared to the answers. I didn't do the roughly 10-15 I completed in a certain order, and ended up doing some papers a second/third time. Usually it is recommended in a VCE study that the VCAA past papers are left to the end of your revision, but considering the dubious quality of most commercial papers, it would be wise to use your best judgement on that decision. I was guilty of marking some exam papers I completed too leniently, so try not to get in to that habit.
Personally, I did not write a comprehensive summary notes booklet like Plan-B. This was mainly because I felt that I knew most of the content well enough (mainly through my work in the SACs), and I didn't want to be greatly overwhelmed by having to learn the content from a book of that size. I thought it would be best for me to go hard at the papers, working on my responding technique, and trying to plug the holes in my knowledge. I printed out the study design, read each dot point and crossed out each point that I thought I knew, and then wrote an "IT notes for further revision" document that included material that I wasn't extremely familiar with, and tried to read/memorise that outside of practice exams.
On reflection, I would advise anyone to take up Plan-B's advice. The summary notes would help in getting used to the exact interpretations/wording expected by the examiners (IT Apps is not maths, so it is important to try and give the answers that the examiners want as much as you can, above and beyond any experience you have in IT). The error log is a fantastic idea to keep track of your mistakes to prevent them from reoccurring, and it is something I will consider doing for my subjects next year.
ExamFrom memory, my plan was to finish 30-45 mins early, so I could go over mistakes I thought I may have made and correct them (Put simply, I didn't really trust myself due to the occasional occurrence where my interpretation of a solution was different to the official solution).
During reading time, I ended up spending half of it answering the multiple choice (in between a slight loss of concentration for about 15-30 seconds which threw me off course a bit), and the rest on the short answer. I filled out the multiple choice section in about 5-10 minutes, and finished the paper with 30 mins to go to spare, so I could check my answers. That was a bad mistake...
I should not have answered the multiple choice in my head during reading time. This then took time away that I could have used to better read through each question and make sure my interpretation of the answer was better. A better plan of attack would have been to briefly skim over the multiple choice over the first couple of minutes, spend the rest of reading time going over each question and thinking carefully about what the question wanted, complete the mult. choice in about 15 minutes and finished the paper with 10-15 minutes to spare as Plan-B suggested.
To sum up, I performed poorly in my exam (see my sig for scores) due to my ineffective exam approach, and it had a large enough impact on the sort of score I received.
I hope this helps anyone taking IT Apps in 2011, and I wish everyone the best of luck. Just remember that IT nous is not enough to be successful in this subject. If you are prepared and have worked hard, you will do well without a doubt.