<HTML>
<HEAD>
<TITLE>Re: [Year 12 IT Apps] When to establish evaluation criteria?</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>While I agree with you Mark, I can also see the logical extension of “Designing” the criteria.<BR>
<BR>
Personally I set eval criteria as part of analysis because they are a result of what the client wants – they will indicate when we have achieved what the client wants. The analysis drives what we will do in design. I do not design until I knowwhere I am going with it – and satisfying the eval criteria is a part of that.<BR>
<BR>
Andrew<BR>
<BR>
-- <BR>
-- <BR>
</SPAN></FONT><FONT SIZE="4"><FONT FACE="Apple Casual"><SPAN STYLE='font-size:14pt'>Andrew Shortell<BR>
</SPAN></FONT></FONT><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<a href="mailto:shortell@get2me.net">mailto:shortell@get2me.net</a> <BR>
Heidelberg Teaching Unit<BR>
Ph 9470 3403<BR>
Fax 9470 3215<BR>
<BR>
<BR>
<BR>
On 12/09/11 9:11 AM, "Mark KELLY" <<a href="kel@mckinnonsc.vic.edu.au">kel@mckinnonsc.vic.edu.au</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Thanks for the clarification, Paula, but it still doesn't sound right to me. <BR>
<BR>
If the functional requirements are established during analysis, why would the evaluation criteria have to wait until design began? They are not contingent upon the chosen <B>method</B> of achieving the functional requirements.<BR>
<BR>
They are a logical and necessary consequence of the choice of functional requirements.<BR>
<BR>
On 12 September 2011 08:58, Christophersen, Paula P <<a href="christophersen.paula.p@edumail.vic.gov.au">christophersen.paula.p@edumail.vic.gov.au</a>> wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><FONT COLOR="#1F497D">Dear colleagues<BR>
<BR>
The problem-solving methodology states that establishing evaluation criteria is an activity in the Design stage (pp 16 and 17 of the study design).<BR>
<BR>
Regards<BR>
Paula<BR>
<BR>
</FONT><BR>
<FONT COLOR="#1F497D">Paula Christophersen<BR>
ICT Curriculum Manager<BR>
Victorian Curriculum and Assessment<BR>
Authority<BR>
(03) 9651 4378 <tel:%2803%29%209651%204378> <BR>
<BR>
</FONT><BR>
</SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'><B>From:</B> <a href="itapps-bounces@edulists.com.au">itapps-bounces@edulists.com.au</a> [<a href="mailto:itapps-bounces@edulists.com.au">mailto:itapps-bounces@edulists.com.au</a>] <B>On Behalf Of </B>Travis Parker<BR>
<B>Sent:</B> Monday, 12 September 2011 8:54 AM<BR>
</SPAN></FONT><SPAN STYLE='font-size:11pt'><BR>
<B>To:</B> Year 12 IT Applications Teachers' Mailing List<BR>
<B>Subject:</B> Re: [Year 12 IT Apps] When to establish evaluation criteria?<BR>
<BR>
<BR>
<FONT COLOR="#1F497D">A lot of them (And even the textbook I think??) have evaluation criteria created during the design phase, but your questions doesn’t really specify……<BR>
<BR>
<BR>
<BR>
<BR>
<BR>
</FONT></SPAN><FONT SIZE="2"><SPAN STYLE='font-size:10pt'><B>From:</B> <a href="itapps-bounces@edulists.com.au">itapps-bounces@edulists.com.au</a> [<a href="mailto:itapps-bounces@edulists.com.au">mailto:itapps-bounces@edulists.com.au</a>] <B>On Behalf Of </B>Mark KELLY<BR>
<B>Sent:</B> Monday, 12 September 2011 8:48 AM<BR>
<B>To:</B> Year 12 IT Applications Teachers' Mailing List<BR>
<B>Subject:</B> [Year 12 IT Apps] When to establish evaluation criteria?<BR>
</SPAN></FONT><SPAN STYLE='font-size:11pt'> <BR>
Hi all. I'm checking a commercial exam I bought... I'm doubtful about its answer to one question<BR>
<BR>
At which stage should criteria should be established?<BR>
A. Analysis?<BR>
B. Design?<BR>
C. Development?<BR>
D. Evaluation?<BR>
<BR>
The suggested answer is B, but should they not be developed in conjunction with functional requirements during analysis?<BR>
</SPAN></FONT></BLOCKQUOTE></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT>
</BODY>
</HTML>