Course Documents
     Main Page
     Contact Information
     Course Announcement
     Schedule and Syllabus
     Course Participants
     Discussion Forum
     Swiki Chat Area
     Lecture Material
     Independent Research
     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
HW 5 by Jun Chen and Sarah Kim-Warren

1.1 What did you find interesting about the article?

The idea of embedding critiques in design environment is interesting and useful itself. We like the idea of having three different kinds of critiquing mechanisms since the problem is so complex that it is realistic to focus on some aspects rather than all aspects at one point of time. Similarly, we agree very much with the point that computer-based critiquing systems are most effective when they are embedded in domain-oriented design environment. It is certainly wonderful if we have a generic solution for all design environments. But, the truth is often that when it is too generic it becomes not useful.

1.2 What did you find not interesting about the article?


2.What do you consider the main message of the article?

For a complex problem, not only constructing a solution but also defining the problem is a problem. Embedding critics in design environments helps understanding the problems incrementally, identifying breakdown processes, and finding the solution at the end.

3.Are themes discussed in the article which you would like to know more about?

There are some other systems where feedback is given back to the user. A simple example is that WORD uses red line under the word to warn users that this might be a wrong spelling. What is the difference between the critiquing and the feedback if we ignore the complexity of the problem?

4.Do you know of other papers, ideas, and systems which are closely related to.


5.1 What does the article say about design?

For complex problems, design is not an easy task. Instead, it is an evolving process. Computer-based critiquing can help designers to evaluate their solutions and improve them.

5.2 What does the article say about learning?

For a complex problem, defining the problem is a problem. The whole process of constructing a solution for the problem is also a process for designers to learn the problem. Often many design participants contribute various design knowledge because individual comes from different domains.

5.3 What does the article say about collaboration?

For complex problems, there is no single person who knows all. So, constructing a solution has to be collaborative work. The Catalog component in HYDRA shows one kind of collaboration.

5.4 What does the article say about innovative media support for these activities?

Computer-based critiquing can support design, learning, and collaboration.

6.Do you have any ideas how this research could / should be extended based on your own knowledge and experience?

This paper did not talk about the situation where multiples rules are broken at the same time. In the simplest case, these rules are independent from each other. Then in which order shall we present these problems to the designer? What if there are dependencies or conflicts among these rules? The situation could become very complicated. This probably could be some future work.

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