[Year 12 IT Apps] When to establish evaluation criteria?
Andrew Shortell
shortell at get2me.net
Mon Sep 12 21:19:42 EST 2011
However
Who does evaluation? The users the client the workers. Not the
designer, not the coder, not the analyst, etc.
Criteria are all about : does it do what was identified as needing doing?
Does it fix the identified problem? / needs? /wants? /desires (written and
contracted)? /whatever it was that got the analyst in there in the first
place?
you must set the evaluation criteria before you start the design otherwise
you will only evaluate the solution you create/design you might not be
evaluating a solution to the problem that you identified in the analysis.
We often tend to create test data that tests what we have designed, not
necessarily test key decision points- we have all (I am sure) left out key
decisions (in our design) because we worked on the design without
referencing the analysis often enough and because our test data and our
evaluation criteria were created after the solution and so only
tested/evaluated the solution that we made - ---
So, simply put, in reality, we create our evaluation criteria, our test
data, and our client acceptance criteria before we start designing so that
we do not waste time in the design phase working on things that do not fit
with the analysis stage. All design works towards satisfying the
tests/evaluation/acceptance. At every step.
If the analysis stage does not identify what constitutes a solution for the
client then analyse properly. There is no point in doing anything if you do
not understand what the client wants unless of course you work for free or
you are an artist (see Blue Poles as a good example would that work as a
solution in a client focussed environment?).
I do NOT work for free when creating things for clients. I also do not allow
for wastage that is avoidable so do not quote above the needs identified in
the analysis; thus I ensure that I identify what they want.
Andrew --
It must be bedtime so off my hobby horse. Good night
--
--
Andrew Shortell
mailto:shortell at get2me.net
Heidelberg Teaching Unit
Ph 9470 3403
Fax 9470 3215
On 12/09/11 8:27 PM, "Branson, Steven S"
<branson.steven.s at edumail.vic.gov.au> wrote:
> I assume ³criteria² means criteria for evaluation- not worded well. My thought
> is that analysis is all about gaining an understanding of the problem and what
> the client wants. You will have these in the back of your mind, during the
> analysis process. These will cover what you hope to produce and hence possible
> criteria, but they will be broad. However until you start designing the
> solution you can¹t develop a full set of criteria that is detailed enough to
> evaluate the solution.
>
>
> Steven Branson
>
>
>
>
> From: itapps-bounces at edulists.com.au [mailto:itapps-bounces at edulists.com.au]
> On Behalf Of Mark KELLY
> Sent: Monday, 12 September 2011 8:48 AM
> To: Year 12 IT Applications Teachers' Mailing List
> Subject: [Year 12 IT Apps] When to establish evaluation criteria?
>
> Hi all. I'm checking a commercial exam I bought... I'm doubtful about its
> answer to one question
>
> At which stage should criteria should be established?
> A. Analysis?
> B. Design?
> C. Development?
> D. Evaluation?
>
> The suggested answer is B, but should they not be developed in conjunction
> with functional requirements during analysis?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/itapps/attachments/20110912/b9add7e3/attachment-0001.html
More information about the itapps
mailing list