 Hello guys, welcome to the session on software testing quality assurance, quality concepts. At the end of this session students will be able to describe the quality concepts, what is quality and the software quality dilemma. What is quality? The American heritage dictionary that defines quality as a characteristic or the attribute of something. For software there are two kinds of quality that may be encountered. Quality of design, end campuses, requirements, specifications and the design of system. Quality of confirmation is an issue focused primarily on implementation and the user satisfaction it is a combination of the compliant product, good quality and the delivery within the budget and schedule. What is quality? Quality is extremely hard to define and it is simply stated fit for use or purpose. It is all about meeting the needs and expectations of the customers with respect to the functionality, design, reliability, durability and the price of the product. What is an assurance? Assurance is nothing but a positive declaration on a product or the service which gives the confidence. It is certainty of a product or a services which it will work well. It provides a guarantee that the product will work without any problems as per the expectations or the requirements. How to do quality assurance? The complete process, the quality assurance has defined a cycle called PDCA cycle. So, the phases of the cycles are plan, do, check and act PDCA. So, these above steps are repeated to ensure that the processes followed in the organization are evaluated and improved on a periodic basis. Let us look into the above steps in detail that is plan, the organization should plan and establish the process related objectives and determine the processes that are required to deliver a high quality end product. Do that is development and the testing of the processes and also do change in the processes. Check that is monitoring of the processes, modify the processes and check whether it meets the predetermined objectives. Act, implement actions that are necessary to achieve improvements in the processes. An organization must use the quality assurance to ensure that the product is designed and implemented with the correct procedure. So, this helps to reduce the problems and errors in the final product. What is quality control? Quality control popularly abbreviated as QC that is quality control. It is a software engineering process that is used to ensure the quality in a product or a service. It does not deal with the processes used to create a product rather it examines the quality of the end products and the final outcomes. The main aim of this quality control is to check whether the products meet the specification and the requirements of the customer. If an issue or the problem is identified it needs to be fixed before delivery to the customer. Quality control also evaluates the people on their quality level, skill sets and it imparts the training and certifications. This evaluation is required for the service based organizations and helps to provide a perfect service to the customer. Let us discuss the difference between the quality control and quality assurance. Sometimes quality control is confused with the quality assurance. Quality control is to examine the product or the service and check for the result. Quality assurance is to be examined the processors and make changes to the processors which lead to the end product. So, the difference between this quality control and quality assurance the product in quality control that associated in the quality assurance as process and in quality control it is a reactive and assurance it is a proactive and line function and in quality assurance it is a stop function and quality control find defects. So, in quality assurance means it is it prevents the defect it prevents the defects. The difference between the quality control and quality assurance where the examples of these activities are given the quality control activities are like walkthrough, testing, inspection, checkpoint review. So, these are the activities of the quality control and quality assurance activities are like quality edit defining the processors, the defining standard processors, tool identification and selection training of the quality standards and the processors. So, the above activities of the concerned with this quality control and quality assurance of any product and not essential the software. So, with respect to the software the quality assurance becomes software quality assurance and quality control becomes software testing with respect to the software concern. Let us discuss the difference between the software quality assurance and software testing. Software quality assurance is about engineering process that ensures the quality. Software testing is it to test a product for a problems before the product goes live. In software quality assurance it involves the activities related to the implementation of the processors, procedures and standards for example, the edits training. In software testing it involves the active concerning verification of the product for example, review testing. Software quality assurance that it is a process focused and software testing it is a product focused. Software quality assurance it is a preventive technique software testing is a corrective technique. So, SQA it is a proactive measure and testing is a reactive measure. The scope of software quality assurance is applied to all the products that will be created by the organization and in the software testing the scope of the software testing that applies to the particular products being tested it applies to the particular product that being tested. So let us pause the video for a while and answer the question. Mention the different phases of quality assurance cycle. So the different phases of the quality assurance cycles are plan, do, CA that is PDCA, plan, do, check and act. Let us discuss the best practices for quality assurance. The following table explains the difference between software quality assurance and software testing. So, it creates a robust testing environment and it selects the release criteria carefully applies automated testing to high risk areas to save the money, time and also it helps to fasten the entire process. Simulate the time appropriately for each process, the schedule allocation for each process and it is important to prioritize the bug fixes based on the software usage. Form the dedicated security and performance testing team. Simulate the customer accounts similar to the production environment. So these are some of the best practices of quality assurance. Quality assurance functions, there are five primary quality assurance functions that is a technology transfer, validation, documentation, assuring the quality of the products and quality improvement plans. Technology transfer means these functions that involves getting a product design documents as well as trial and error of the data and its evaluation. The documents are distributed, checked and approved. So this is a technology transfer activity and validation means here the validation master plan for entire system is prepared and approval of the test criteria for validating the product and process is set. So resource planning for execution of the validation plan is done. The documentation here the function controls, the distribution and archiving of documents. Any change in the document is made by adopting the proper change control procedures and assuring the quality of the product, quality improvement plans. So we discussed about the different the quality, the quality assurance activities and the concept of quality and assurance, the difference between the quality control and assurance. These are the references I refer. Thank you.