Upload
oswald-cobb
View
214
Download
1
Embed Size (px)
Citation preview
Viking Quality ReportTeam Assignment 9
Team 2-1
Content
Viking Product Defect LifecycleDefect Detection Arrival Rate by Severity MetricDefects Detection by StatusActive Defect by StatusViking Project Defect Data AnalyzeViking Project Defect data Conclusion and Recommendation
Viking Product Defect Lifecycle
Defect Detection Arrival Rate by Severity Metric
Measurement Functions:Defect Detection Arrival rate by Severity = Number of defects detected that periodBase Measure Measurement MethodNumber of defects detected by severity
Count all defects in the week follow each type severity
Measurement Functions and Methods
Decision CriteriaReady to Ship: No critical, no high defects and <= 5 medium defects in week 7
Standardized DefinitionsAttribute/Entity DefinitionDefect A software fault that requires a
correctionSeverity The impact of the defect on the
operation of the software (i.e., critical, high, medium, low)
Defection arrival rate The number of newly opened defects during the period
Report Format
Defects Detection by StatusStandardized Definitions
Attribute/Entity DefinitionDefect Open Status of new defect, not yet
assigned Approved The defect has been approved for
resolutionAssigned The defects has been assigned to
a software engineer who will work on the defect
Resolved The software engineer responsible for fixing the defect believes that the defect is fixed. Typically this means that the updated product passes all unit and integration tests.
Not- resolved Tested The defect is considered resolved
by the QA teamClosed The updated product is available
for release. Sometimes the original defect submitter is responsible for closing defects, but often this isn't possible.
Measurement Functions:Open defects= count of open defectsApproved defects= count of approved defectsAssigned defects = count of assigned defectsResolved defects = count of resolved defectsNot- resolved defects= count of not- resolved defectsTested defects= count of tested defectsClosed defects= count of closed defects
Measurement Functions and Methods
Decision CriteriaReady to ship: For non- closed defects:
No non-closed critical defectsLess than 10 non-closed high defectsLess than 25 non-closed medium defects
For arrival rate: No new defects in the last week of system test
Report Format
Active Defect by Status
Measurement Functions and Methods
Decision Criteria
Standardized Definitions
Attribute/Entity Definition
Active defect Active defect that are from status approved to status tested of a defect
Measurement Functions:Active defect = Approved defect+ assigned defect+ resolved defect+ not resolved defect+ tested defect
Ready to ship: Less than 10 active defects in the last week of system test
Report Format
Viking Project Defect Data Analyze
Assume the Viking Product has been in system test for 7 week, the current week is #7
There are about more than 5 and less than 23 defects has been opened per week, the variance is about 18 defects
And there about more than 12 and less than 71 defects has been close per week, the variance is much more than the open frequent. For at the current time (week 7), number of open defects is the highest and there is any defect that resolved.
There is no defect to be reopen or rejected. All defects are considering to be approved and assign to 2 developers, Bob and Anjuli.
Viking Project Defect data Conclusion and Recommendation
Based on data analysis, we can see status of product at week 7 is:We should not ship to customer (using 2 quality to evaluate : correctness and ready to ship)
Need to add more resources for fixing defects to ensure fixing meet standard
Need build process for ensuring quality of product.Viking CCB has no fix meeting day and schedule, so the recommendation is they need to have the meeting schedule and rule.