Design And Implementation Of The CVS Auxiliary Tool System

Software Configuration Management (SCM) is a foundation stone of the good software project management, also an important means which can improve the production efficiency of the software. It begins when a software engineering project begins and terminates only when the software is taken out of operation. According to the function played of SCM in every phases of software life cycle, an integrated environment of SCM has five tasks including version control, change control, status reporting and configuration auditing. The version control is the key function of SCM and it offers a means to track the software development behaviors of changing Software Configuration Items and the results of change. Through this means the version control can prevent the software development behaviors from going on in a situation that is out of control or falls into confusion and conveniently advance the software development behaviors finished in the way of Baseline.As a powerful version control tool, Concurrent Version System (CVS) has exempted from the register and maintenance jobs of a large number of artificial completion by automating jobs of version control such as version keeping, version comparing, version merging, change, log control etc.. CVS is one of the core tools of SCM and can efficiently assist software engineers and software companies to manage the change of software--version evolution. It is extensively used in global medium and small-scale software enterprises and becomes the basic platform of software project management of these companies.The main work of this thesis was to analyze several problems which the enterprises ran into when they utilized CVS to put SCM process into practice and later develop the CVS Auxiliary Tool System to solve the problems. These problems mainly included three parts: the problem of module management, the problem of authority management, the problem of automation-notice management. The aim of developing this auxiliary tool was to better match the use of CVS in the companies and perfect the implementation of SCM process.The design and implementation principles of the CVS Auxiliary Tool System were provided here. This system adopted the Client/Server structure and the server end did not offer an interface to the users whose operations were only going on at the client end. This structure and working were the same as the original CVS software system. The CVS Auxiliary Tool System was divided into five function modules according to the systematic function module, including system management, project management, module management, authority management, automation-notice management. The server end which used the configuration server of the original CVS software utilized the trigger function of CVS itself and was offered the trigger procedures needed to expand the basic functions of CVS, which thus achieved the management of authority and the management of automation-notice. The client end offered the friendly operations of man-machine interface and treated with the data of the server end in many aspects, which could achieve the access and control of the client end. The CVS Auxiliary Tool System did not offered the establishment course of CVS users, but continued to use the existing CVS users which were fallen into three categories, including repository manager, project manager and common user.For the easy integration with the original CVS software system and keeping the basic working way of the original CVS software system, the CVS Auxiliary Tool System utilized the basic communication function of CVS itself to solve the communication problem of the client end and the server end.As the carrier storing the data in the CVS Auxiliary Tool System, data files in the server end adopted the way of text file. The main reason of using this way was that the configuration files in the repository of the CVS server end existed and worked with the way of text file. The CVS Auxiliary Tool System and the original CVS software were better combined by using text file as an addition to configuration...