################
OVERVIEW:
================

CP3047 frustrated me a lot when I did it (in 2003).
It's easy to go into this subject with the wrong expectations.
Also, we were told a lot of things which were later contradicted.


#1) Don't expect to learn ANYTHING during this subject unless you research it yourself!! We only had 1 contact hour per hour per semester, and the lecture often couldn't make it anyway.

#2) We were told the greatest empahasis of marks would be for implementation, and not documenation. As students we put almost 90% of our effort into implemenation, but, as it turned out, implemenataion was worth less than 20% of total marks. We were given little to no guideance on documentation, and only found out what was expect a week or two before each of the three submission dates.

#3) Personally, I wrote too much on documentation, and was dissapointed by the lack of feedback. It wasn't just the students who didn't know the correct ways to write Quality Insurance etc. In the end most of us got great marks for documentation just for attempting each section. Crazy.

#4) Phillip, unlike the lecture I had the semester believes in a much different type of "speech". Rather than preparing to give a mock presentation to clients, try approaching it as a one-on-one discussion with Phillip about the design on your project (from a architectural perspective). Personally, I'm not very good at impressing Phil - he and I always seem to think very different, but his methods of trying to fault your project does have a lot of merit. Always ask and make sure you know what your marker wants. Best of luck.

#5) One of the lecturers once said: "the only reason to do the project subjects is if you have a project you really want to do, and you need time to do it". That's about right. Once again, make sure you apply safety margins to your estimates, otherwise you'll almost certainly have bitten off more than you can deliver.


################
INSTRUCTIONS:
================

This download includes documentation only (although "Code.doc" shows you what my VB code looks like).

There were three submissions, but for each submission I just added any required sections to the previous document, so you'll find everything I've done in "Ass3 - Documentation.doc". I got good marks, but I have no idea how credible my documentation was. If you interested in seeing the Visual Basic files (and other stuff) for my actual Exam Creator program e-mail andrew_noske@yahoo.com .


################
FINAL WORDS:
================

Note: I chose excel to draw most of my diagrams & Microsoft Visio for flowcharts. To put these into my word document I used the print screen button & MS Paint. Easy as that.