[Year 12 SofDev] sofdev Digest, Vol 134, Issue 36

Fri May 20 16:04:34 AEST 2016

The glossary states
Design principles are accepted characteristics that contribute to the functionality and appearance of solutions.
In this study the principles related to functionality are useability, including robustness, flexibility and ease of use, and accessibility, including navigation and error tolerance.
Design principles related to appearance are alignment, repetition, contrast, space and balance.

As long as the layout diagrams etc show a clear difference in functionality, then they're able to get into a higher band, most of mine so far have clear differences in their ease of use and error tolerance - both very achievable through choosing different controls and splitting a cramped screen into several smaller screens.

Damien ATKINSON-BUCK

Head of Learning Area: Technology/Arts

Ivanhoe Grammar School

PO Box 91 The Ridgeway

Ivanhoe Victoria

3079 Australia

e: Damien.ATKINSON-BUCK at ivanhoe.com.au

p: +61 3 9490 3848

w: www.ivanhoe.com.au

-----Original Message-----
From: Heath, Natalie [mailto:Natalie.Heath at marcellin.vic.edu.au]
Sent: Friday, 20 May 2016 3:47 PM
To: Year 12 Software Development Teachers' Mailing List <sofdev at edulists.com.au>
Subject: Re: [Year 12 SofDev] sofdev Digest, Vol 134, Issue 36

Just be careful - if they are only designing appearance, the highest band that point can get is 1-2... where it refers to "appearance OR functionality". All of the others in bands 3-10 refer to "functionality AND appearance" (except for the 3-4 band which oddly refers to "appearance and functionality"... maybe it's because the higher bands are putting the emphasis on functionality?)

Natalie

Mrs Natalie Heath

ICT Learning Coordinator

Marcellin College

160 Bulleen Road

Bulleen VIC 3105 Australia

T +61 3 9851 1698

ABN 77 413 001 496

marcellin.vic.edu.au

twitter.com/Marcellin

-----Original Message-----

From: sofdev-bounces at edulists.com.au<mailto:sofdev-bounces at edulists.com.au> [mailto:sofdev-bounces at edulists.com.au] On Behalf Of Nayak, Jayanti S

Sent: Friday, 20 May 2016 2:16 PM

To: sofdev at edulists.com.au<mailto:sofdev at edulists.com.au>

Subject: Re: [Year 12 SofDev] sofdev Digest, Vol 134, Issue 36

Hi,

I agree with Damien. I am getting students to create three User Interfaces. Time being a constraint, it is difficult to get them to think & do all the permutations & combinations.

---------------------------------------------------------------------------------------------------

Ms. Nayak,

Info Tech Teacher,

Sunbury College, 30, Race Course Road,

Sunbury - 3429.

________________________________________

From: sofdev-bounces at edulists.com.au<mailto:sofdev-bounces at edulists.com.au> [sofdev-bounces at edulists.com.au] on behalf of sofdev-request at edulists.com.au<mailto:sofdev-request at edulists.com.au> [sofdev-request at edulists.com.au]

Sent: Friday, 20 May 2016 11:47 AM

To: sofdev at edulists.com.au<mailto:sofdev at edulists.com.au>

Subject: sofdev Digest, Vol 134, Issue 36

Send sofdev mailing list submissions to

        sofdev at edulists.com.au<mailto:sofdev at edulists.com.au>

To subscribe or unsubscribe via the World Wide Web, visit

        http://www.edulists.com.au/mailman/listinfo/sofdev

or, via email, send a message with subject or body 'help' to

        sofdev-request at edulists.com.au<mailto:sofdev-request at edulists.com.au>

You can reach the person managing the list at

        sofdev-owner at edulists.com.au<mailto:sofdev-owner at edulists.com.au>

When replying, please edit your Subject line so it is more specific than "Re: Contents of sofdev digest..."

Today's Topics:

   1. Re: Folio of Designs (ATKINSON-BUCK, Damien)

----------------------------------------------------------------------

Message: 1

Date: Fri, 20 May 2016 01:47:47 +0000

From: "ATKINSON-BUCK, Damien" <Damien.ATKINSON-BUCK at ivanhoe.com.au<mailto:Damien.ATKINSON-BUCK at ivanhoe.com.au>>

Subject: Re: [Year 12 SofDev] Folio of Designs

To: "Year 12 Software Development Teachers' Mailing List"

        <sofdev at edulists.com.au<mailto:sofdev at edulists.com.au>>

Message-ID:

        <3E17F75B626F994B87071361E4FD0D74C7B94D31 at MICKEY-MBX.igs.vic.edu.au<mailto:3E17F75B626F994B87071361E4FD0D74C7B94D31 at MICKEY-MBX.igs.vic.edu.au>>

Content-Type: text/plain; charset="us-ascii"

Hi Lisa,

Sounds good. The assessment criteria says to compare 2 or 3 distinctive design ideas, I personally am getting them to go for 3, just to be safe. But I'm getting them to just compare the interfaces of the 3, not the lower levels, which I think is where you're heading.

The more I think about it though, the more I like where you're heading getting them to compare more than the interfaces, but struggling with what differences to compare with the processing level!

If you were to split it up and compare at each level,

-          Interface layer

o   Compare in terms of efficient and effective usability

-          Data store layer

o   Compare data storage and data access options

?  Database vs flat file

?  Download XML vs locally stored

-          Processing layer

o   realistically what would be the difference to pseudocode if we get the data from a database or locally stored? They would both say GET data or something, not GET Data from xyz storage system

o   Seems too simplistic to do comparisons of different selection methods

o   Possibly could use this to compare accessing data via stored procedures versus a standalone module, I vaguely remember someone saying that we shouldn't be putting the code in stored procedures etc as that's reducing the need for the OO language too much.

I like where you're going with the client justification - are you thinking something like a sales pitch "this design is more efficient because the radio buttons makes data entry easier" or "this design is more effective in its user friendliness because....." ?

Cheers

Damien

Damien Atkinson-Buck

Head of Learning Area: Technology/Arts

<http://>

[http://www.ivanhoe.com.au]<http://www.ivanhoe.com.au/>

The Ridgeway, Ivanhoe VIC 3079 Australia

p. +61 3 9490 3848

e. damien.atkinson-buck at ivanhoe.com.au<mailto:damien.atkinson-buck at ivanhoe.com.au>

w. www.ivanhoe.com.au<http://www.ivanhoe.com.au<http://www.ivanhoe.com.au%3chttp:/www.ivanhoe.com.au>>

[cid:image003.png at 01D1B28B.AF26AA00]<http://www.facebook.com/IvanhoeGrammarSchool> [cid:image004.png at 01D1B28B.AF26AA00] <http://twitter.com/ivanhoegrammar>

From: Lisa Kerekes [mailto:Lisa.Kerekes at donvale.vic.edu.au]

Sent: Thursday, 19 May 2016 6:03 PM

To: Year 12 Software Development Teachers' Mailing List <sofdev at edulists.com.au<mailto:sofdev at edulists.com.au>>

Subject: Re: [Year 12 SofDev] Folio of Designs

Love the idea of a design sprint Damien! Thanks for sharing :D

Re: efficient interface designs - could compare two form designs - which is faster and easier to fill out? Eg use of a dropdown list instead of a textbox; a calendar VS typing in a day, month and year. Could your students evaluate their designs, then show the client and explain/justify their choice?

My approach to the Design Folio: I asked students to choose one relevant tool to represent each of these conceptual layers. Do this for each of their two Design Concepts.

-          Interface layer

-          Processing layer

-          Data store layer

I tried to limit them to just using 3 tools per Design Concept (one tool for each layer). This would allow them to outline each concept's visual and structural elements, and provide differentiation between the two concepts.

What do you think about this way of breaking it down?

Lisa Kerekes

Secondary Teacher

Phone: (03) 9844 2471 Ext: 266

[cid:image005.jpg at 01D1B28B.AF26AA00]

From: sofdev-bounces at edulists.com.au<mailto:sofdev-bounces at edulists.com.au<mailto:sofdev-bounces at edulists.com.au%3cmailto:sofdev-bounces at edulists.com.au>> [mailto:sofdev-bounces at edulists.com.au] On Behalf Of ATKINSON-BUCK, Damien

Sent: Tuesday, 17 May 2016 12:14 PM

To: Year 12 Software Development Teachers' Mailing List <sofdev at edulists.com.au<mailto:sofdev at edulists.com.au<mailto:sofdev at edulists.com.au%3cmailto:sofdev at edulists.com.au>>>

Subject: Re: [Year 12 SofDev] Folio of Designs

Hi Ben,

            The way I looked at it was they should have at least 3 designs for the input and the output screens, and had then see if they could annotate some good points and bad points about each (considering different devices etc.) Once they sorted that out, I asked for object descriptions, data dictionaries and psuedocode for the design they eventually chose.

I did a little experiment to get the ball rolling with them and introduced Google Design Sprint concepts - I showed the video here<http://techcrunch.com/2013/10/23/inside-a-google-ventures-design-sprint/>, then gave them 4 minutes to come up with 3 input designs - 2 of which had to be for different devices and again for the output. The time limit worked amazingly, they almost all got 3 done. I then gave them a bit longer to finish off and flesh out any of those a bit more before taking them back to the client to view and discuss...... this part makes me nervous on how to mark their evaluation of efficient and effective designs, as it's realistically the client's choice.

Hoping I'm on the right track!

Damien Atkinson-Buck

Head of Learning Area: Technology/Arts

<http://>

[http://www.ivanhoe.com.au]<http://www.ivanhoe.com.au/>

The Ridgeway, Ivanhoe VIC 3079 Australia

p. +61 3 9490 3848

e. damien.atkinson-buck at ivanhoe.com.au<mailto:damien.atkinson-buck at ivanhoe.com.au<mailto:damien.atkinson-buck at ivanhoe.com.au%3cmailto:damien.atkinson-buck at ivanhoe.com.au>>

w. www.ivanhoe.com.au<http://www.ivanhoe.com.au<http://www.ivanhoe.com.au%3chttp:/www.ivanhoe.com.au>>

[cid:image003.png at 01D1B031.F95442B0]<http://www.facebook.com/IvanhoeGrammarSchool> [cid:image004.png at 01D1B031.F95442B0] <http://twitter.com/ivanhoegrammar>

From: Ben Hines [mailto:b.hines at ccg.vic.edu.au]

Sent: Tuesday, 17 May 2016 11:37 AM

To: Year 12 Software Development Teachers' Mailing List <sofdev at edulists.com.au<mailto:sofdev at edulists.com.au<mailto:sofdev at edulists.com.au%3cmailto:sofdev at edulists.com.au>>>

Subject: [Year 12 SofDev] Folio of Designs

Hi all,

My students are up to the Folio of Designs in SD at the moment.

I'm just wondering what should be done in the 2 or 3 designs compared to what should be left to the detailed design (of the chosen one).

Surely the algorithm in Pseudocode can be left to the detailed design (since there wouldn't be able to be too much difference in design here, in order to the meet the req's of their SRS).

But then what should the 2 or 3 designs include? Mock ups? Data Dictionaries? I'm not really sure.

Thanks all.

Ben

This e-mail is intended for the use of the named individual or entity and may contain confidential and privileged information. Any dissemination, distribution or copying by anyone other than the intended recipient of this e-mail is strictly prohibited. If this e-mail has been received in error, then please notify Christian College or the author of this email immediately and destroy the original message. We have made every attempt to ensure this e-mail message is free from computer viruses however the attached files are provided on the basis that the user assumes all responsibility for use of the material transmitted. Views, opinions, etc. expressed reflect those of the author and not Christian College nor its associated companies and campuses which includes Eden Quality Services Pty Ltd.

________________________________

Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering.

http://www.mailguard.com.au

Privacy, Virus and Copyright Warning

The information contained in this electronic message (e-mail), and any files transmitted with it:

* is intended for the named recipients only. If you have received this in error, please advise the sender and delete it and any copies immediately;

* Any personal information in this email must be used in accordance with the Privacy Act 1988 and this always applies even if it has been sent to you in error.

* represents the views of the sender and does not necessarily represent the views or formal advice of Ivanhoe Grammar School;

* may be subject to Copyright, so no further use should be made of it without the author's permission.

The School does not represent or warrant that the email or any files attached do not contain errors or are free from computer viruses or other defects nor does it accept responsibility for any loss or damage resulting directly or indirectly from the use of the email or any attached files.

Privacy, Virus and Copyright Warning

The information contained in this electronic message (e-mail), and any files transmitted with it:

* is intended for the named recipients only. If you have received this in error, please advise the sender and delete it and any copies immediately;

* Any personal information in this email must be used in accordance with the Privacy Act 1988 and this always applies even if it has been sent to you in error.

* represents the views of the sender and does not necessarily represent the views or formal advice of Ivanhoe Grammar School;

* may be subject to Copyright, so no further use should be made of it without the author's permission.

The School does not represent or warrant that the email or any files attached do not contain errors or are free from computer viruses or other defects nor does it accept responsibility for any loss or damage resulting directly or indirectly from the use of the email or any attached files.

-------------- next part --------------

An HTML attachment was scrubbed...

URL: http://www.edulists.com.au/pipermail/sofdev/attachments/20160520/32fb9f55/attachment.html

-------------- next part --------------