Software Quality Control

Quality Assurance :

- It is a Assurance activity,emphasizing on the standards and procedures to be followed while developing an application

- It is a Preventive action taken before hand to ensure the product that developed are defect free

- It is a systematic actions necessary to provide enough confidence that a product or service will satisfy the given requirements for quality.

Quality Control

- It is a Corrective action

- Inspection if the developed application follows the standards and procedures by using the checklists.

Quality assurance is planed and systematic set of activities necessary to provide adequate confidence that products/services will confirm to the specified requirements. It is a staff function, Defect prevention based.

Quality control is the process in which product quality is compared with applicable standards and action will be taken when non conformance occurred. It is a line function, Defect design based.

USL is Upper Specification limit. This is the the acceptable level and defined by Customer. beyond which the product is rejected.

If the average of all measurements falls relatively close to an understood point (on target), then the process is said to be accurate.

The design of experiments may be used to help improve the capability of a process by identifying the process and product variables that affect the mean and the variance of the quality characteristic(s) of the product.

D) Binomial

the p-chart is a type of control chart used to monitor the proportion of nonconforming units in a sample, where the sample proportion nonconforming is defined as the ratio of the number of nonconforming units to the sample size

What is the cost the business would have to incur if a big error was missed if these steps were not followed properly? Damages in terms of money (cost of litigation, regulatore claims, cost of fixing those bugs) and to the brand name of the company (open to discussion).

For me, that is the cost of Quality

DRR = # of Defects Rejected/Tester to assess the tester performance

DRR = # of Defects Rejected/module to assess the module complexity

DRR = # of Defects Rejected/Team/Project to assess the team performance.

and

DLR = # of Defects uncovered/Tester

DLR = # of Defects uncovered/Module

DLR = # of Defects uncovered/Project

( Uncovered- Defects missed out by the testing team)

Accepted practice uses a width of three standard deviations around the population mean ( 3) to establish the control limits for control chart.Anything that falls between the range of ( 3) is teh common cause of variation & anything that falls out of the range of ( 3) is special cause of variation

different type of metrics captured

Defect Density- no of defects par KLOC

Defect Severity distribution- which measured in term of defect severity

Defect Removal Effectiveness- total number of defects prior to delivery

Review Effectiveness

The answer to this question depends on its context. If you are referring to the Software Development Life Cycle (SDLC), then the answer still depends on the model you are referring to. The number and nature of phases varies greatly between software development models. Generally, the phases of software development are:

Phase 1: Planning (a.k.a. the Requirements Phase)

Phase 2: Design

Phase 3: Implementation

Phase 4: Verification

Phase 5: Maintenance

A) Meaning 99.999997% perfect; only 3.4 defects in a million.

Lower specification limit (LSL)

Also known as the lower control limit (LCL).

Here's a simplified response:

1) Begin by learning about the products and services; gain domain knowledge

2) Understand workflow and processes throughout the product life cycles

3) Determine where defects are caused in these workflows and processes

4) Establish checkpoints at these junctures

5) Establish reliable methods of defect detection

6) Establish quality standards and targets for quality improvement

7) Tie Quality Control effort to organization's cost and profitability

8) Report findings

The maintenance phase is considered to be the blackout phase. Maintenance is the last stage of the software development life cycle. After the product has been released, the maintenance phase keeps the software up to date with environment changes and changing user requirements. It is called the blackout phase because the system is not accessible and is said to "black out" during maintenance.

The Three Measures of Common use in Quality Control is Mean, Median and Mode

The three commonly used measures in quality control are Mean (also called as Average), Median (is the value that divides a series of ordered observations so that the number of items above it equals to the number below it) and Mode (is the value that occurs with the highest frequency).

QA people roles will be do the auditing to make sure that in testing, everything has happened as expected (proper documents created, have been they tracked in exact time, are all the documents stored in share path?....etc) so that they are making sure about the process which delivers the quality products.

product quality means we concentrate always final quality but in case of process quality we set the process parameter