The software engineering curriculum design has finally come to an end. Summary.

The software engineering curriculum design started from 13th weeks, but it was dragged to the beginning of 17 weeks. In the end, it could only be modified from the Internet, the reports are basically confused, and generally fail.

There are many reasons for this failure, mainly my own reasons. I will summarize these reasons:

1. An incorrect estimate of the situation is too idealistic. The biggest mistake is to idealize the software project too much and think that it can be done as long as it is well done without taking the time and technical level of the team members into account, the enthusiasm of the team members for participation has not been mobilized. In the end, I did almost all my work by myself, and other team members were busy with the test and did not participate in the test. This was a big failure of my team leader.

2. I chose an online pet store, which has been badly selected by many people. Although there are a lot of existing programs on the Internet for selecting this question, it can be run after modification, but it also greatly reduces the enthusiasm of the team members, it is difficult to surpass what has been done by others. Zhao Qun has done a great job in their group. They chose an online printing system, which is not only simple but not complex, but also innovative and scalable. Such a project can easily stimulate the enthusiasm of the group members. It can be seen that a program can be successful only when its functions are simple but novel, or complicated things that others have done well.

3. The answer in the class is not ready. I only spent half a day preparing for the PPT. Although the pictures were well drawn, I was very vague and had unclear logic when explaining the development process of the entire project to the audience. It may have something to do with websites that are not self-developed, lack of confidence and confidence. Finally, Mr. Guo gave an award to each group that gave a speech. It was very interesting. Our group was the best modeling Award, and Wang Mian's group was the best requirement analysis award, zhao Qun's group is the Best Innovation Award, Ji Wendi's group is the best Unity Award, and Zhou junxian's group is the best achievement award. I know that the awards given by the teacher are actually just a comfort to our group.

There are still many improvements to be made. For me, the most important thing is the way and method of speaking. I think the points summarized by Mr. Guo regarding the project reply speech are also quite good, as listed below:

1> development background. Including the definition of the problem and the proposal of the solution.

2> technical foundation. The basic technical knowledge used in the project, such as the Struts framework principle and MVC pattern, enables the audience to invest more in this speech.

3> process induction. Describes the entire process of project development and what process models are used, such as the XP model and the RUP model.

4> methods and technical difficulties. Analyze the methods used in project development and the technical difficulties that may be encountered during specific development.

5> tool application, problems and solutions. Tools used during project development, specific problems encountered, and the process of solving the problems.

6> innovation, advantages and disadvantages. Innovation points, advantages and disadvantages of this project.

7> understanding of this field and future prospects.

The speech was successful.

There are too few practical experiences and a lot of things to learn. For my dear family, for my classmates, friends, teachers, and for everyone's happiness and for my own ideals, I still have a long way to go. Finally, I 'd like to warn myself with the cool phrase-"Don't be too idealistic. Let's be realistic ".