[Year 12 SofDev] Validation naming

Thu Dec 16 16:38:41 EST 2010

Dear colleagues

I would like to clarify several statements that have been made about the
content of the study design (2007-2010) and the Software development
examination. The study design does not specifically mention any types of
validation in the key knowledge or in the glossary - it defines
validation in a broad sense (page 52). And the Software development
examination did not assume that students had knowledge of specific types
of validation because a description of each type was provided in the
exam e.g. type - to make sure that only numeric characters have been
entered. This made it quite clear to the students the nature of each of
the listed validation tests so they were all on the 'same page' for this
question - it is never the intention of examinations to be confusing for
students. 

Glossaries

IT is one of only four study designs that has a glossary which has the
same status as the study design (as distinct from glossaries that are
part of the Advice for teachers). It took a lot of sweat and tears to
maintain the glossary in the 2011 study design. As has been stated in
the last VCE Bulletin Supplement
http://www.vcaa.vic.edu.au/correspondence/bulletins/2010/November/2010NO
VSUP2.pdf the terms in the glossary are 'ones for which there is not a
consistent definition, so for the purposes of fairness for all students,
definitions are provided'.

Season's greetings

I hope that everyone has a safe and enjoyable break. The first year of
introducing a new study design is demanding, and I know that many people
will be working over the holidays to provide the best opportunities for
their students. But make certain that there is plenty of time you. 

I'm finishing work mid next week and will be returning on 17 January. 

Regards

Paula

Paula Christophersen

ICT Curriculum Manager

VCAA

41 St Andrews Place

EAST MELBOURNE 3002

(03) 9651 4378

________________________________

From: sofdev-bounces at edulists.com.au
[mailto:sofdev-bounces at edulists.com.au] On Behalf Of Don Morelli (Optus)
Sent: Wednesday, 15 December 2010 7:15 AM
To: 'Year 12 Software Development Teachers' Mailing List'
Subject: Re: [Year 12 SofDev] Validation naming

I would agree with Brett that existence checking is actually to test if
the input exists(i.e. null). This has always been the definition as far
as I am aware. Again I agree with Brett that testing against a limited
list is an extension of what we normally would say is range checking
(checking against a range of values). If the application is checking to
see that a file exists, you are still comparing a filename against a
list of filenames (limited list). It does not matter if the actual
command to do it has the word "exist" as part of it (fileexists or
something like that).

However, Mark's point WE NEED A GLOSSARY of accepted definitions is
vital and I don't understand why it can't happen. It  would at the least
ensure that the examiners are using terms where they and teachers have
the same understanding as to what they mean. The more subjective type of
definitions, based on our own understandings of terms, only
disadvantages students.

Paula, we know that you monitor the lists so why can't we have a list of
definitions?

Cheers and merry Christmas

Don

From: sofdev-bounces at edulists.com.au
[mailto:sofdev-bounces at edulists.com.au] On Behalf Of Mark KELLY
Sent: Tuesday, 14 December 2010 12:00 PM
To: Year 12 Software Development Teachers' Mailing List
Subject: [Year 12 SofDev] Validation naming

Hi campers.  A little audience participation question. Validation types
in the study design are:

*	existence checking
*	range checking
*	type checking

The 2010 SD exam <http://postmortems/2010sd/SD2010exam.htm#c4>  decided
to muddy the waters by describing these validation tests:

Existence - to make sure that the number entered exists on Medicare's
database
Null - to make sure something has been entered

Now, I've always read "existence" as "has a value been entered?" (like
"Null" in the exam question).

How many of you good folk refer to existence testing as "existence in a
limited list", and how many would equate existence testing as null
testing?

If you agree that the exam's terminology is unconventional, I am a bit
concerned about it being used in an exam where it could confuse students
who were taught the conventional interpretation.

Now I'm even doubtful about what the study design means by "existence
checking" - does it mean "null checking"?

Have a happy winding-down time, if you're luck enough to have one!

-- 
Mark Kelly
ICT Manager
Reporting Manager
IT Learning Area Manager

McKinnon Secondary College
McKinnon Rd McKinnon 3204
Victoria, Australia
Direct line / Voicemail: +613 8520 9085
Fax +613 9578 9253
kel at mckinnonsc.vic.edu.au

VCE IT Lecture Notes: http://vceit.com
Moderator: IT Applications Edulist

I scream a lot to make myself hoarse. I undress to make myself bare. I
throw stones at myself to make myself duck.

Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20101216/69456395/attachment.html 