QUALITY ASSURANCE:QA i s defi ned as a procedure or se t o f procedures in tended to ensure that a product or serv ice under deve lopment (be fore work i s complete , as opposed to a f terwards) meets spec ifi ed requi rements . OR Act ions that you intend to use to prevent errors on a cer ta in task .

Qual i ty Contro l :(QC) i s a procedure or se t o f procedures intended to ensure that a manufactured product or per formed serv ice meets the requi rements o f the c l i ent or customer. OR making sure that no errors occurred a f ter the complet ion o f task .

Difference Between Quality Assurance and Quality Control

Identify Quality Assurance and Quality Control aspects in the given points

Project quality planDevelopment plan reviewContract proposal reviewSoftware requirements walkthroughDetailed design inspectionTest plan sign-offProgrammers quality manual instructionsSoftware unit testingSoftware integration testingSoftware use case preparation guidelines

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.

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.

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

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.

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.

Identification of Quality Assurance and Quality Control Points

Project quality plan Quality Assurance

Development plan review Quality ControlContract proposal review Quality ControlSoftware requirements walkthrough Quality ControlDetailed design inspection Quality ControlTest plan sign-off Quality ControlProgrammers quality manual instructions Quality Assurance

Software unit testing Quality ControlSoftware integration testing Quality ControlSoftware use case preparation guidelines Quality

Assurance

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.

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 codingMeasure the quality of requirements documentMeasure the quality of a testing engineering

work