Software Quality Assurance(SQA) and Testing: metric

Showing posts with label metric. Show all posts

Monday, June 15, 2009

There are some ways for metrics and measurements for data

Measurements are collected as per their definition at defined points as mentioned in Organization Metrics File
Data is collected and compiled by using Project Summary, Help Desk, eRMS, Analysis Reports, Peer Review Analysis Reports etc
Verification of the measurement data is done independently to check completeness, integrity, accuracy by SQA & SEG for the data that they provide to each other
Once the data is collected will be assessed independently by QE
Project may consider additional metrics to better manage their project
Data should be available for use only by appropriate groups and personnel.

Here are the points to be noted

Software requirements are the foundation from which quality is measured. Lack of conformance to requirements is lack of quality.
Specified standards define a set of development criteria that guide the manner in which software is engineered. If the criteria are not followed, lack of quality will almost surely result.
There is a set of implicit requirements that often goes unmentioned (e.g., the desire for ease of use). If software conforms to its explicit requirements but fails to meet implicit requirements, software quality is suspect.

So there is relationship. As we have measurement correct we will have solid requirements and on that at the quality will be fine

Here are the main steps.

Derive the software measures and metrics that are appropriate for the representation of software.
Data required to derive the formulated metrics are collected.
Once computed, appropriate metrics are analyzed on pre-established guidelines and past data.
The results of the analysis are interpreted to gain insight into the quality of the software, and the results of the interpretation lead to modification of work products arising out of analysis, design, code, or test.