1. Purposes
Through the implementation of software test and found that the software capabilities, the system design defects; reference design improvements, the reliability of the software to meet product specifications and improve customer satisfaction.

2. Definition of software measurement
Refer to non-testing of the software (referring to the Institute with the Ministry of software test measurement company other departments, including the Institute (except software design engineers and software test engineer), the Engineering Department, the Department of quality control, production department, marketing, logistics Department, General Manager Office, the Ministry of Public Relations Department, etc.) functional testing of the software.

3. Steps
a. Operational flowchart

b. Test task order
Software design department completes "Test task order" and submits the software to realize the function modules and related materials.

c. The preparation of test plans and countersigned
1> Based on the testing of the software design to the test-preparation tasks "software test schedule," participated in the testing program will be measured in the number of departments arrangements, time spent and so on.

2> "Software test schedule" needs test, countersigned departments, and departments in accordance with the test plan for testing and submit the list to test for testing.

d. Case and platform structures
Testing of the software test engineers prepared in accordance with the Software Test Case for testing machines and testing platform structures.

e. Software measurement
Measure sector participation in strict accordance with test plans prepared by the Department to the designated test sites for testing, and testing schedule on the sign. In accordance with the test provided by the Department of test forms and test standards test, test reports and carefully fill in the problem at the records of the testing program in accordance with the standardized test aircraft test specifications determined.

f. Tracking and improving test problem points
1> tests fail, measured by the project staff and do a good job record, software test engineers to view the situation and confirmed test, and complete the follow-up single-point test problem.

2> software test engineer at the issue in accordance with the test point on the issue of responsible departments track until the problem was closed, if the problem can not be shut down point, need to consult with general manager or chief engineer ruling.

g. Test reports
Upon completion of testing various departments, software test engineers will test results feedback software design and the Department of the Chief Engineer. Save the test reports according to all departments.

h. Test evaluation
Testing in accordance with the Limitation of "software test schedule" in the arrangements for attendance calculation of the test will be the test of all tests measuring departments cope with the situation to various departments responsible for the release, in accordance with the department responsible for incorporating test issued by the Ministry of the month.