The third software engineering jobs - Study Quality Assurance
1, after reading textbooks and reference materials about software quality assurance What is your experience? (40 marks)
(1) What is software quality assurance
Software Quality Assurance is to establish a planned, systematic approach to management to ensure the development of the standards, procedures, practices and methods can be used correctly all the items. Software Quality Assurance aims to make software for process management is visible. It is through the software products and activities to review and audit to verify that the software is up to standard. Software Quality Assurance group has been involved in the project together with the establishment plan, standards and procedures. These projects will enable the software to meet the requirements of agency policy.
In this book, use the software program = + software engineering formulas derived software program quality + quality = quality of software engineering .
(1) QA (QUALITY ASSURANCE, Chinese means "quality assurance", which is ISO8402: 1994 definition is "to provide adequate confidence indicates that an entity can meet the quality requirements, and the implementation of the quality management system and demonstrated as needed all the planned and systematic activities. "some of the implementation of ISO9000 organizations will set up such departments or positions responsible for functions related to quality assurance requirements of ISO9000 standards, such as the work of staff called QA staff.
(2) in CMMI, the main job is to process QA review and audit products. from practical experience, QA only do both work hard to reflect the value of QA. in order to output QA organization is greater than the investment organization, add value it should be based on business needs appropriately increase the QA responsibilities, such as process instructions, process measurement and process improvement, etc. the process guidance is mainly pre-project aid project manager project plan (including auxiliary define or modify the project processes and process models to assist the project is estimated establish acceptance criteria for the project, set quality goals), members of the project process and specifications Training and guidance in the process, etc. The process metrics (including product measures) in the CMMI has become CMMI ML2 level domain in a separate process, but it is a common for all process requirements. In particular, the higher the maturity of the measure also requires the higher, the greater the difficulty, which requires a professional staff to be responsible, QA is a good choice. the main responsibilities include the collection, statistics, analysis and metrics to support management information needs. in the process improvement CMMI is mainly EPG responsibility. but in fact, QA process closer to the implementation of the environment, a better understanding of the situation during the operation, it is even more likely to find "the shortest piece of the barrel." At the same time, QA is the process of implementing improvements an important driving force.
in the understanding of these work after QA, QA think that every business should have the same or similar duties it? current status of many domestic enterprises is indeed the case, which is low QA overall effect of a very important the factors we use to determine when the QA responsibilities should consider their own needs and circumstances, including business requirements, process maturity Level and corporate culture.
The main business is to identify the needs of QA need to work to complete what aspects, such as the implementation of the peer review process, review and QA can help organize conferences; in the presence of outsourcing, QA may need to play a role in monitoring outsourcer aspects.
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? (30 points)
I think it does not need a full-time QA, QA because some do not know how developed, but not necessarily do well developed human testing. Just do not understand the development of R & D Manager R & D team as necessarily a bad tube. This problem is smart developers appear to bear responsibility.