A summary of software engineering courses

After a semester, I completed the Software engineering This course of study. During this semester, I have some new feelings about the knowledge of software. First of all, this course let me understand that the so-called software development, and not simply to build code, adjust the code, but need a scientific methodology to guide the process of scientific development. Code writing, just a small part of the software development process, and more importantly, the early design work, as well as the subsequent maintenance process, are extremely important. Like once a high man said: "When, the development process is like building a scientific guidance program, can know those who do not have professional knowledge can also complete the work, that is the software development should achieve the goal." "In this way, people can be freed from the heavy mental activity of software development." The course of software engineering is the beginning of this series of engineering methods.

One semester, I have done a lot of things personally. From the initial personal project calculator, to the trooped project, to the diagram description of the study, then to the final team project development and report summary of the composition, it can be, this is my continuous learning process.

A personal project is just a simple calculator project, and basically one night you can submit a more complete code, and I do the same. But by the end of the project, I found that when I had a co-developed teammate, simply relying on code and language communication is not enough, because everyone has different understanding of the program, different opinions, there will be differences, and discussion is the way to resolve differences, the outcome of the discussion is very valuable, At this point you need to have a medium to save it, that is, to implement it as a text, in the form of documents to save. So, every time we talk about something new, we can see where we're going with the last design, where it's going, where it's going, at a glance, not every time we start from half-way, or from the ground up. This has greatly improved our development efficiency.

To the later learning process, I pay more attention to the summary of these engineering methods, including a variety of analytical models, various diagram structure description method. All of this has been a great help when I later wrote the project report for our group. And the final report, in addition to describing our software project, I think for me, is a summary of the knowledge learned this semester. From the requirement description, the need analysis to the diagram description, and the test sample, I think that basically covers all the knowledge we learned this semester, and it is the process of putting the knowledge in the book into practice.

In a word, this course is not as progressive as I thought, but it does make me feel better.

A summary of software engineering courses