Links
Course Documents
     Register
     Main Page
     Assignments
     Contact Information
     Course Announcement
     Schedule and Syllabus
     Course Participants
     Discussion Forum
     Swiki Chat
     Lecture Material
     Independent Research
     Projects
     Questionnaires
     Previous Course
Swiki Features:
  View this Page
  Edit this Page
  Printer Friendly View
  Lock this Page
  References to this Page
  Uploads to this Page
  History of this Page
  Top of the Swiki
  Recent Changes
  Search the Swiki
  Help Guide
Related Links:
     Atlas Program
     Center for LifeLong Learning and Design
     Computer Science Department
     Institute of Cognitive Science
     College of Architecture and Planning
     University of Colorado at Boulder
(1) to which extent are there "versus" or "and" relationship between them

(2) there are trade-offs associated with each criteria

Trade-offs

• 1 – Simplicity

• Making the interface too simple takes away some of the more useful and powerful features that you could add for more advanced users.

• Simpler programming languages like java are easier to use but not nearly as powerful as languages like c++.

• 2 – Consistency

• Making the interface consistent allows for easier navigation but again this could be restraining and irritating for advanced users. Some common don’ts of interface design is to make the user feel constricted. “Give the user control, don’t control the user.”

• 3 – Usefulness

• Making an interface truly useful and powerful can also make the interface much more complex and less usable.

• One of the goals in good interface design is to make it accessible. The user should have easy access to the software / interface. An example of this is when Flash applications started coming out. They were very useful but it was hard for schools to acquire the Flash software and so a lot of the schools couldn’t use the applications.

• Truly useful and powerful software might not be very easily accessible.

• 4 – Usability

• The only drawback of trying to make an interface usable is that, once again, powerful and useful features might not be included. It’s hard to make an interface useful and usable at the same time.

• 5 – Accessibility

• Accessible software / applications / interfaces might not be as useful as more technologically advanced applications that aren’t easily accessible.

• An example of this could be java applications. They are easily accessible because java applications can run on just about any type of hardware / operating system but don’t have the possibility of being nearly as powerful as applications designed specifically for one type of hardware / operating system.

• 6 – Coherence

• By only adding what the user needs to see you’re limiting your interface to only one type of user. In other words the interface feels generic and therefore the user feels generic. By adding lots of features and extraneous material the user feels like the application is designed for them personally and so it becomes more usable and useful.

• Extra but more powerful features could be added by not making the interface coherent allowing the interface to be more useful, but could also be cluttering and irritating.


(3) apply the criteria to a specific systems (e.g.: our Swiki, or ....)

(4) how is "coherence" related to the reseeding phase in the seeding, evolutionary growth, (3) reseeding model

View this PageEdit this PagePrinter Friendly ViewLock this PageReferences to this PageUploads to this PageHistory of this PageTop of the SwikiRecent ChangesSearch the SwikiHelp Guide