QUOTE(Trebor @ Sep 18 2005, 04:22 PM)
Yep. It's like IT, you make the project and then you do the preliminary design.
Chemistry coursework was pretty easy to be honest. Just make some reference to collision theory and you're into the top marks.
Hoop jumping, boring but easy enough.
In the second year of my Computer Science degree we had to do a group project split up into distinct stages (domain analysis, requirements capture, design, implementation and evaluation if I recall correctly). The idea at the design phase is to detail how the user interface is going to work and what goes on behind the scenes, then implement it in the implementation phase. The thing is, the easiest way I could think of doing the user interface designs was to use the tool I'd use in the implementation phase, so that's just what I did. Consequently, the implementation phase took 2 days once we got there

.
I seem to remember design and technology being really bad for this sort of thing - make a working product, invent three clearly flawed designs to support your decision to make it how you did.
QUOTE
Speaking of science coursework, can anyone explain to me the coursework stuff for double science. Do we hand in one full piece and then bits of all the others?
Is it still the Planning, Observation, Analysis, Evaluation system of a few years ago, marked out of 8/8/8/6? If so, all the exam board need is two planning sections, two observation sections etc. etc.. The marks are added together to form a mark out of 60, plus 6 marks for SPG, and then the total is rescaled to be out of 60 again.
The board don't mind how you manage to do two of each section - either two whole pieces of work, one whole piece of work + bits and pieces to make up the rest etc. I remember doing two whole pieces of work in Chemistry, but the class as a whole was weak in one section so we all did an extra observation section (the teacher prepared the first part so we just did the experiment and wrote down what happened).