A summary of software engineering courses

From seeing the class of software engineering in the curriculum, there is a lot of anticipation for such a course, because in my opinion, software engineering is the development of software. Later on this course to know that software engineering is not the original thought of the "development" curriculum, most of the embodiment of the idea of a software engineering. Throughout the semester, let me have a new understanding of software engineering. In addition, for team development projects is also a development of their own growth of knowledge, or a lot of insight and ability! Here I have a detailed summary of the relevant knowledge learned in this course.

There is so much to learn about this textbook.

1. The importance of unit testing, in the real self-coding, especially in the search for the bug phase, when we can not find the wrong place, we will know, if each module, have been personally tested, is not so much trouble? Actually looking at wasting time, but actually unit testing is saving time.

2. The importance of code specification, when we go to write code, often do not pay attention to the format, especially the next section of the code to cut to the beginning or end of the program, the format may be chaotic. Let others read, it called a pain, software engineers to give us evaluation, as well as the grading situation, fully explain the company or actual development, the code is very important, the code of their own reading specifications and non-standard code relative empathy.

3. Of course, there are a lot of specific knowledge, such as agile development, MSF, project manager, demand analysis, typical users and scenarios, software testing, personal performance and so on, in the course of the listening process can be learned is absolutely in mind.

The teaching mode of "doing high school" is of course not confined to textbooks, and there are many gains in classroom practice and practical development.

The beginning of the course is a general understanding of software engineering. Software engineering is the process of applying systematic, orderly, and quantifiable methods to the development, operation and maintenance of software, and we know the process of the development. Because for those of us graduating students, more or less will be to understand some of the work on this aspect, such as: To do the job needs analysis, do the work of knocking code, and do software testing, in fact, this is the development process of several sub-processes. If we have found a job now, each of us has personal skills, you can become Daniel, you can also become a common code farm, but this will involve how to integrate into a team.

We start with the cooperation of two people, such as the arithmetic of this semester, we have a group of two people, continuous iteration, the beginning may be very simple, two people will not have any differences, even if there is, it will be very small. But in the back will find that with the increasing number of code, the divergence will be more and more, this time, communication skills and two people's mutual tolerance is really important, the first fork, may be easy to go in the same direction, but when the fork a lot of time, and think oneself is right, refused to let the other side, So the project will not be done anymore. Two people eventually worked together to develop an app called "Easy Hundred points", arithmetic two people cooperation is also considered a successful end.

Again in our team's harvest, this time we have two people develop the tacit understanding, also slightly know how to integrate into the team, we put ourselves in a room, no matter how, write code, even for a bug overnight, and later found that, to the end of the night, the coding efficiency is almost zero. From which we can also see that the longer the time, the more results come out, the most important is efficiency, if we are willing to spend time in the inside. To later, we have a lot of differences, even the kind of you say you, I said, you do not consider me, I do not consider you, to the stage of mutual rivalry, this time, maybe we are very "helpless" bar, after all, finally come out an idea, how can be denied it! As time goes by, the result of this rivalry is that the project progress is zero. Later realized that this is not possible, here to apologize to you. In general, the integration of a team, the first to accept the views and suggestions of other people, "three people will be my Teacher Yan", followed by mutual learning, mutual progress. Pay tribute to my team here! Teamwork has brought me great gains.

Software Engineering This course is really different, although teachers usually let us do some tasks, and then coding, pair programming and other practical development, sometimes in order to learn to swim also to implement "kick a foot" method, but look carefully, is not learned a lot of things? Do more than you can learn! Personally, I prefer Mr. Wang's lecture style, humor and fun, and, if you listen carefully, certainly will not go thinking. In addition, the individual to "do high School" teaching mode is very recognized, because we learn the textbook theory, want to really understand the meaning of it, or in the actual development of the use of this theory, "theory and Practice combined" it! In this high-intensity programming exercise, will also have to, do not have to, although some "hard", but after learning something, will be to thank this "hard rules."

Finally to thank Mr. Wang for a semester of hard teaching, humorous and strict style is very popular with classmates. Also thank Meng engineers for their rigorous work evaluation, patiently pointed out the shortcomings in our code. This is a course that I love a lot.

Software Engineering Course Summary