For a large business, I personally define this large-scale software company's concept is that managers, developers include testers (excluding sales personnel) in more than 100 people, then the complete quality system can be implemented, but also execute Strength, including process monitoring can be very strict. but
It is the number of companies in the software development enterprises in 100 people in China. Most domestic software development companies, the number of people developed and tested is around 50 people. For small companies, the progress of benefits and development is valued by the manager. Of course, quality
This is also paying attention to it, but there is no strong technology, management, and capital resources of large enterprises. So many times in terms of quality but it is difficult to implement the quality management system smoothly. In the forum we can see a lot of posts pay attention to the quality management system of large-scale enterprises.
At Japan pay attention to the ISO9000 system, pay attention to the CMM system in the United States.
With the growing development of domestic software markets, many foreign students or local people started to create a company. The problem occurs is that it is difficult to supervise the quality because of the shortage of funds. An ISO9000 complete system, basic implementation of funds may be in 200,000. If you take into account continuous management utility, the proportion of this fund will be high. A CMM system, the cost may be more high might to be in millions or even a record. So how do small companies guarantee quality supervision? ?
I personally recommend as follows:
It is not necessary to set up a special quality department, and the quality sector and test department can be merged, and the general name can be called the test department. The fulfilled responsibilities are generally testing work to test the quality of software products. Process supervision, process audit can pass high-level managers, test department managers,
Software development manager set up a three-person supervision mechanism.
=================================================
The following is the basic list of documents and tools that need to be output.
BUG management tool
Check In Check OUT Code Management Tool
Project staff arrangement and schedule
Development and output documentation
Test document (TEST Plan, Test Case)
Organized review of meeting management documents
=============================================================================================================================================================================================================
Automated Test Tools (for small businesses do not need to purchase relative automation test tools, can be developed by the corresponding testers, or need to develop)
** In the initial stage of development, the three-person supervision groups conducted project evaluation and project supervision.
Output: Project Error BUG LIST, project initial budget plan document, review record
** in the function design phase
R & D managers have been divided into modules and determine corresponding personnel to organize development, arrange staff development progress, and test managers to determine specific testers to follow into the specific module. In the detailed design phase of a single module function, the tester is incorporated into the bug list in the later stage of function design, and the design document, error or unreasonable is entered into bug list. And output Report to the test manager, schedule a unified meeting, supervise the correction or To discuss. After completion, the tester outputs the Test Plan.
Output: Function Design Details Document, Module Review Report, Bug List, Test Plan, Review Record
**development stage
In the program development phase, the programmer is developed in accordance with the functional design documentation. At this point, the tester can develop module test tools in Test Plan. Development function test software and performance test module test tool software (developed in applicable and simple principles). If there is conditional adoption
The unit of the automated test tool can be organized to write automated test scripts. In the later stage of program development, the tester should complete the development of the test tool and the writing of scripts. So you can enter the writing of TEST CASE.
Output: Module Test Tool, and User Guide of Module Test Tool. Test script, Test Case
** Implementation Stage
The program module is developed, the tester is tested. But the test of the module, using the self-written test tool or the purchased test tool first tests the function, then performs performance test. During bug management and programmer's interactive DEBUG .
Output: Test Report, Bug List, Module Performance Curve Chart.
For details on the implementation phase, Me will be described in the next article because there are many works in consideration of the implementation phase. Not only contains testing, but even interpersonal communication, etc..
The above is a little bit of personal experience, a little view of small businesses.
I hope to be a brick, it can attract everyone to discuss the quality management of small enterprises!
