I. Status of project code issues
Second, the Code problem causes analysis
Third, what is the code quality
Four, the Quality improvement strategy
Five, the road of department implementation
vi. Support Tools for code assurance
One, the code problem:1, no code comments;
2, no code-related design or structural documents;
3, the function code line too many;
4, the function of class and function is not single;
5, the risk of memory leakage is greater;
6, logic confusion, it is difficult to read;
7, hard coding more;
8, the interface definition is not clear, the input and output definition is not clear;
9, more garbage code;Second, reason analysis1, the project member skill is insufficient;
2, the project time comparison rush;
3, Project code, code review control effect is not good;
4, code specification is not unified;
5, the design principles of understanding is not unified, not deep;
6, lack of awareness of the importance of quality;
7, the new person, the project midway joins, etc.;
8, rely on the test personnel to find the bug;
Third, what is the code qualitythree-sex:Readability: 1, annotations;
2, reject large paragraph code;
Maintainability:
1, can not hard code;
2. Avoid platform-related calls
Availability of Changes:
1, code reuse, public functions;
2. Design mode
Key indicators of code quality evaluation: Low coupling, high cohesion
Iv. upgrading ideas and strategies 1, Code quality indicators, including performance appraisal;
2. Discuss and confirm code planning standard;
3, build Code quality control organization, apprentice pair, master of code quality control;
4, conduct code review meeting;
5, the discussion design principle;
6, the application of mature code detection tools;
Consciousness
Standard
Process
Mechanism
Accessibility tools
V. Implementation of monitoring 1, the protection of project design phase of code norms learning activities;
2, the development personnel self-examination mutual investigation, the detection tool detection;
3, the product code submitted at the same time to submit the corresponding module interface test code;
4, to submit the code of the programming process of the record, as an important activity in the project process;
5, Code Review Meeting, assessment of each member of the code quality, as the basis for project assessment data;
6, the project every round of testing, testing to provide developers for the code defect rate;
VI. Auxiliary Tools Static:
Cppcheck
VS Analysis Tools
Xcode comes with analysis tools
Dynamic:
Instruments
BoundsChecker
My opinion on the improvement of Team code quality
