SENG521 (Fall 2002 ) [email protected]1 SENG 521 SENG 521 Software Reliability & Software Reliability & Testing Testing Best Practice SRE (Part 12c) Department of Electrical & Computer Engineering, University of Calgary B.H. Far ( [email protected]) http://www.enel.ucalgary.ca/~far/Lectures/SENG521/12c/
SENG 521 Software Reliability & Testing. Best Practice SRE (Part 12c). Department of Electrical & Computer Engineering, University of Calgary B.H. Far ( [email protected] ) http://www.enel.ucalgary.ca/~far/Lectures/SENG521/12c/. Incremental Implementation. - PowerPoint PPT Presentation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Feasibility PhaseFeasibility Phase Activity 1:Activity 1: Define and classify failures
Define failure from customer’s perspective Group identified failures into a group of severity classes from
customer’s perspective Usually 3-4 classes are sufficient
Activity 2:Activity 2: Identify customer reliability needs What is the level of reliability that the customer needs? Who are the rival companies and what are rival products and what is
their reliability?
Activity 3:Activity 3: Determine operational profile Based on the tasks performed and the environmental factors
System Test PhaseSystem Test Phase Activity 11:Activity 11: Determine operational profile used
for testing Decide upon critical operations Decide upon need of multiplicity of operational profile
Activity 12:Activity 12: Track testing progress and certify that reliability objectives are met Conduct feature test, regression test and performance and
Post Delivery Phase /2Post Delivery Phase /2 Activity 17:Activity 17: Time new feature introduction by
monitoring reliability New features bring new defects. Add new features
desired by the customers if they can be managed without sacrificing reliability of the whole system
Activity 18:Activity 18: Guide product and process improvement with reliability measures Root-cause analysis for the faults Why the fault was not detected earlier in the development
phase and what should be done to reduce the probability of introducing similar faults
Activity 15-16:Activity 15-16: Monitor field reliability vs objectives, track customer satisfaction with reliability Benefits:Benefits: Maximize likelihood of pleasing customer with
Post Delivery Phase: Post Delivery Phase: BenefitsBenefits
Activity 17:Activity 17: Time new feature introduction by monitoring reliability Benefits:Benefits: Ensure that software continues to meet
customer reliability needs in the field
Activity 18:Activity 18: Guide product and process improvement with reliability measures Benefits: Benefits: Maximize cost-effectiveness of product and