The experience of the law of construction

Hello everyone! I am now a reading software engineering students, should be to their own software engineering major is to understand, but most of them are professional is also smattering, including me, only know that software engineering is the background code development, etc., and then it is not clear that, in fact, the Software engineering subdivision down, It also covers a wide range of disciplines and expertise.
However, after reading the "Law of construction" This book, I have a certain degree of software engineering this concept or professional understanding, there are a lot of experience, many vivid examples of the book to simulate the form of real communication to explore, giving people a plain and understandable text in front of the reader, This allows the reader to more in-depth understanding and understanding, making it easier for people to appreciate the technical aspects of software engineering, so that people have a desire to understand more deeply the impulse.
The whole book mainly introduces software testing, software engineer's growth, code specification, team cooperation to develop the importance of software, as well as the overall process of developing software projects, it development and innovation and so on, so that the content of the whole book is rich and colorful, not like the General Software Engineering book, the same, too stiff and stiff, And the content of this book to the reader a cheerful reading experience, can let people more quickly to accept the content, and absorbed for their own use, and the contents are examples of life, make people look more familiar with the software engineering is in our side.
So what are you going to ask about software engineering? Software engineering is the process of applying the systematic, orderly and quantifiable methods to the development, operation and maintenance of the softwares. It includes the following areas: Software requirements analysis, software design, software construction, software testing and software maintenance.
In fact, software engineering is to include "the development, operation, maintenance of software in the process of many techniques, practices, habits and ideas." Software engineering unifies these related technologies and processes into a single system called the "Software development process", the purpose of which is to improve the efficiency of software development, operation, maintenance, and improve customer satisfaction, software reliability and maintenance. "This is an overview of what is software engineering in the book.
There are, for example, examples to clarify the difference between team and non-team, and give a new definition. The residents of Qu to move a pile of bricks from the village to the end. He came to Ball bar before, see twos squatting some people, some people in front of a cardboard box, which reads "Java, five cents a line"; "The front page, not cool no money"; "Turn to PS, be good at the human body"; "Take all SQL, NoSQL", and so on.
The big wisdom to these people shouted a voice: board bricks have there? 100 Bricks A dime! Some of the people squatting on the ground looked up, and one or two of them stood up slowly. Big Wisdom looked at the number, and shouted: Lunch has lunch! At this time seven or eight people all stood up, pat the buttocks to be in front of big wisdom. The great wisdom took them away. Are these seven or eight teams? No, they were just a bunch of rabble, and they gathered together to get their money out of their jobs. Compare it to the track and field group competition examples. "We can see that the team's characteristics are:
1, the team has a consistent collective goal, the team to accomplish this goal together. A team member does not have to work at the same time, such as a relay race. (Qu Move Brick "non-team" Members are not, everyone wants to move how much to move, do not want to work on the settlement of wages leave. ）
2, the team members have their own division of labor, mutual reliance on cooperation, work together to complete the task. (Qu the "non-team" members of the brick are their respective actions, the task is completed independently, some people leave without a real impact on the other people who move bricks. ）
Use these examples to more vividly explain the importance of team work in software engineering projects.
There are a variety of models of software teams, different teams have different modes of cooperation, based on the actual situation of team members to plan the deployment, no universal team program can guarantee the results. With a team, you can only involve team processes. It is precisely because we students often have only a lot of experience, in the teacher talk about waterfall model, agile process and so on when the understanding. When we are really in a team project, the problems that we didn't care about at the time are often the key to hindering the progress of the project. Therefore, the book's five or 63 or 73 chapters refer to a variety of team project collaboration and theory, but also let me gradually understand the indispensable team, each is a part of the, indispensable.
It is precisely because the law of construction is based on the most easily understood steps, from development testing, developer growth, and team management to demand analysis, design, and user experience. First let us know what the development of things, everyone has the experience of coding practice and then step to demand analysis, design will understand more thoroughly. A good book in addition to its own content, but also need to be able to trigger the reader to think, to learn more extended knowledge. Remember before someone on the internet answered how to find a good technical book, said: "In a classic book to find the reference books or quoted books, is generally good." "I think it's quite reasonable. There are a number of valuable references in the body of the Law of construction and in exercises and discussions that allow us to learn more about the wider range of knowledge, and the practice of a large number of exercises that can be independently thought of and solved in a way that will greatly improve our practical ability.

But after reading I still have some questions to ask:
1, to do software engineers to have what elements? What knowledge is needed to supplement it?
2, how can we better achieve the knowledge? is to use the content of the book in practice.
3, how can quickly improve the project practice less, no practical experience, the foundation is not good, and want to engage in the industry is people?
4, want to do product manager to have those skills?
5, how can we better achieve the innovative thinking of it?

The experience of the law of construction