[Year 12 SofDev] Pseudocode standards
Russo, Frank R
Russo.Frank.R at edumail.vic.gov.au
Wed May 18 15:50:16 EST 2011
Love the Nasty Spiderman reference too funny...I will use that one with my year 11's unit 2 with your permission of course Andrew ?
Frank
[cid:image001.jpg at 01CC1573.47C5F600]
Frank Russo
Leading Teacher - Timetabling & Daily Organiser
Monterey Secondary College
Frankston North, 3200
Phone: 9781-7700
________________________________
From: sofdev-bounces at edulists.com.au [mailto:sofdev-bounces at edulists.com.au] On Behalf Of Andrew Shortell
Sent: Wednesday, 18 May 2011 3:06 PM
To: Year 12 Software Development Teachers' Mailing List
Subject: Re: [Year 12 SofDev] Pseudocode standards
Hi Mark
Before we get too carried away with producing a complex definitive set of constructs I would like you (and everyone else too) to carefully read the examiners' reports since 1991 about the question(s) involving writing pseudo code or reading pseudo code and flowcharts and Nasty spiderman diagrams and match them up to the questions themselves.
Then consider carefully the level at which these questions have had to be pitched to elicit a reasonable spread of results. (an average of 50% of the available marks is nice )
One needs to carefully consider the purpose of VCE
CATs/SACs/projects are very different to exams
My 5c worth (given that the face value is nearly less than the metal in it!)
Andrew
--
Andrew Shortell
mailto:shortell at get2me.net
Heidelberg Teaching Unit
Ph 9470 3403
Fax 9470 3215
On 18/05/11 11:16 AM, "Mark KELLY" <kel at mckinnonsc.vic.edu.au> wrote:
Hi Claudia and all
Is there any news on what pseudocode we can expect to be "standard" in SD exams? Until recently there wasn't even a FOR structure in pseudocode, but it's there now (Q4 in the sample questions) - a good move.
What other structures and syntaxes does VCAA consider appropriate?
Just as the lack of complex structures in flowcharts result in primitive and bulky representations of design, a pseudocode lacking important programming primitives must hamstring the potential of pseudocode-based questions.
I suggest we need some more powerful data and control structures in our pseudocode that better reflect the standards seen in all modern languages.
The exact naming is neither here nor there as long as they're intelligible to everyone...
= for assignment. Why do we persist with <- when it's not used in any language and is so hard to typeset for printing??
IF-ELSEIF-ELSE-ENDIF (including AND/OR as logical operators)
The three basic loops...
FOR-NEXT
DO-WHILE
LOOP-UNTIL (or REPEAT-UNTIL like last year's exam had)
I'd like pseudocode to be able to declare variables and arrays. It's a vital programming concept...
DECLARE var AS type
DECLARE array(a,b) AS type
Add some decent I/O operators...
INPUT (from keyboard) and READ (from a file)
DISPLAY (onscreen), WRITE (to file) and PRINT (to paper)
OPEN - CLOSE text file
MESSAGEBOX - hell, our language has to be GUI but there's no GUI support in the pseudocode.
One major omission in current pseudocode is the concept of modularity: I've never seen a subprogram or function call.
We could really improve the power and reality of algorithms by allowing modularity with
CALL subprogram(parameters)
SUBPROGRAM(parameters)-END SUBPROGRAM
FUNCTION(parameters)-END FUNCTION (with RETURN value)
And if the examiners want to introduce new functions all they have to do is explain them before using them. It's not too hard.
Have I left out any important programming concepts you think we could use in pseudocode?
--
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/20110518/0d33f57e/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2623 bytes
Desc: image001.jpg
Url : http://www.edulists.com.au/pipermail/sofdev/attachments/20110518/0d33f57e/image001.jpg
More information about the sofdev
mailing list