I may have screwed up the "What factors affect if an array should be sorted, and which search type should be used?", just due to clarity, and at the end I started going off topic and talking about sequential and random files lol^ Hw/sw was the worst section, section 1 and 2 were fairly easy though
HW\SW is my strength, but it had a binary division question (if they expect full and proper working [shift and subtract], most people will get it wrong) and a question about headers, body data and trailers, using escape characters (eg. What happens if the escape character is removed from the string?) They gave us all the stuff to interpret the body with, but one question asked "What data would be in the header and trailer?" with no given information except that the data went to digital displays.Haven't seen the paper but students are saying the HW\SW option was horrendous. Thoughts?
I just wrote the commands "Open FoodData", "Read next line". Should be enough for psuedocode.How do you read the sequential file for the algorithm question? I got rekt by that and the instantiation question in programming paradigms
You should be OK with all that. Open file for read\write\append is a little more correct.I just wrote the commands "Open FoodData", "Read next line". Should be enough for psuedocode.
Hopefully accessing each character in the line like an array is valid (ie. "IF line(letter) = 'a', do thing").
I think I wrote "Open [...] for input" (from Visual Basic, but should still clear enough for pseudo) (I'm 90% sure I didn't write output instead of input lol)You should be OK with all that. Open file for read\write\append is a little more correct.
I did that question last iirc. Also, almost forgot to add that the length of the body would need to be in the header, until last few minutes. I also put "and other metadata" because my answer was too short :/Had a look at the data stream question. A really wordy and overly complex scenario with no mention of the header\trailer contents, then the first question is about header \trailer. The question was then poorly worded. Should have been something along the lines of what information is typically found in a header\trailer. Would have tested the same knowledge without confusing the f out of everyone.
OH SHIT, I DIDN'T SEE THE "C"Second part spelt out CAT in Courier\Italic\bold with some flashing which changes
3rd part with the 1B missing spelt out CFPPAT I think
Nice - the markers Giz themselves every time someone puts "metadata" in an answer. Youll do wellI did that question last iirc. Also, almost forgot to add that the length of the body would need to be in the header, until last few minutes. I also put "and other metadata" because my answer was too short :/
I doubt it. I did pen too. The paper says to use pencil, but I believe it's mainly so they don't get massive scribbled-out parts when someone might make a mistake and try to fix it but end up making it illegible, etc. Also, I've never seen "pencil" in a marking criteria. I don't even think you need a ruler, as long as it's clear what you did.I drew my charts and stuff with a pen. Will I get marked down?
I just went through them in three minutes, mostly using memory rather than working them out (so maybe some errors)1) A
4) D (literally could be any of them)
7) D (only one that describes physical components?)
9) A or B (?)
Generally, software experiences no aligning at the top.Question 9 is a strange question. I put B but after thinking about it, I think the correct answer might be A.
Does anyone know the cut off for Band 6? Or maybe the cut off for 95 ?
Also anyone know the answer for Q34 ii) (programming paradigms).