Read the experience of the law of construction
First of all, this is a panoramic book that will give you a better understanding of the industry, allowing graduates to be less surprised and unexpected in the process of unfamiliar to the industry, which is a textbook that integrates reality.
Secondly, this is a best practice book, covering every aspect of scientific and healthy software engineering, introducing various methodologies, but not high-up, programmatic methodology, but the best practice of methodology, is indeed available, to use.
Third, the book makes people have feelings, students on the "ancient" waterfall textbooks or "imported" agile books, will inevitably lack of confidence: this thing can do? Is it suitable for modern? Is it suitable for China? And if to the major forums, communities, or ask "experienced", often will harvest more negative information, so that the students have feelings of disappointment, so that the lack of feelings of the students willingly. But it is obvious that our industry needs more feelings of talent, better professional ethics and literacy, if the students bow before graduation, the industry has any hope to say? Xin Zou Teacher's textbook will let students know "should be so" and "can be so", from this point of view, boundless beneficence.
The book introduces methodology at the same time, actually will introduce the methodology does not apply to the scene, the methodology in the reality is how to run off, it is like talking chess, "so go, after the development will be how, so no", how to do it, how to do wrong-what is the macro perspective? What do you mean by best practices? What do you call scrutinise? It is like drawing a decision tree, to which branch to walk, the result will be what, clear, clear, convincing.
Five, this book in the introduction of methodology, did not put "people" into the "methodology" of the lower level, but introduced a variety of roles, flesh and blood emotional people, can let students understand the work of the various roles and ideas, demands, to avoid "program-centric" thinking problems, and understand people-centred thinking, After all, the program to solve is a matter of people. This shift in thinking is crucial for programmers.
This book covers the whole of modern software engineering, and every chapter and even every paragraph can be taken as a guide in practice.
This is a great enrichment of the essence of a good book, the software should be attendee, like every military must have a copy of the Art of war.
After reading this book, I left a few questions:
Question 1: How do we guarantee the quality of software development? How to measure?
Question 2: What if there is a change in the middle of the team writing?
Question 3: How to gain the user volume?
Question 4: How can the code be further optimized to ensure resource utilization is reduced?
Question 5: How do I increase code coverage?
Fifth Blog Assignment-read the "Building method" experience