Another work page2

Last modified by Jason Cockerham on 2010/09/20 10:53

 

     Pretty much like last time, but this time we have some sort of format. The format is listed below.

 I just selected Learner-centered design as our topic without asking you, because it will be most likely done during Monday. However, please do this as soon as possible.

Format:

  1. selection process: choose one of the design methodologies (not yet taken by another group) from the list (and mark it as chosen by editing this wiki page — “first come / first served”)
  2. do research (read papers, interview software designers, analyze existing systems—hint: the abovementioned wiki site contains references to resources) and answer the following specific questions for your chosen design methodology:
  3. define it
  4. characterize it
  5. identify strengths
  6. identify weaknesses
  7. identify domains and problems for which your chosen design methodology is
    1. appropriate
    2. not appropriate
  8. argue why is design methodology is important (suited) or not important (suited) for human-centered computing

Jason Cockerham - 3, 4)  Learner centered design is design with learners in mind.  Learners come from a lot of different backgrounds, so the design has to reflect that and be adaptable.  Learners might have strong motivation or no motivation at all, so a program made for learners needs to motivate them.  Tools need to change as a learners knowledge increases.  5, 6)  The weakness of this idea of designing is on the designer's side.  The designer has to go the extra mile to make a program that can adapt to different learning styles and one that motivates the learner, so it's harder on the designer.  This weakness is a strength on the learner's side.  A program can be used by many learners with different learning styles and the task of learning a program is made easier given the right motivation.

Tags:
Created by MyungHo Kim on 2010/09/18 12:51

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 2.7.1.${buildNumber} - Documentation