Spring 2020 Software Engineering assistant summary of the work of the fourth week

1, TA blog link: HTTPS: //www.cnblogs.com/NWNU-LHY/
2, this week, the number of jobs Comments: 14
3 Comments this week's work links: third experiment software engineering twinning projects https: // www. cnblogs.com/nwnu-daizh/p/12521474.html
job submission amount: 14/14

Job submission rate: 100%
job Average: 88.07

4, this week, main tasks:
evaluation of students work, git communication problems with some students, communication problems scoring rules in letter and micro enterprises students.

5 this week found problems and solutions:

Question 1: very few students did not upload coding rules in git

Question 2: Results of the peer review blog, nearly half of the students did not objectively pointed out the shortcomings, pointed out that only advantages in all aspects, to the disadvantage avoided.

Question 3: very few students Checklist rather perfunctory, but we all do the verification, most of the students are doing very very carefully.

Question 4: Design and Implementation, more than half of the students did not do an analysis of class, just cut a map in there.

Question 5: Do a flow chart of class analysis and the students are not using the standard flow diagrams and class diagrams, of course, this is understandable, because the theory classes should have not learned painting class diagram.

Question 6: very few students capture large, resulting in the blog pages seem to have been exaggerated, like, pay attention to layout.

1 problem has been solved: everyone's PSP are in line with the basic law of the incident.

2 problem has been solved: we have a visual and visual work is very nice.

The problem has been solved 3: There are a lot of students have a class diagram and flowchart, although not standard, but a little bit mean.

6. Summary: The junction of the epidemic reporting system relative to previous jobs, has been a qualitative improvement, and more from the average score of 88 points assigned to the 60 can be seen from our efforts. If you still have some work textual mistakes, then they are very beautiful software. Either from the login screen, fill systems, or visualization, the results are encouraging each student. Visible pair programming is meaningful, greatly improved the quality of the students of the system, from the junction of the situation of communication point of view, we give full play to their own strengths, but also discussing the existence of deficiencies in the system were noted and corrected .