A4AdamMork
Last modified by Hal Eden on 2010/08/20 11:32
A4AdamMork
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
- The DODE's. To me this paper correctly predicted the progression away from formal methods, waterfall methods towards more integrated environments. For example the Interface builder in the xCode development environment for Apple/Iphone development. I also like how it touches on user cooperation with developers, and the important role that they play in making a software system effective and more usable throughout their lifetime.
- What you did not understand
- Why automation of programming is bad, i think that this concept if not properly specified can infringe on the automated programming that something like the FRAMER does. I understand that automated programming can mean having a computer write a program to solve a problem, obviously in its completeness, the computer cant effectively write an entire program to solve a problem given by a human, that is the problem inherent with KBSA's. But some automation is a good thing.
- Compare DODE with EDC
- DODE is simply a programming environment, where EDC is a context aware DODE, which integrates physical environments with computational environments to capture a larger context of what the user is doing.
- Comment on the best role distribution
- The best role distribution is about making the most effective and intuitive use of the computers and technology at our disposal. Making things easier to use and understand not only increases access to these tools, but simplifies them, making them building blocks for more complex abstractions.