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

1, TA blog link: HTTPS: //www.cnblogs.com/NWNU-LHY/
2, this week, the number of jobs Comments: 10
3 Comments this week's work links: Northwest Normal epidemic reporting system https: // www. cnblogs.com/nwnu-daizh/p/12416880.html
job submission amount: 10/14

Job submission rate: 71%
job Average: 59.2 (uncommitted not counted in average 0)

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: Project Code specification (10 points) evaluation of all the students I have not presented on git, leading to the score is not high.

Question 2: commit more than 10 times, in addition to a student's way to delete data brush to brush 23 times, not one student to complete multiple submissions, of course, that the students deduct invalid even if the operation is also higher than the effective operation of the other students.

Question 3: requirements analysis, I saw some students directly copy and paste operational requirements of the project background, I also wonder how much the students needs analysis is the same syllogism.

Question 4: design and implementation, not one student to do the analysis of class relations, as well as the students to use the python and c of process-oriented design, it is understood that they did not like the analysis, but they did not top-down design flow chart function.

Question 5: Summary: How do you design a program to achieve "modular" principles of software design. Almost all the students regarded as a summary of this experience, I learned a whole XX, this is not good apparently did not read the job requirements.

Question 6: If all the links you seriously do, then here you should have a lot of experience willing to share with you. (5 points) because we put this link in the summary inside, resulting in many students do not do this, the score is very low.

Question 7: Some students Code is not strong, so I chose the operational requirements of a mission, but did not do histogram visualization, hoping to improve.

Question 8: Although can understand that some students use python and c in this assignment, but in future we progress into the analysis and team projects like when still hope that we use c ++ or java, there is no ability must also create use class Construction and c python code, not only defines the function completion.

Question 9: There is a student submitted a compressed file on git, apparently did not understand the usefulness of git.

Question 10: There are some students to reflect not on board git, can be considered responsible for teaching assistants whisper passed it to overcome the difficulties.

Question 11: The third student has come, PSP portion relative to the previous two students has been greatly improved. Only one student said demand analysis (learning techniques) used 9000MIN, but only a specific design phase 150MIN, I express my doubts.

The problem has been solved: The generation of teachers will score the ultimate requirements of the job in detail, it can be completely normalized score, very fair. But some students though better to complete the work, but no details of the completion of all aspects of our blog, and even missed a number of areas, leading to low scores, pay attention to the design of the importance of their work links and textual needs. Although this generation of teachers with two weeks to set up a job, but you can see the detailed design problems, you can expose the refinement of the problem. Obviously spend more time also good. By this time the job was last seen some students can not keep up the rhythm completely, or hope we work it, can not do exhaustive code must ensure that the text of the stage and the functional code. In my personal experience, the score includes many of the fifteen sub-class, spend time, but more objective, to reduce the subjective factors, but also expose our students to the many obscure problems. For example, do not carefully read the job requirements of rules and so on.