[Software Engineering] Chapter 3 and Chapter 4 Summary

[Software Engineering] Chapter 3 and Chapter 4 Summary

The summary is supplemented by the previous one. The consequence of failing to summarize it in time is that you may feel unfamiliar when looking at your notes. Such learning is the least efficient! It is a good habit to sum up part of this article. But I still cannot stick to it. What a painful understanding...

[Summary] Chapter 3 of the software Describes the software requirement analysis. To put it bluntly, before designing a software, we must first understand the customer's needs. If there is no customer's need to do it blindly, it is like a football match without a goal. Just as we have no goals in our lives. Even if something is made at the end, it doesn't necessarily satisfy the customer's needs. Such a job is meaningless. Therefore, the software requirement analysis stage is very important. Just like a flag, it sets up a goal for us to move forward toward the goal step by step.

Chapter 4 of software engineering is the software design stage. When we make a handicraft, we usually design the outline of it first, and then design the details. The same is true for software. In the early stages of design, our primary task was to design the entire system structure, followed by refined processes and data design. Therefore, in the design phase, we divide the design into a summary design and a detailed design. Then there is a detailed design process. Below is my summary of the two chapters.

[Overview] Chapter 3 and 4

[Conclusion] In fact, the overall idea of the software engineering video is very clear. It is to design a whole process of what we need first and then what we need to do. Grasping the overall macro structure and overall thinking, watching videos and learning will be a great deal of fun... It can be very efficient .... Watching all the videos is a truth, so come on. Forward toward the front...