Summary of the fifth to sixth chapter of "Software Engineering"

the first chapters of software engineering are software planning, requirement analysis and software design. After the overall planning has been done, it is time to start practicing. When the so-called theoretical system is strong enough, practice becomes particularly easy. We design software, of course, in the language I have planned to write the software we need to do, then this process is called "program writing".

"Summary" in the program to write this chapter, the video mainly around the program to write some of the basics, writing methods, as well as writing the completion of the detection process. Summing up is the first thing we need to write the program before we have some basic things, for example, we use the language, it is equivalent to our tool, it shows the "What to do", with the tool below is the method, it shows "how to do." method is to use "structured programming method to program." This is both simple and practical. The second is the structure of the design of some methods, principles, style. Finally, the process of testing should be done after writing. For example, some methods of detecting the complexity of the program. Below is my summary map of the same.

"Summary Guide Map"

"Summary of the sixth chapter" after the completion of programming, our program is not able to make customer satisfaction? Is there any problem that needs to be solved? Answering these questions requires testing the program we have written, which is the program testing phase. Do not assume that the program test will be very simple, it also requires steps and methods. Otherwise the test is not comprehensive, there is likely to be a lot of legacy problems resulting in customer dissatisfaction. Here is a summary of my steps in the test phase.

"Guide Map"

The map below is the link between the test phase and the preceding phases.

"Summary" If there is a very detailed plan before a thing is done, then things will become extraordinarily simple, just as we have already analyzed each step in our mind before practice, then we will be confident when we do it. Just like our study. When you feel nervous about the enormous amount of work you have in front of you, you might want to make a plan, divide the big tasks into small tasks, and then step through them. That would make things a lot easier. This is what the so-called ax should mean. This is what I learned in software engineering.

Summary of the fifth to sixth chapter of "Software Engineering"