A4MichaelMinerva
Last modified by Hal Eden on 2010/08/20 11:32
A4MichaelMinerva
To-Do
- which was the most interesting idea/concept you learned from the article?
- articulate what you did not understand in the article but it sounded interesting and you would like to know more about it
- compare the ideas/argumentation/functionality for DODEs with the EDC demonstration given in the class meeting on February 11!
- one major objective of the article, the commentaries, and the reply is to understand the best role distribution between humans and computers in joint human-computer systems (or socio-technical environments)! Comment of this issues from your personal experience!
- Most interesting idea/concept
- I found the general idea of creating highly specialized design environment intriguing. I very much liked the idea of creating systems that are dynamic enough that the user is able to mold his own design environment, instead of being constrained by the system designer's notion of what is best for the end user designer.
- What you did not understand
- I did not get a good idea of what a DODE system would look like in action. I did not get a feel for what sort of concrete ways would a designer be able to mold their own design environment.
- Compare DODE with EDC
- DODEs differ from error detecting code mainly it its focus. The point of a DODE is not simply to pick out errors that a designer may have made in their choice, but to be readily adaptable to the end-user and specific to the domain of the designer.
- Comment on the best role distribution
- I feel that the best role-distribution in this sort of system is one that is weighted more toward the human side. It has been my experience that in many situations computer interaction is forced about users. For example, computerized telephone answering systems are often used to cut down on the cost of paying human customer service representatives. While this is a good use of computer-human interaction it becomes an impediment and announce for the user when they have no option to skip past the AI receptionist when they are sure that it can be of no help to them. This comes back to the issue of customizability and the importance of not make this issue a one size fits all solution.