[Year 12 SofDev] SD SAT admin info

[Paragreen, Chris J]

… or perhaps they design the useability test during the design stage, but it just doesn’t form part of their assessment for U2O3 …?

From: sofdev-bounces at edulists.com.au [mailto:sofdev-bounces at edulists.com.au] On Behalf Of Esther Andrews
Sent: Wednesday, 2 March 2016 12:56 PM
To: Year 12 Software Development Teachers' Mailing List <sofdev at edulists.com.au>
Subject: Re: [Year 12 SofDev] SD SAT admin info

Perhaps they create the useability CRITERIA in the design stage (U3O2) but the actual method of assessing this criteria can be decided later?

From: sofdev-bounces at edulists.com.au<mailto:sofdev-bounces at edulists.com.au> [mailto:sofdev-bounces at edulists.com.au] On Behalf Of Mark
Sent: Wednesday, 2 March 2016 12:44 PM
To: Year 12 Software Development Teachers' Mailing List <sofdev at edulists.com.au<mailto:sofdev at edulists.com.au>>
Subject: [Year 12 SofDev] SD SAT admin info

Hi,SAT navigators. A quick question.

VCAA's admin info PDF says at the top of p.4 that "Students must present evidence of the useability test that they designed, conducted and documented."

I would have assumed that all design should take place during the design stage in U3O2 - and be assessed as part of U3O2. But the design of the usability test is not included in the design assessment rubric for U3O2.

That means that design of the useability test happens during development in U4O1 and will be assessed in U4O1.

Isn't that contrary to the spirit of the PSM which expects that design should be complete before development begins.

Yes: I know that the new study design acknowledges Agile and says (p.14) that "when creating solutions, this methodology can be applied as a single stage-by-stage problem-solving process or to each iteration of an agile problem-solving process." but Agile does not deliberately plan to design after development begins.

Agile just acknowledges that sometimes circumstances require a solution to return to an earlier stage and start again, e.g. because of technological developments, changes in the market, new client requirements, or changes to legislation that make the current design or solution infeasible.

I can't see a reason why a useability test could not be designed before development begins... if the solution's design is thorough.

I think the useability test could be created during design. Designing anything during development (apart from user documentation, perhaps) does not seem right to me.

But then again determining evaluation criteria during design never felt right either, but that's a different story.

Mark

--

Mark Kelly

mark at vceit.com<mailto:mark at vceit.com>
http://vceit.com

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20160303/abf1c181/attachment.html