Login

Welcome, Guest. Please login or register.

May 11, 2026, 07:47:58 am

Author Topic: 2012 SD Exam Discussion  (Read 9608 times)  Share 

0 Members and 1 Guest are viewing this topic.

billyjackson768

  • Victorian
  • Trendsetter
  • **
  • Posts: 125
  • School: Echuca College
  • School Grad Year: 2012
Re: 2012 SD Exam Discussion
« Reply #15 on: November 16, 2012, 08:12:19 pm »
If you are sure of that I think now we may both lose a mark. You're 3001 in that case should have been a 4000. Then my 3500, which I am sure for 1 that I wrote down should have been that 2999 that I'm not entirely sure I wrote down. Well, unless the assessors are very generous with accepting answers that still have a sensible justification.

Well everything you wrote is right, it's just that they asked for 4 things not 5.... 4000 and 2999 have the same purpose so you are right it's just I don't see how you wrote 5 down...

I mustn't have. I defiantly didn't add anything extra. I so maybe I didn't include the 2999. My brain is on holiday now though so you'll have to wait till it's back before I can be sure.  :P

Uberjew

  • Victorian
  • Forum Regular
  • **
  • Posts: 71
  • School: McKinnon Secondary College
  • School Grad Year: 2013
Re: 2012 SD Exam Discussion
« Reply #16 on: November 16, 2012, 08:15:12 pm »
I was pretty pleased with the exam. The programming focus was a bit better than previous years too.

I'm also pretty happy with the last two questions of section B - actually having to write out some pseudocode.

Yeah that annoyed me. I'm not sure I did the best job for that. I think I just pretty much made temporary vales to equal length and width then made each of them take on the temporary value of the other so that they swap. I didn't really include much in the way of control structure. Just had the above described within and Begin and End statement. ;D

Begin
A <- 1
B <- 2
Repeat
A <- A + A
B <- B + 1
Until A >= B
End

Did that with same indentation as the pseudo code question later in section C.
2012: Mathematical Methods: CAS [41] | IT: Software Development [39]

2013: English Language [31] | Specialist Maths [40] | Physics [39] | Accounting [42]

ATAR Goal: 97.00

billyjackson768

  • Victorian
  • Trendsetter
  • **
  • Posts: 125
  • School: Echuca College
  • School Grad Year: 2012
Re: 2012 SD Exam Discussion
« Reply #17 on: November 16, 2012, 08:19:54 pm »
I was pretty pleased with the exam. The programming focus was a bit better than previous years too.

I'm also pretty happy with the last two questions of section B - actually having to write out some pseudocode.

Yeah that annoyed me. I'm not sure I did the best job for that. I think I just pretty much made temporary vales to equal length and width then made each of them take on the temporary value of the other so that they swap. I didn't really include much in the way of control structure. Just had the above described within and Begin and End statement. ;D

Begin
A <- 1
B <- 2
Repeat
A <- A + A
B <- B + 1
Until A >= B
End

Did that with same indentation as the pseudo code question later in section C.

I was talking about the other question. But was that one greater than or equal to? -_-

Uberjew

  • Victorian
  • Forum Regular
  • **
  • Posts: 71
  • School: McKinnon Secondary College
  • School Grad Year: 2013
Re: 2012 SD Exam Discussion
« Reply #18 on: November 16, 2012, 08:28:45 pm »

I was talking about the other question. But was that one greater than or equal to? -_-

Yes it was.
2012: Mathematical Methods: CAS [41] | IT: Software Development [39]

2013: English Language [31] | Specialist Maths [40] | Physics [39] | Accounting [42]

ATAR Goal: 97.00

billyjackson768

  • Victorian
  • Trendsetter
  • **
  • Posts: 125
  • School: Echuca College
  • School Grad Year: 2012
Re: 2012 SD Exam Discussion
« Reply #19 on: November 16, 2012, 09:43:38 pm »

I was talking about the other question. But was that one greater than or equal to? -_-

Yes it was.

I should probably take your word for that but... I want to at least be able to go to bed tonight dreaming of a 50, so I better not dig to much into everything which I may have already.  ::)

Yendall

  • Victorian
  • Forum Leader
  • ****
  • Posts: 808
Re: 2012 SD Exam Discussion
« Reply #20 on: November 17, 2012, 12:36:23 pm »
The case study section asked you to fill in a UCD (first time ever) and a DFD (first in a long time). What was your answer to the DFD and UCD? Also, the test table asked for values to test the requirements form 3000 to 3999, what values did you provide? Does that imply inclusive, exclusive or one of each?

I did 2999, 3000, 3001 and 3999.  That tests all boundaries, expected data and invalid data.
The conditions were <3000 and >3999 so my test data was:
  • 2999 (<3000)
  • 3000 (=3000 AND <3999) [Lower Bound]
  • 3999 (=3900 AND > 3000) [Upper Bound]
  • 4000 (>3999)

Your test data doesn't account for >3999
« Last Edit: November 17, 2012, 12:40:46 pm by Yendall »
2013 - 2016: Bachelor of Computer Science @ RMIT
2017 - 2018: Master of Data Science @ RMIT
ΟΟΟΟ
VCE '12: | English | I.T: Applications | I.T: Software Development | Music Performance Solo |  Further Mathematics | Studio Arts |

Uberjew

  • Victorian
  • Forum Regular
  • **
  • Posts: 71
  • School: McKinnon Secondary College
  • School Grad Year: 2013
Re: 2012 SD Exam Discussion
« Reply #21 on: November 17, 2012, 12:47:38 pm »
The case study section asked you to fill in a UCD (first time ever) and a DFD (first in a long time). What was your answer to the DFD and UCD? Also, the test table asked for values to test the requirements form 3000 to 3999, what values did you provide? Does that imply inclusive, exclusive or one of each?

I did 2999, 3000, 3001 and 3999.  That tests all boundaries, expected data and invalid data.
The conditions were <3000 and >3999 so my test data was:
  • 2999 (<3000)
  • 3000 (=3000 AND <3999) [Lower Bound]
  • 3999 (=3900 AND > 3000) [Upper Bound]
  • 4000 (>3999)

Your test data doesn't account for >3999

Okay well 2999 and 4000 serve the same purpose in my reasoning because they're both invalid data.  3000 and 3999 are borderline, there needs to be something in between.  This is were i think reasoning comes in because generally you want before lower border, lower borer, inbetween borders, upper border and above upper border.

Technically 3000 and 3999 are both in the allowed values so they would count as just one.
2012: Mathematical Methods: CAS [41] | IT: Software Development [39]

2013: English Language [31] | Specialist Maths [40] | Physics [39] | Accounting [42]

ATAR Goal: 97.00

Yendall

  • Victorian
  • Forum Leader
  • ****
  • Posts: 808
Re: 2012 SD Exam Discussion
« Reply #22 on: November 17, 2012, 12:48:57 pm »
3000 and 3999 are between?
2013 - 2016: Bachelor of Computer Science @ RMIT
2017 - 2018: Master of Data Science @ RMIT
ΟΟΟΟ
VCE '12: | English | I.T: Applications | I.T: Software Development | Music Performance Solo |  Further Mathematics | Studio Arts |

Uberjew

  • Victorian
  • Forum Regular
  • **
  • Posts: 71
  • School: McKinnon Secondary College
  • School Grad Year: 2013
Re: 2012 SD Exam Discussion
« Reply #23 on: November 17, 2012, 12:50:53 pm »
3000 and 3999 are between?

Well technically anything below 3000 and above 3999 isn't in the allowed values so as those 2 are, they technically would serve the same purpose.  The border is really not existent as it's not an equal to sign.

My reasoning for just using 2999 and not 4000 was that it was enough to test invalid data.
2012: Mathematical Methods: CAS [41] | IT: Software Development [39]

2013: English Language [31] | Specialist Maths [40] | Physics [39] | Accounting [42]

ATAR Goal: 97.00

Yendall

  • Victorian
  • Forum Leader
  • ****
  • Posts: 808
Re: 2012 SD Exam Discussion
« Reply #24 on: November 17, 2012, 12:54:04 pm »
It's not simply to test "invalid data" as a value. You have to test all conditions. You need to make sure that anything under 3000 and over 3999 are invalid. If you don't test over 3999, how do you know that if someone inputs a number over 3999, like 4000, that it's going to return the correct value? There could be a logic error or something that you will never know because you didn't test it.

The boundaries are between: 2999 and 4000 at a minimum.

You need to test at least one value above and below to test both conditions, and at least two between.
2013 - 2016: Bachelor of Computer Science @ RMIT
2017 - 2018: Master of Data Science @ RMIT
ΟΟΟΟ
VCE '12: | English | I.T: Applications | I.T: Software Development | Music Performance Solo |  Further Mathematics | Studio Arts |

Uberjew

  • Victorian
  • Forum Regular
  • **
  • Posts: 71
  • School: McKinnon Secondary College
  • School Grad Year: 2013
Re: 2012 SD Exam Discussion
« Reply #25 on: November 17, 2012, 12:56:30 pm »
It's not simply to test "invalid data" as a value. You have to test all conditions. You need to make sure that anything under 3000 and over 3999 are invalid. If you don't test over 3999, how do you know that if someone inputs a number over 3999, like 4000, that it's going to return the correct value? There could be a logic error or something that you will never know because you didn't test it.

The boundaries are between: 2999 and 4000 at a minimum.

You need to test at least one value above and below to test both conditions, and at least two between.

I used 2999 as my test and invalid data as my reasoning.  I should be fine imo
2012: Mathematical Methods: CAS [41] | IT: Software Development [39]

2013: English Language [31] | Specialist Maths [40] | Physics [39] | Accounting [42]

ATAR Goal: 97.00

Yendall

  • Victorian
  • Forum Leader
  • ****
  • Posts: 808
Re: 2012 SD Exam Discussion
« Reply #26 on: November 17, 2012, 12:57:05 pm »
It's not simply to test "invalid data" as a value. You have to test all conditions. You need to make sure that anything under 3000 and over 3999 are invalid. If you don't test over 3999, how do you know that if someone inputs a number over 3999, like 4000, that it's going to return the correct value? There could be a logic error or something that you will never know because you didn't test it.

The boundaries are between: 2999 and 4000 at a minimum.

You need to test at least one value above and below to test both conditions, and at least two between.

I used 2999 as my test and invalid data as my reasoning.  I should be fine imo
We'll see. In my eyes you didn't test all conditions.
2013 - 2016: Bachelor of Computer Science @ RMIT
2017 - 2018: Master of Data Science @ RMIT
ΟΟΟΟ
VCE '12: | English | I.T: Applications | I.T: Software Development | Music Performance Solo |  Further Mathematics | Studio Arts |

Uberjew

  • Victorian
  • Forum Regular
  • **
  • Posts: 71
  • School: McKinnon Secondary College
  • School Grad Year: 2013
Re: 2012 SD Exam Discussion
« Reply #27 on: November 17, 2012, 01:01:45 pm »
It's not simply to test "invalid data" as a value. You have to test all conditions. You need to make sure that anything under 3000 and over 3999 are invalid. If you don't test over 3999, how do you know that if someone inputs a number over 3999, like 4000, that it's going to return the correct value? There could be a logic error or something that you will never know because you didn't test it.

The boundaries are between: 2999 and 4000 at a minimum.

You need to test at least one value above and below to test both conditions, and at least two between.

I used 2999 as my test and invalid data as my reasoning.  I should be fine imo
We'll see. In my eyes you didn't test all conditions.

Well i think that you need something between 3000 and 3999 which is expected, usual, non-boundary values.
2012: Mathematical Methods: CAS [41] | IT: Software Development [39]

2013: English Language [31] | Specialist Maths [40] | Physics [39] | Accounting [42]

ATAR Goal: 97.00

Yendall

  • Victorian
  • Forum Leader
  • ****
  • Posts: 808
Re: 2012 SD Exam Discussion
« Reply #28 on: November 17, 2012, 01:03:12 pm »
It's not simply to test "invalid data" as a value. You have to test all conditions. You need to make sure that anything under 3000 and over 3999 are invalid. If you don't test over 3999, how do you know that if someone inputs a number over 3999, like 4000, that it's going to return the correct value? There could be a logic error or something that you will never know because you didn't test it.

The boundaries are between: 2999 and 4000 at a minimum.

You need to test at least one value above and below to test both conditions, and at least two between.

I used 2999 as my test and invalid data as my reasoning.  I should be fine imo
We'll see. In my eyes you didn't test all conditions.

Well i think that you need something between 3000 and 3999 which is expected, usual, non-boundary values.
I would agree with you if the boundaries were : <= 3000 and >= 3999.
2013 - 2016: Bachelor of Computer Science @ RMIT
2017 - 2018: Master of Data Science @ RMIT
ΟΟΟΟ
VCE '12: | English | I.T: Applications | I.T: Software Development | Music Performance Solo |  Further Mathematics | Studio Arts |