Version Tube Tool Visual SourceSafe 6.0 Practical Guide (last)

First, the need for version management
If the software crisis of the 70 's led to the birth of the idea and the development of the theory system, the rapid development of the software industry in the 80-90 years, especially in the 90, led to the generation and realization of another new idea, which is the software version management.
As long as anyone who's been involved in software development knows, it is hard to imagine and impossible for a software project to be completed by one person at a time, usually with a research and development team to analyze, design, encode, and maintain, and a dedicated test team to test software that has completed coded debugging. In the huge and complex process of software development, people need to be involved in all aspects, and the information feedback is not only between the team members and the research and development groups, but also between the customers and the developers. All of these communication feedback information can lead to changes to the software, the small may be only a source file in the definition of a variable changes, large to redesign the program module may even be the entire requirements analysis changes. In this project, due to the inherent characteristics of software development, may form a large number of software versions, and we do not guarantee that there will be no error changes, and such a difficult situation is very realistic in front of the project development manager, how he/she can effectively solve these problems, specifically the following questions:
1. How to conduct the overall management of research and development projects;
2. How to coordinate with an effective mechanism among members of the project development team;
3. How to carry out the unified management of the sub-projects undertaken by the members of the Panel;
4. How to make a unified summary of the changes made by the members of the Research and Development Group;
5. How to retain the modified trajectory in order to remove the wrong changes;
6. How to identify, manage and differentiate the various versions of the software that are formed during the research and development process.
A very direct response, we have to introduce a management mechanism, a versioning mechanism, and a generalized version management, which requires not only the source version of the release management, but also the entire project management. In the past, it has been hailed as having a good programming style, such as commenting on changes to other people's source programs, modifying people and dates, and if multiple members have been modified at the same time, there is a need for timely manual differences in comparison and synthesis in order to form a unified new version. This approach in the current large-scale software development has become more and more space, can be said to be a small workshop in the form of the face of the social production of software, it is no longer possible to make it.
　
In fact, the idea of version management has long existed in the minds of software developers, but the past is not as urgent as people now realize. UNIX's program development system earlier provided the ability to carry out the source version management tool in the development team, now Linux is to provide a powerful Cross-platform version manager, the foreign company's windows-based version manager has a more mature products, Domestic research units such as the computer Department of Peking University Case laboratory are also committed to this work. In a wide range of mature products and pilot products, there will only be a detailed introduction to the Visual SourceSafe 6.0 of Microsoft, which uses a wider range of user prospects and is easier to obtain, for common research and development team solutions, and specific implementations.