[Year 12 SofDev] Evaluation Report Template

Tue Aug 16 09:43:30 AEST 2016

Hi Ben

I like the idea of a template for a report. I have struggled with my
students in this area this year to get the level of detail required and all
content included.

One change I would make would be to get one heading for each descriptor to
ensure everything is included there and put what you want as statements
into point form. I have found sentences and paragraphs ensure students
don't read it and therefore miss content.

Here's what I have suggested to my students and they are submitting
tomorrow.

Written report (in significant detail) including:

   1. Testing table - Thorough testing with expected and actual output.
   Show what's working and what's not.
   2. Preparation and conduct of useability test - Discuss how you prepared
   and conducted your survey for testing. Discuss how you conducted your test.
   Discuss your users. Discuss how your surveys met the user's requirements.
   3. Results of useability testing - Discuss the results of the
   surveys/tests. Include evidence in the appendices. Discuss what the results
   tell you.
   4. Modifications to software solution - Discuss the necessary
   modifications you will need to make to your solution as a result of your
   useability testing.
   5. Strategies for meeting evaluation criteria - Propose strategies for
   evaluating your software solution against the evaluation criteria. How is
   it efficient and effective? Refer to the Glossary in the Study Design.
   6. Software solution meets requirements - Explain how your solution
   meets functional and non-functional requirements. How is it efficient and
   effective?

Again I asked them to submit a copy of the Criterion 7 rubric with their
submission and tick off where they believe they will meet each descriptor.
I also got them to write down their estimate of a score they believe they
will get for each descriptor.

When they submitted Criteria 5 and 6 I sat down with each student to run
the program. This enabled me to see what worked and what didn't and ask
questions as well as take notes. It aided in the marking. Time consuming
but worthwhile.

Regards

Phil.

On Tue, Aug 16, 2016 at 9:13 AM, Baas, Benjamin B <
baas.benjamin.b at edumail.vic.gov.au> wrote:

> Hi Andrew,
>
>
>
> Thank you for the feedback I will make some changes based on your
> suggestions for efficiency and effectiveness.
>
>
>
> And thanks for the pick up on Page 5, I think I might have misinterpreted
> a criteria. That’s why I send this type of stuff out to the list.
>
>
>
> Cheers,
>
>
>
> Ben.
>
>
>
> *From:* sofdev-bounces at edulists.com.au [mailto:sofdev-bounces@
> edulists.com.au] *On Behalf Of *Andrew Shortell
> *Sent:* Monday, 15 August 2016 7:43 PM
> *To:* Year 12 Software Development Teachers' Mailing List <
> sofdev at edulists.com.au>
> *Subject:* Re: [Year 12 SofDev] Evaluation Report Template
>
>
>
> hi Ben
>
> I like it
>
>
>
> thanks
>
>
>
> one of the things that i stress with  my students is never use efficiency
> and effectiveness in the same sentence
>
> Too many people confuse them or only write about one and not the other
>
>
>
> I also ask my students to write about teh three aspects of efficiency time
> cost effort and not about efficiency in general as they often do not
> mention time cost effort
>
>
>
> Note also at the top of P 5 you relate it to the design but in the next
> paragraph to the program
>
> I think it shoudl all be about the program here.
>
>
>
> I will certainly be giving this to my students (slightly modded)
>
>
>
> Thanks again
>
>
>
> Andrew
>
>
> Andrew Shortell
>
> Educator
>
> CRC Melton
>
>
>
>
>
> shortell at get2me.net (This List)
>
> @acsbear8 (twitter)
>
>
>
>
>
>
>
>
>
>
>
> On 15 Aug 2016, at 10:26 am, Baas, Benjamin B <
> baas.benjamin.b at edumail.vic.gov.au> wrote:
>
>
>
> Hi all,
>
>
>
> I have created a template I might give my students for reporting on the
> testing and evaluations the students have done on their program. I was just
> wondering if any can have a look at it. I am keen to get people’s opinions
> on the Usability section.
>
>
>
> Cheers,
>
>
>
> Ben.
>
>
>
> *Benjamin Baas*
>
> <image001.png> *Alkira Secondary College*
>
>
>
> 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 Training.
>
>
> _______________________________________________
> http://www.edulists.com.au - FAQ, Subscribe, Unsubscribe
> IT Software Development Mailing List kindly supported by
> http://www.vcaa.vic.edu.au - Victorian Curriculum and Assessment
> Authority and
> http://www.vcaa.vic.edu.au/vce/studies/infotech/softwaredevel3-4.html
> http://www.vitta.org.au  - VITTA Victorian Information Technology
> Teachers Association Inc
> http://www.swinburne.edu.au/ict/schools - Swinburne University
>

-- 
Phil Feain

*Head of eLearning*
*Head of Information Technology*
*St. Kevin's College*

-- 
This email message does not represent the view of St Kevins College, is 
intended only for the addressee(s) and contains information that may be 
confidential and/or copyright. If you are not the intended recipient please 
notify the sender by reply email and immediately delete this email. Use, 
disclosure or reproduction of this email by anyone other than the intended 
recipient(s) is strictly prohibited. No representation is made that this 
email or any attachments are free of viruses. Virus scanning is recommended 
and is the responsibility of the recipient.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20160816/1cd2398a/attachment-0001.html 