summary
A product line is always quality problems. Almost every time the cause of the accident retrospective analysis boils down to Test developers and Code Review done well, the interface is not a problem, the problem is the branch, and it was taken for granted.
For us such internal product development, there is no time is often just an excuse, often they do not want to do or feel unimportant.
Together with the R & D manager, to discuss the implementation of a program to test and develop the Code Review. That is, coding is complete, the code freeze, in order to process the recording unit testing. Thus, the SQA can code the differences between the baseline and the UT ST baseline audit, and UT report and verification report Code Review. So, I put forward the implementation of SQA process based on the right to refuse to submit to the product testing department for testing, that is, under normal procedures, research and development of design review, test and Code Review has done is not sufficient, you can not submit test system.
SQA to do is audit, reports, suggestions
SQA Although the main function is in the process of execution, but the fundamental reason for the existence but also to improve the quality, can pass a marked presence is not in place on the analysis of SQA, during the execution stage point (mainly it refers to every step of the show on like process have done that kind), SQA has a negative power is good, it will show to all personnel, real leadership quality view, progress in the end is pure existence of priority, or the perfect combination of quality and progress.
