"Modern Software Engineering", chapter 5.5, 6th and 7th of the Reading notes

This time I am going to write a reading note about the "Modern Software Engineering" Chapter 5.5, 6th and 7th chapter of the content.

In Chapter 5.5, I contacted a series of software development processes, such as: Write a re-change mode, waterfall model, waterfall model of various variants, rational Unified process and boss-driven process and so on. Each software development process has its advantages and disadvantages. What impresses me most is the spiral model, which integrates the waterfall model with the prototype model, and solves the different needs of users from different levels. But different models have its advantages and disadvantages, how should we use it correctly?

The 6th chapter is about the agile development process, which teaches us how to develop software better and faster. In the process of development, we will encounter a lot of problems, so we have to continue to summarize themselves. The development software has a total of 4 agile processes, as described in section 6.3. The first step is that there are all kinds of complex dependencies between the requirements and tasks, and we should understand how to embody the dependencies in the plan, that is, the so-called interdependence; the second step is to learn to gradually refine a task from the description of the product level to the technical realization level, which is in need of technical ability and communication ability. We must learn in practice to assign to each individual a different task according to each individual's ability to be more efficient; the third step is to determine your own task every moment, a firm goal, like a beacon, with it, in order to successfully complete each task; The third and half is a long-term task, is a sprint stage, at this time, we have to constantly repair bugs in the software, learn how to test, is to test a programmer is the only standard of excellence, in this process, we can constantly improve their programs, improve the original plan, so as to produce better software. The fourth step is to verify the incremental release of the software, then the question is, if you find a new problem in the sprint, improve the original plan, this is good or bad? The answer varies from person to person!

The 7th chapter is about MSF. The MSF (Microsoft Solution framework,msf), Microsoft Solution Framework, is actually a methodology and a Microsoft recommended way to do software. With the rapid development of the information Age, MSF also has its basic principles: 1. Promoting information sharing and communication; 2. Work for a common vision; 3. Full delegation of trust; 4. Responsible for the project, 5. The value of the delivery increment; 6. Maintain agility, anticipate and adapt to change; 7. Investment quality; 8. Learn all the experience; 9. Work with customers. These principles teach us how to make a software efficiently. At the same time, we need to combine the MSF team model with the MSF process model to uncover software-hidden issues at different levels, then fix the different bugs, combine the waterfall model with the Helix model, and combine the milestone-based scale advantage of the waterfall model with the strengths of the incremental iterations in the Helix model. After reading this chapter, I am familiar with the scientific connotation of MSF, but there is not very clear is that we as a software engineer, the future in the employment process, the boss test is our actual combat experience, but as a freshman college students, there are too many shortcomings and shortcomings, how should we break this dilemma?

Every time reading, every thought, every doubt, is the life of every growth, may we in the future journey more and more brave!

"Modern Software Engineering", chapter 5.5, 6th and 7th of the Reading notes