What activities consist of quality management?
Quality management consists of the following activities: quality control (QC), quality assurance (QA), and quality planning (QP).
Quality management: quality control, quality assurance, quality planning
Quality control is the peak quality management. As a rule, it was observed even when other quality management was ignored. This product-oriented quality management component starts simultaneously with software development. QC includes software testing activities that have been determined by quality plans. Manual function and automaticity, performance, integration, usability, security, regression testing - all of this and many other types of testing consist of QC. Quality control must check whether the software is in accordance with the requirements and no severe defects will be revealed after the software is released.
Quality assurance is a process-oriented part of quality management, which must be introduced as early as the project planning stage. QA is related to the following questions:
Standards and software requirements What should obey?
What should every stakeholder (for example, project managers, bass, and developers) do for software for high quality?
What kind of software production process can prevent defects occur?
How do you set a process like that?
As the US Standard and US National Technology Institute was found, it was 6 times more expensive to fix bugs found during system testing rather than regulating software requirements that gathered with this bug will not appear. Mature quality assurance aims especially on prevention, does not detect existing defects.
Quality planning. The quality plan can be devoted to the practice of quality management or general quality of public companies or quality provisions during each project specifically. At the project level, QP usually formalizes quality management aspects such as:
Stakeholder roles and responsibilities related to quality assurance.
Project documentation and testing needed.
Software requirements specifications and a series of standard software must comply with.
Relevant types of testing.
Schedule of estimated testing, costs, and human resource arrangements for the appropriate project.
The training needed by the QA team member.
Reporting and schedule process.
Test KPI.
Risk mitigation plan.
General obstacles on the way to effective quality management include remiry by parties involved in the production of software, leaving important aspects of quality plans (such as testing metrics efficiency or professional training needed), and mixing QA with QC. While the three parts of the Quality Management are interdependent and none of them can be ignored if you aim for high quality software.
Where is your quality management now?
Effective quality management is indicated by the level of high QA maturity. In turn, mature quality assurance is not possible without clear quality planning and overall quality control activities. In this way, to start with increased quality management, you must find out where you are standing on the stairs of the QA maturity with the help of one of the models of QA maturity.
The Maturity Model Integration (TMMI) test, the most popular QA maturity model, provides a series of QA, QP and QC activities that are clear to each level of maturity for you to easily understand what has been done to provide quality software and what goals are still lying at front.
Early
This level is characterized by basic quality control activities, such as testing of smoke and internal integration, which aims to find the most critical bug functionality. software testing company activities are not well organized and documented. Quality guarantee and quality planning are almost non-existent.
Comments