The book of the Law of construction

I have read the book "The Method of construction: Modern software Engineering" by teacher Xin Zou. Last semester in the course of learning software engineering, because I have been in a relatively weak base and not much understanding of professional knowledge and deep research, always feel that this is a thing and boring course, so there is no great interest in learning. But reading this book, I completely have a new feeling. Here are my tips for learning.

The first chapter of "SOFTWARE = program + Engineering", which let me understand that the writing process is not only to consider the data structure, but also to apply to software engineering. Then through the introduction of the particularity of software, software engineering knowledge areas and other aspects of knowledge like we elaborated on what is software engineering.

The second chapter is about personal skills and processes. I was Baidu after I know VSTS is a development tool developed by Microsoft. In this chapter, I learned about the main steps of creating unit tests and what are the criteria for good unit testing.

The third chapter analyzes the development of software engineers from 5 aspects, and has to admit that he has a big step to the goal.

Maybe because of a problem in the mid-term exam, so I was in the fourth chapter of the time, especially serious, code specification and pair programming read two times, let me understand that in the development level, pair programming can provide better design quality and code quality, two cooperation problem-solving ability is stronger. Indeed in the process of cooperation, can learn from each other and help each other.

The fifth chapter introduces several models and development processes of software team cooperation. The strength of the team is endless, it makes me understand that we should strengthen the sense of teamwork, so many times will be inefficient.

The sixth chapter is about agile processes. Through reading, I understand the principles of agile development and some of the problems and solutions of agile processes. But I still do not understand, specifically when to choose the agile process. I hope to get help with this question.

The seventh chapter introduces the principles of MSF, the MSF Team Model and the development model, MSF and CMMI. It must be admitted that this chapter is very difficult to read, and there are a lot of things to understand.

The eighth chapter is about demand analysis. This chapter is more interesting to me because I personally like to analyze something. So when you see the headline, you have a lot of patience to read on. But it was not as simple as I thought when I read it in the back.

From the Nineth chapter to the 17th chapter, the project manager, user experience, software testing, quality assurance and other related concepts are introduced respectively. While introducing these concepts, there are some examples to illustrate, which makes it easier for us to understand.

After reading this book, I have the following questions:

1. Are code specifications required?

2. What is the relationship between the team model and the team's development model?

3. When is it appropriate to choose an agile process?

4. What are the improvements that can prevent bugs from happening?

5. What is the quality of software engineering measured?

The book of the Law of construction