Evaluations CS4310 Software Engineering Spring 2001

My posted hours were 4:30-6:00 MW, 2:30-4:00 TR, 9:00-11:00 R, and by appointment. Class was 3:00- 4:20 MW. (The office hourse were misprinted in the syllabus as 3:30-6:00PM on MW. If you found me unavailable from 3:30-4:20 MW, it was because I was teaching the class you should have been attending.) Many students made appointments to meet with me at times other than these, including mornings, afternoons, evenings and weekends. I believe I am quite accommodating to students who make even a minimal amount of effort to see me.

I had two objectives in posting student errors during class. First, it was intended to make you think critically about your own work. We had reviewed errors from published sources, and the class did reasonably well in evaluating those errors. However, the members of the class in general had a difficult time recognizing similar errors in their own work. This is a common difficulty, not just with students. (I admit now, as I did then, that I have a hard time finding my own errors, yet it is essential that I proofread my work. It is essential that you learn to proofread yours.)

My second intent in that review was to let you know that other people were making similar mistakes. When I review writing, any writing, my intent is to improve the quality of the thoughts and the expression of those thoughts. Sometimes there are many comments on papers, and in the past, some students have found this discouraging. This discouragement arises because there are many comments, and students feel that so many comments indicate a lack of progress or ability. Few students realize that I make just as many comments on early versions of my own work and the work of my colleagues. (Ask them. The TA has many versions of the SRS that I wrote, that I corrected, that are every bit as marked as yours.) I had hoped that by showing some of the mistakes your colleagues were making, you would realize that good writing is difficult, that critical review of your writing is necessary, that you are not alone in your need to have other people review your work, and that you need to be honest and critical in your review of your own work and the work of your teammates.

o        In class, I took examples of errors from the student homework and had the class review them. In an effort to avoid embarrassing anyone, the work was presented anonymously, and examples were extracted from work turned in from every team, including examples from my own work. Short of a team admitting that a particular example came from its report, it would be very difficult for other students to associate that example with any team or individual. I tried to keep the review lighthearted and focus attention on the examples, not the students. I am sorry that you took offense at this. My intent was to draw your attention to problems the class as a whole was having with technical writing.