Reliability Assurance Measures of CNC System Software

Article Preview

Abstract:

Based on the technology characteristics of CNC system software, the corresponding assurance measures are set for the reliability in design stage, program implementation stage and software testing stage respectively. CNC system software reliability is improved by modularizing program design and structure program design, code review and program readability, using different reliability testing methods. Finally the purpose is accomplished that the whole reliability of CNC system software is improved.

You might also be interested in these eBooks

Info:

Periodical:

Advanced Materials Research (Volumes 418-420)

Pages:

2182-2185

Citation:

Online since:

December 2011

Export:

Price:

Permissions CCC:

Permissions PLS:

Сopyright:

© 2012 Trans Tech Publications Ltd. All Rights Reserved

Share:

Citation:

[1] Jun li, Wen-jun Lu. Imported Numerical Control Machine Tool CNC System Reliability [J].Inspection and Quarantine Science, 2008 (3): 25-26

Google Scholar

[2] Tao Wang. Research on Reliability Design Theory and Methods of NC system[D]. Tianjin. Tianjin University, (2008)

Google Scholar

[3] Xin-xing Li. Reliability assurance in the life cycle of software[J]. Electronic Product Reliability and Environmental Testing, 1999 (1): 10-14

Google Scholar

[4] Fan-mao Liu, He-chi Yi, Ze-jun Wen. Research on the Open Soft Numerical Controlled System Software Architecture[J]. Machinery & Electronics, 2009(9):44-46

Google Scholar

[5] Guo-wei He. Software Reliability [M].Beijing: National Defense Industry Press, (1998)

Google Scholar

[6] Fei Sheng. The Research and Application of Numerical Control[D]. Changchun. Jilin University, (2004)

Google Scholar

[7] Yun-hui Ning, Hai-mei Hou. Research on Methods of Software Reliability Testing[C]. Fifteenth Reliability Academic Annual Conference Collected Papers in 2010, Zhang Jiajie: Reliability Branch of the Chinese Institute of Electronics, 2010:55-57

Google Scholar

[8] Jie Li. Design the Software Test Case [J]. Software Development and Design, 2009(11):17-23

Google Scholar