A shallow reading of the construction method

1. What is the difference between "software engineering" and "Computer Science and Technology", in fact we have a lot of the same courses as computer science majors and the employment direction of the two majors is roughly the same, so where are the differences between them?

2. When implementing the software required by a user, we tend to minimize and make every effort to produce bugs that require detailed analysis of the user's needs, including trends in the development of such software in the future. The main functions are the design document, the source code is complete, has the modification record, and has the final version. The key module has the unit test that can execute, the pressure test script, and so on whether that means we should pay more attention to the software analysis in the course of learning.

3. Pair programming, the two director of different, the simple implementation of the "driving/pilotage" mode of work will affect efficiency?

4. The completion of a project requires a successful team. A person's ability is limited, a company to develop a large project, how to make a software team in a methodical way, how they work together, how to integrate the responsibility of all the parts into a project?

5. What are the specific standards for qualified software engineers? Or is it possible to write code and find problem solving to be a problem? At this stage, where can we start to develop our own development thinking and ability to begin to move towards an engineer?

6. Some software enterprises not only free, and even the source code is also a gift, but require the source code developers to abide by some kind of convention, I do not understand how they profit for this software enterprise? Or are they just offering a free service to get developer usage to boost corporate visibility.

A shallow reading of the construction method