The HSC exam. (1 Viewer)

[Ragerunner]

From what i hear is that the majority of SDD exams are based on algorithms. Hearing from peoples respones in the 2002 one

however i checked the past paper and saw a 5 mark question to write an algorithm and 1 question to identify stuff in an algorithm they provided.

But that isn't that much is it ?

i was under the impression that if you learn algorithms very well you can own the SDD exam.

Well i do hope this is not true as i am struggling with it

is that true about algorithms and the exam ?

 

[del]

In 2002, there were 2 algorithms, but if u did the Hardware option you did 3 in total.

Theres always gonna be at least 6 mark or so write an algorithm for some scenario.

Not 100% true that knowing algorithms very well will ensure doing good.... but it is an easy way to get marks for the questions that involving anything such as writing an algorithm, desk checking etc etc

most of the test seems - well last year it was... on the process of software development........ dunno that just my opinion....


if you look at the algorithm question in 2002(the ticket system), 2001(Mikes Bikes scenario) sdd hsc exam, you'll notice they are practially the same........ 2002 has a bit more work to it (extra stuff like the sort)...

 

[Ragerunner]

well i find algorithms bs, which is why i really want to try do good in other places but not algorithms.

like writing an algorithm that uses an array is bs to the max for me. and apply searching and sorting is beyond me.

and those questions that ask you do so many things which you are expected to write like 1-2 pages. How do u guys actually start your first few lines of pseudocode ?

How do u approach the question?

 

[del]

If you are pretty good in the other aspects of SDD don't worry, 'cos it'll cover not getting all the marks in the algorithm section....for me, i was the opposite way round...

Before starting think of what the question is asking, what sort of control structure(s) you need and variables you need to use, whether or not file processing is done....

then think of a general/basic structure for the algorithm, if its to hard to get further than the basic structure, make sure to write the basic structure down such as BEGIN and END statements, initialise any variables you know need to be used.... if you know a loop has to be used stick the WHILE - END WHILE.... get marks just for doing that

for anything that uses files make sure you open the file and distinguish whether you are meant to process it sequentially or not...... if its random make sure to define something as the key/index

oh... and use sub programs... its not necessary, but it solves the problems of having to rewrite anything when you decided midway that the logic is wrong......'cos only have to fix the subprogram up...

 

[Ragerunner]

What is looping through an array ?