(1) After reading textbooks and reference materials about software quality assurance What is your experience is? :
First application "software quality" of the word is very extensive, there are different definitions in different contexts. Such as "Capability of software product to satisfy stated and implied needs under specified conditions"
Software Quality = + program quality software engineering quality
Where the program is reflected in the quality of software quality external function.
The quality of software engineering in the following five areas:
Visibility 1, the software development process
2, risk control software development process
3, internal software module, an intermediate stage of the project delivery quality factors of project management tools
4, software development costs of control
5 completion of the internal quality indicators
Thus, in fact, the quality of software engineering has an important significance for the quality of the final software. One set of relatively mature theory is CMMI, software engineering, quality can embody exactly how. The significance of this theory is that the implementation can improve the management level, reduce business costs. Divided into five levels: an initial stage, two-level management, defined three-level, four-level quantization management, optimization level five.
CMMI although much has been achieved in traditional software companies, but in the Internet business-oriented small and medium enterprises, its effect remains to be seen.
(2) If you are a QA project, what do you think your job responsibilities?
1. The plan
to develop SQA plans for specific projects to ensure the proper execution of the project team. Develop SQA plan should note the following:
focused: to determine the focus of the audit based on business goals and project situation
clear audit: Which specific audit activities, those products
clear audit approach: determine how audit
rules are clear results of the audit report: audit The results are reported to whom
2. The audit / confirmed
SQA SQA audit work carried out according to plan, released the results of the audit report in accordance with the rules.
The contents of the audit: whether to follow the procedures required to perform the corresponding activities, whether in accordance with the process required to produce the appropriate product.
3. Issue Tracking
problems found in the audit, requires the project team to improve, and follow up until resolved.
(3) If you are a project manager, a full-time QA do you think that your project needs it? Or you can just have a Test? If problems arise, how do you define who should bear responsibility?
I think both are still needed, if a team is doing software seriousness, they must consider how to ensure the quality of quality / software engineering program, as well as achieve these qualities. So QA and Test are complementary. QA is to ensure the quality, if you let go QA testing, did not even two, may be more prone to error. If there are problems, the first division of labor between the two is clear, there should be both shared and found errors before they can develop better software.