student comments

在闭卷考试的时候，我要求同学们把意见和建议也写在卷子上，反馈给TA。 下面是TA 给我的列表，我大略分了类：

They are listed as below. I omit the names. Also I omit the positive comments which just simply say that this class is very good (there are definitely lots of it!)

book 移山之道  (i think a couple of the comments also refer to 梦断代码）

1. The books are not very good. What we are told to read is childish. Not suitable for teaching.
2. "移山之道" is a good. More training from that book should be used in our class.
3. Provide more books so more people can read it.
4. Having a paper based, closed book exam is a bad decision.
5. Some discussion problems at the end of each chapter of the book can be used in class.
6. We spent too much time on I Project and P Project. Should focus more on Team Project.
7. I found the book 移山之道 is good for reading but not for referring, I see many localized dialogues, it maybe better for me to understand, but not to found a specification of definition of something. Besides, there’re not much explicitly emphasized things

项目 Individual Project, Pair Project, homework

1. The difficulty of homework should be decreased a little bit.
2. Should require the students do more documentation.
3. To focus more on the scale and scalability of the program, give some detailed instructions, and really hard projects.
4. I don’t like the project like I Project & P Project, since they give to much attention to the algorithmic aspect of the program, and in a really "unprofessional", way.
5. Should add more check points during the development process.
6. The interface in P Project should be agreed by majority of the students before used.
7. More examples in lectures. Balance the work load of each time in P Project.
8. For I Project, the evaluation standard should be announced ahead.
9. For P Project, the interface is too complicated.
10. Should have more real case scenario analysis.
11. Too much work for P Project.

Team Project and Team work

1. There should be penalty for those who didn’t do anything in T Project
2. PM doesn’t have enough authority to manage the group. Some team members do very little work in the project.
3. It may be good to have the teacher as the PM for a demo project. Then we can learn software engineering in real world instead of program homework.
4. There should be more team work since it’s the core of this class.
5. We can try some new and interesting method, such as Pair-Programming, since we don’t have chance to do that outside the class.
6. The time of class is not very good. 1:30pm is the time for nap.

others:

1. Can we have at least a 180-day-trial TFS instead of 90 ? (From the admin)
2. I like to see more examples rather than terms, actually it’s not bad in the class, but maybe it’ll be better if we follow one (fictional or real) project through the whole class
3. I hope students can take part in MSATC to do some real project.
4. The teacher can do more demos.
5. The teacher should not be too casual.
6. The organization is loose. Absence for class doesn’t get penalty.
7. The organization is loose. Absence for class is common.
8. The content of the class is not solid. And most of the time, it feels like there is only a framework.
9. Some real case in MS can be used in class.
10. The teacher can invite some engineers from MS to give some presentations.
11. Let students do some explanations about Test & Dev.
12. As senior students pay less attention on their scores, we should use rewards and competitions to attract their interests.