On the improvement of software development process

            process improvements are repeatedly mentioned in many of the software's data. It is expected that the goal of achieving CMM will not be shown to most companies, However, some basic management methods can be seen in the short term effect, such as conference system, attendance system, project resources Unified Management, configuration management, test management, respectively, explained below:      meeting system is not a software engineering scope, But it is a very basic company management system, if this is not well implemented, it is difficult to imagine that the knowledge system of large-scale software engineering implementation. A project team usually has a regular meeting within a week, summarizes the work of the week and plans the next week's work, designating a moderator and a recorder before the meeting, The time cost of meeting minutes is relatively small, just take care to record the conclusions of the meeting. In addition, a number of meetings should be held on a weekly basis, depending on the specific circumstances of the project. The format of meeting records can be consulted, or according to their own requirements, as long as the key to ensure that the record is enough.      attendance system for high-tech companies, especially important, software company employees are mostly young people, but also many just out of school, the characteristics of young people in the project is tight when overtime are not care, but usually there will be lazy situation, such as late, early leave, etc., In some fledgling software companies, frequent overtime has become an excuse for many software engineers to work in a rambling form. This is detrimental in the long run. Should try to reduce overtime, but usually the attendance system must be strictly enforced, not because of a person, a group of time overtime frequently or work hard to relax attendance. There are many ways to do this, and the intranet is a good way.      in a project team, even if the number of small, should be as far as possible division of labor, such as to allow someone to undertake tasks such as coding,design, while inclined to testing work, someone is responsible for configuration management, Team leader to be responsible for the unified management of documents, text block format specification is best by a person to check, the specific content of the text by each member to write, do the benefits of division of labor is to avoid everyone seems to do anything, but nothing is proficient, may appear everyone write text block, but the format is not the same situation, If everyone is required to write the same format of the text block often have a lot of difficulties, rather let a person to ensure that the text block format, generally to ensure that the text in every week can be synchronized updates.      configuration Management is the CMM in comparison can see the effect and implementation of the issue, general use Sourcesafe,cvsand other tools to meet the requirements, if using Microsoft's IDE, generally use SourceSafe, if it is JBuilder or Linux under the development environment, the use of CVs. But be aware that once you've selected a tool, don't give up easily, and get to know the tricks of using the tools. The implementation of      test management also requires a certain understanding of the importance of testing and general theory, which is a lot of information, nothing more than the classification of tests, steps, and so on, and most will use very heavy ink to prove how important the test is, In fact, the importance of testing does not need to say more, we have already recognized. After understanding the theory, the same is to find some tools, such as OpenSource bugzillar is a good bug management tool, just configure the time to understand Apache,perl and so a bunch of things, but also to consider the Chinese and so on.