Overall

• What is the best feature of this course?
  • Instructor.
  • All the patterns we learned about.
  • Useful.
  • The knowledge gained is very useful.
  • Homework.
  • Question & Answers and HW.
  • Learning Pattens.
  • Learning the new patterns concepts, they were distilled into slides very well.
  • Subject matter, plus in Java. Also liked: Quick assignment feedback; On-line solutions when we got stuck, or just to see how you did it.
  • Lots of code.
  • The course has too many patterns & too many assignments. I expect the Prof. to teach only important patterns & then devote half the time on teaching Java in class which will use for the assignments. E.g., some of the homework were done in Swing, so I expect Prof to cover that part in class. In short, it would be a great course if Prof. mixes this ``DPJ'' with his previous ``Advanced Course in Java''.
  • Practical application of the course.
  • Right mix of theory and practice.
  • Assignments.
  • All in all a great course!
  • Interaction in class.
  • Context.
  • A new subject.
  • Solid OO Design concepts.

• What is the worst feature of this course?
  • Textbook.
  • I thought that the textbook was very often difficult to understand.
  • Textbook.
  • Text.
  • Too much homework.
  • Too much non patterns related Java coding.
  • Number of assignments and the workload.
  • Some weeks prog. assign. got up to 7.
  • Offered off campus.
  • Too many patterns to digest.
  • Homework.
  • Homework requires too much time in some cases.
  • Again homework! Note: Inspite of my repeated mention of homework as a problem, the matter was very good. I enjoyed this course fully. and not regret taking it at all! Good luck with future offerings of this course.

• What would you change about this course?
  • Change order of patterns, add inter-section links for patterns.
  • Move it downtown.
  • Downtown.
  • Project based set-of-patterns.
  • Make less number of assignment.
  • I'd make the homeworks more related to each other. I'd eliminate all GUI coding.
  • Another textbook?
  • Start offering on campus.
  • Location.
  • Decrease number of patterns.
  • Clarify problem statement for some assignments.
  • Better text.
  • Teach less patterns or balance homework better.
  • Timing.
  • Predictably, being about more of a balance between class work & home work.

• What would you add to this course?
  • More discussion on patterns in Java built-in utilities.
  • UML introduction and usage in each pattern.
  • More examples on each pattern.
  • I'd provide the ``grunt'' Java code, such as the low and high quality stacks, then let the students code the specific pattern that use them, rather than having to provide whole solutions.
  • 1 Lecture on UML. More classroom explanations using diagram and UML.
  • More focus on java.net + java.beans.
  • Teach advanced features of Java.
  • Better text.
  • Covering textbook examples in some cases.
  • A project.
  • Nothing.

• What would you remove from this course?
  • A better text.
  • Study less number of patterns.
  • I'd eliminate GUI-related code or provide it as part of the exercise. I have taken the Java course over a year ago and forgot much of the GUI related API. At times it was difficult to see the ``forest for the trees'' meaning I was coding the solution too much and not focusing on the pattern I was implementing.
  • Some of the trivial patterns, e.g., some of the earlier patterns covered during the first half of the course.
  • Keep it the same.
  • It will be good as it is.

Thank you for your answers.