Difference Between Quality Assurance and Quality Control

1. Difference Between Quality Assurance and Quality Control Quality Assurance: QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is complete, as opposed to afterwards) meets specified requirements. OR Actions that you intend to use to prevent errors on a certain task. Quality Control: (QC) is a procedure or set of procedures intended to ensure that a manufactured product or performed service meets the requirements of the client or customer. OR making sure that no errors occurred after the completion of task.

2. Identify Quality Assurance and Quality Control aspects in the given points Project quality plan Development plan review Contract proposal review Software requirements walkthrough Detailed design inspection Test plan sign-off Programmers quality manual instructions Software unit testing Software integration testing Software use case preparation guidelines

3. Identification of Quality Assurance and Quality Control Points • Project Quality Plan: • A plan defining the key quality criteria, quality control and audit processes to be applied to project management and specialist work in a specified project. It will be part of the text in the Project Initiation Document. • Development plan review: • Development planning refers to the strategic measurable goals that a person, organization or community plans to meet within a certain amount of time.

4. Identification of Quality Assurance and Quality Control Points • Contract proposal review: • Peer review of R&D contract proposals provides objective evaluation of technical aspects and acceptability or unacceptability of specific proposals based on the technical evaluation criteria. Further it helps to achieve program goals by identifying the best technically qualified offerors. • Software requirements walkthrough: • walkthrough is step by step simulation of the execution of a procedure, as when walking through code line by line, with an imagined set of inputs. The term has been extended to the review of material that is not procedural, such as data descriptions, reference manuals, specifications, etc.

5. Identification of Quality Assurance and Quality Control Points • Detailed design inspection: • A formal evaluation technique in which software requirements, design, or code are examined in detail by person or group other than the author to detect faults, violations of development standards, and other problems. • Test plan sign-off: • Number of requirements implemented should match the number of requirements provided • No "critical" bugs • List of "Serious" bugs • Number of "non-critical" bugs • Number of test cases executed per component • What testing areas have not been covered • Number of test cases passed • Number of test cases failed

6. Identification of Quality Assurance and Quality Control Points • Programmers quality manual instructions: • A typical quality manual will include the company's quality policy and goals, as well as a detailed description of its quality control system that might include staff roles and relationships, procedures, systems and any other resources that relate to producing high quality goods or services. • Software unit testing: • Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually and independently tested for proper operation. • Software integration testing: • Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.

7. Identification of Quality Assurance and Quality Control Points • Software use case preparation guidelines: • use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal.

8. Identification of Quality Assurance and Quality Control Points Project quality plan QualityAssurance Development plan review Quality Control Contract proposal review Quality Control Software requirements walkthrough Quality Control Detailed design inspection Quality Control Test plan sign-off Quality Control Programmers quality manual instructions Quality Assurance Software unit testing Quality Control Software integration testing Quality Control Software use case preparation guidelines Quality Assurance

9. software quality metric The kind of metrics employed generally account for whether the quality requirements have been achieved or are likely to be achieved during the software development process. As a quality assurance process, a metric is needed to be revalidated every time it is used. Software Quality Metrics focus on the process, project and product. By analyzing the metrics the organization can take corrective action to fix those areas in the process, project or product which are the cause of the software defects.

10. Suggest a software quality metric that will perform the following Measure the speed of a student course registration module Measure how easy it is to learn new student data entry module Measure how many student can be registered in one hour Measure the quality of a programmer coding Measure the quality of requirements document Measure the quality of a testing engineering work