DEADLINE: 2021/12/20 23:59
1. Please recall your first assignment in the summer vacation and your imagination of the software engineering course
(1) Compared with the course objectives and expectations of your first blog, "I hope to enhance the ability and employment competitiveness of computer major through practical exercise". Compared with the current learning and practice, in what aspects have you achieved your expectations and objectives, what are the deficiencies and why?
(2) Summarize the practice and improvement of this course, including the following contents:
2. Write your own ‘The Mythical Man-Month’, which means write experience summary and case analysis in project practice (e.g., personal project, team project).
3. What do you want to suggest and tell the next practice, or for you at the beginning of school, for you in your freshman year, and for Mr. Zhang at the beginning of school? And expectations for future generations. In particular, do you want to change team players in the next term?
4. Please analyze your team. Software engineering practice is a rare serious team cooperation experience in universities. ‘The construction law’ says that there are several stages of team development. Has your team experienced them and finally reached the "creation" stage?
5. How to prove that you have learned software engineering?
(1) Develop software that meets user needs
It must be published publicly, with actual users, a certain number of users and continuous usage (10 - 100 users can be maintained after 3 days); Instead of making software that no users use.
(2) Through a series of tools, processes and teamwork, we can release "good enough" software within the expected time
Have project planning / requirements / design / implementation / release / maintenance and regular progress release; Instead of being fooled by staying up late, patching things up, working alone, delayed delivery, etc.
(3)The software can be maintained and continuously developed through data presentation.
It's not that the source code can't be found, the code has no documentation, the code can't be compiled, and there is no development information of projects such as task / bug
P.S: Please use data to prove the above contents or focus on one of the choices in your blog.
6.＊(Optional) Read the classic papers on code quality in software engineering, select one or several from the following literature, and make a reading note in combination with your own reality (for example, how about the quality of your own code, is it a big mud ball, and how to measure the quality of your own code)? Select one or more of the following reference papers:
 Stamelos I, Angelis L, Oikonomou A, et al. Code quality analysis in open source software development[J]. Information Systems Journal, 2002, 12(1): 43-60.
 Boehm B W, Brown J R, Lipow M. Quantitative evaluation of software quality[C]//Proceedings of the 2nd international conference on Software engineering. IEEE Computer Society Press, 1976: 592-605
 Samoladas I, Stamelos I, Angelis L, et al. Open source software development should strive for even greater code maintainability[J]. Communications of the ACM, 2004, 47(10): 83-87
7. Give full play to your personality, including graphics, photos and creativity