squ34ki
heavenian woohzaa!
Cardslot is set as False
so WHILE NOt cardslot
means while there is a card
so WHILE NOt cardslot
means while there is a card
-
Best of luck to the class of 2024 for their HSC exams. You got this! Let us know your thoughts on the HSC exams here -
YOU can help the next generation of students in the community! Share your trial papers and notes on our Notes & Resources page
Question 22 exam thoughts (1 Viewer)
- Thread starter Ragerunner
- Start date
Saintly Devil
Member
- Joined
- Oct 12, 2002
- Messages
- 107
hmm......i don know..... i think WHILE NOT cardslot means that whilst there isn't a card in the slot. That's the point of READ cardslot being put in a loop - to continually monitor when a card is input.
squ34ki
heavenian woohzaa!
but cardslot is a booleen set to false???
squ34ki
heavenian woohzaa!
that's a logic error isn't it?
so i changed it to While cardslot is false
so i changed it to While cardslot is false
~Perfection
-Funked Up-
same 'ere
yeh, thats what my friend saidOriginally posted by Fiona
Oh crap.
I thought it was later on when the thing checked to see if the card was there, and then after the IF thing to see if there was a card, there was instructions for what to do.
I thought the error was that in even if there was no card, it was doing the instructions for if there was a card eg. checking the password and stuff.
Hmm...
saves.the.day
Member
dammit. After reading this ton of posts I realise I am wrong and after reading all these posts, yours seems like the most logical response. This is because
a) its a logic error hehe
But if this is the right answer, then that exam was a total ripoff. Seriously.. the code was flawless except one little thing like that grrr hehehe well enough of my sooking.
No
Doubt that. As much as I'd like to think so. If you read the marking guidelines for the past 2 years' algorithm desk checking, you can only identify the one problem, or when it specified in last years i think (can't remember off the top of my head if it was last year or 2001) it specified multiple.
But I hope thats right.. gives us a chance lol
squ34ki
heavenian woohzaa!
don't worry, its just one question...
but that was a killer, there was so many ways to interpret the error, like ppl said, the error could have been in the validated.
but that was a killer, there was so many ways to interpret the error, like ppl said, the error could have been in the validated.
Kn1ght_M4r3
Member
why n0t scan the question up and see wat sam d says?
squ34ki
heavenian woohzaa!
what do you mean?
Ragerunner
Your friendly HSC guide
http://unix.ozclans.com/HSC/2003_HSC_SDD_Section_II.pdf
There we go, section II scanned.
NOW PREPARE FOR US TO GET OWNED
There we go, section II scanned.
NOW PREPARE FOR US TO GET OWNED
saves.the.day
Member
SamD is the author of the red software design and development book and he's been coming on the forums alot helping other students with marking algo and answering questions etc.
For more info.. http://www.boredofstudies.org/community/showthread.php?s=&threadid=18228
rushworld
Member
Was I the only person who found a few logical errors in the algorithm?
1) System_on [Line 2] is never used throughout the code, it's 'Switched_on' [Line 4/20].
2) When the 'WHILE NOT CardInSlot' loop is entered in to it will continually repeat over and over until CardInSolot = TRUE. So in essence this is a logical error because 'Switched_on' can never be turned to FALSE (so the system cannot be turned off) unless you put in a card and bypass the Lines 15-etc crap somehow, perhaps a dummy card?
I'm sure I found some more during the exam I just can't think right now, too tired -_-
EDIT: Okay I read all the other posts, and maybe I'm not the only one... *shrug*
1) System_on [Line 2] is never used throughout the code, it's 'Switched_on' [Line 4/20].
2) When the 'WHILE NOT CardInSlot' loop is entered in to it will continually repeat over and over until CardInSolot = TRUE. So in essence this is a logical error because 'Switched_on' can never be turned to FALSE (so the system cannot be turned off) unless you put in a card and bypass the Lines 15-etc crap somehow, perhaps a dummy card?
I'm sure I found some more during the exam I just can't think right now, too tired -_-
EDIT: Okay I read all the other posts, and maybe I'm not the only one... *shrug*
Last edited:
Here's what I've posted to the Computing Studies Teachers group in regard to 22 (b)(i)...
Hi everyone,
Some comments on 22(b)(ii) in the SDD HSC.
Exam committee members, please take these comments as constructive criticism. I just feel for the students who had to answer this question and for the poor buggers who've got to mark it!
Anyway here's my comments on it...
1. Firstly, just prior to part (ii) the question says "The system has a logic error", the "system" not necessarily the algorithm, although most would assume the logic error is in the algorithm. Then in part (ii) it says "Locate the error...", we assume "THE error" is THE logic error previously referred to, but maybe not! I know this is somewhat pedantic; however maybe it means consideration should be given to awarding marks for locating/correcting any type of error? (Hence my non-logic error comments below).
2. Line 4 is an error (but is it in reality a typo?) still it should be WHILE System_on. There are two possible effects, either you never enter the loop at all (if Switched_on is false) or processing continues infinitely (if Switched_on is True). In either case it results in bodgy processing, so it is a logic error. If this is the intended error then it's pretty trivial for 4 marks, it's a shame it's in the question as many students will have spotted it and just waffled on about it. Surely students will get marks for it... as the question says locate THE error. (Also if you need to READ this value from somewhere at the end of the loop then surely you'd need to READ it before the loop as a priming READ).
3. Line 21 is redundant, but this does not cause a logic error.
4. Line 5 has a space in CustomerNumber. This line is pointless anyway, as the CustomerNumber originates from the AcceptCardDetails call, so not a logic error. Similarly, why is Validated and StoredPassword initialised? The values for all three of these identifiers originate from calls before they are processed at all, hence they dont need to be initialised at all. (When implemented in code you need to declare them but you dont need to initialise them).
5. The mainline does not implement the structure chart correctly. In the pseudocode AcceptMenuChoice is executed in response to a decision based on the value of Validated, yet no decision diamond appears on the structure chart. The structure chart indicates that the Validated control parameter is sent to the AcceptMenuChoice routine, which it is. The implication being that it is used within the AcceptMenuChoice routine to determine if menu choices can indeed be processed. Is this a logic error? It all still works as intended so I guess not, but there is redundant processing. However, the logic in the pseudocode does not match the logic in the structure chart, so in this sense it is a logic error (or at least some sort of error),its better than writing nothing so I'd hope some portion of the marks would be awarded.
6. I suspect this could just be 'THE logic error' the examiners were after, but I'm not a mind reader. Imagine the ATM is turned on (Switched_on or System_on, whatever), execution has now entered the outside loop. CardInSlot is set to FALSE, so we enter the inside loop. The only way you can ever get out of this 'WHILE NOT CardInSlot loop is to shove in a card. So the only way to get the thing to turn off is to switch it off (whatever that means!) then shove a card in the card slot, this gets you out of the 'WHILE NOT CardInSlot' loop, before System_on (or Switched_on) is read as false. This is weird stuff, as it seems logical to assume System_on or Switched_on refers to the power, if you turn the power off then surely everything stops regardless of the algorithm! (Maybe there's a battery, so the current transaction can be completed, who knows!) If this is "THE error" then it's a bit obtuse, I can think of heaps of ways to include a logic error in the algorithm, and this would not be one of them.
So how do kids fix all this mess? Here's one possible solution that, I think, fixes all of the above...
Have I missed the intended logic error? If I have then let me know, and then trash this post!
Regards,
Sam
(Kids are asking about this on the Bored of Studies site, so Ill post a copy there also).
Hi everyone,
Some comments on 22(b)(ii) in the SDD HSC.
Exam committee members, please take these comments as constructive criticism. I just feel for the students who had to answer this question and for the poor buggers who've got to mark it!
Anyway here's my comments on it...
1. Firstly, just prior to part (ii) the question says "The system has a logic error", the "system" not necessarily the algorithm, although most would assume the logic error is in the algorithm. Then in part (ii) it says "Locate the error...", we assume "THE error" is THE logic error previously referred to, but maybe not! I know this is somewhat pedantic; however maybe it means consideration should be given to awarding marks for locating/correcting any type of error? (Hence my non-logic error comments below).
2. Line 4 is an error (but is it in reality a typo?) still it should be WHILE System_on. There are two possible effects, either you never enter the loop at all (if Switched_on is false) or processing continues infinitely (if Switched_on is True). In either case it results in bodgy processing, so it is a logic error. If this is the intended error then it's pretty trivial for 4 marks, it's a shame it's in the question as many students will have spotted it and just waffled on about it. Surely students will get marks for it... as the question says locate THE error. (Also if you need to READ this value from somewhere at the end of the loop then surely you'd need to READ it before the loop as a priming READ).
3. Line 21 is redundant, but this does not cause a logic error.
4. Line 5 has a space in CustomerNumber. This line is pointless anyway, as the CustomerNumber originates from the AcceptCardDetails call, so not a logic error. Similarly, why is Validated and StoredPassword initialised? The values for all three of these identifiers originate from calls before they are processed at all, hence they dont need to be initialised at all. (When implemented in code you need to declare them but you dont need to initialise them).
5. The mainline does not implement the structure chart correctly. In the pseudocode AcceptMenuChoice is executed in response to a decision based on the value of Validated, yet no decision diamond appears on the structure chart. The structure chart indicates that the Validated control parameter is sent to the AcceptMenuChoice routine, which it is. The implication being that it is used within the AcceptMenuChoice routine to determine if menu choices can indeed be processed. Is this a logic error? It all still works as intended so I guess not, but there is redundant processing. However, the logic in the pseudocode does not match the logic in the structure chart, so in this sense it is a logic error (or at least some sort of error),its better than writing nothing so I'd hope some portion of the marks would be awarded.
6. I suspect this could just be 'THE logic error' the examiners were after, but I'm not a mind reader. Imagine the ATM is turned on (Switched_on or System_on, whatever), execution has now entered the outside loop. CardInSlot is set to FALSE, so we enter the inside loop. The only way you can ever get out of this 'WHILE NOT CardInSlot loop is to shove in a card. So the only way to get the thing to turn off is to switch it off (whatever that means!) then shove a card in the card slot, this gets you out of the 'WHILE NOT CardInSlot' loop, before System_on (or Switched_on) is read as false. This is weird stuff, as it seems logical to assume System_on or Switched_on refers to the power, if you turn the power off then surely everything stops regardless of the algorithm! (Maybe there's a battery, so the current transaction can be completed, who knows!) If this is "THE error" then it's a bit obtuse, I can think of heaps of ways to include a logic error in the algorithm, and this would not be one of them.
So how do kids fix all this mess? Here's one possible solution that, I think, fixes all of the above...
Code:
BEGIN ATM System
READ System_on
WHILE System_on
IF Card is located in cardslot THEN
AcceptCardDetails(CustomerNumber,StoredPassword)
AcceptAndValidatePassword(StoredPassword,Validated)
AcceptMenuChoice(Validated,CustomerNumber)
ENDIF
READ System_on
ENDWHILE
ENDRegards,
Sam
(Kids are asking about this on the Bored of Studies site, so Ill post a copy there also).
Ragerunner
Your friendly HSC guide
Hmmm....interesting. Most I didn't pick up.
But did they expect us students to be able to do that?
Pretty bad question. And it was worth 4 marks!
But did they expect us students to be able to do that?
Pretty bad question. And it was worth 4 marks!
True_Monolith07
New Member
- Joined
- Oct 28, 2003
- Messages
- 5
urm...does the fact that it doesnt validate their password b4 accepting their credit details count as a logic error or a design flaw.
Ragerunner
Your friendly HSC guide
Logic error = works fine but the expected output is wrong?
The card details are, in terms of the system given, just the CustomerNumber. I'd say the StoredPassword is looked up in the banks database using the CustomerNumber. The pass word is not validated until the ValidatePassword routine.
No, you don't need all my waffle. That was my analysis of the question, not a recommended solution.
From a student's point of view it really doesn't matter too much that the question was a bit bodgy. The marking process is extremely thorough, and I can confidently say that answers with worth will be awarded marks accordingly.
HTH
Sam