OCR AS Computing - F452 - 3rd June 2015

In the code questions are we righting in our high level language or pseudo code?
The question I just did had an answer in pseudo code not sure if this is the same for all coding questions.

We've been told to always write in pseudo-code unless the question states otherwise.

Damn, now I need to practice writing in pseudo code.

What do you guys find trickiest about F452? For me, there are less definitions to learn so I perform well on worded questions, but I make the most stupid mistakes with dry runs and writing algorithms. I repeatedly start the trace table with the wrong value and cock it all up.

Can someone please share their design of a suitable layout so I can see what exactly we are supposed to put?
Do we put actual stuff on the design, say like if the design has a timer to we put say "12:08" and then put an arrow (annotation) pointing to it saying it's a timer or can we just put a box and right timer in it?

(Just tell me if this doesn't make sense!)

I don't have a design to share but I think both would be okay. As long as you annotate it and show what it is then they can see that you understand the relevance fair. One thing I always remember is that there are extra things that you need to add to get full marks (not always mentioned) such as a 'next' button or a scroll bar.


Posted from TSR Mobile

Are we supposed to know what MOD means?
Because a question I'm on says state the value of TicketNumber MOD Key.
Key has a value of 10 and TicketNumber has a value of 3210.

Are we supposed to know what MOD means?
Because a question I'm on says state the value of TicketNumber MOD Key.
Key has a value of 10 and TicketNumber has a value of 3210.

MOD means Modular Division. It returns a remainder of division

EDIT: Sorry didn't see your reply :P

Has Any body got a definition for run time errors? Mine seems half dodgy.

Runtime errors can only be found while the code is executing ("running". Consider the formula (a+b)/(c-d). If c == d, then the program will crash, as it is dividing by zero. It may be rare that c is made equal to d (or d is made equal to c), therefore runtime errors can often be the hardest to debug.


Taken from;http://www.ocrcomputing.org.uk/f452/solution_testing/errors.html

Has Any body got a definition for run time errors? Mine seems half dodgy.

I think the simple definition of a runtime error is when the programmer asks the processor to do a impossible task. Often this will result in the programming crashing.

Always note that a runtime error will be cause by the programmer themselves and not for some other reason.

I could be completely wrong ,but this was a definition i got taught and learnt .