1 / 18

CSE 300: Software Reliability Engineering

CSE 300: Software Reliability Engineering. Topics covered: Project overview. Objectives. Introduce the state-of-the-art in reliability engineering. Cultivate the ability to understand and critique research papers.

malcolm-gamble
Télécharger la présentation

CSE 300: Software Reliability Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CSE 300: Software Reliability Engineering Topics covered: Project overview

  2. Objectives • Introduce the state-of-the-art in reliability engineering. • Cultivate the ability to understand and critique research papers. • Implement and adapt reliability analysis techniques presented in research papers. • Develop communication skills and ability to work in a team • Enhance presentation skills

  3. Project components • Each project will be conducted by a team of two students • Select your partner and let me know. • Each project will be based on one research paper • Related to (or may extend) the topics covered in class. • Three components: • Presentation • Implementation • Report

  4. Presentation • Each group will be expected to present the chosen paper to the class. • Each presentation will be allotted 15 minutes. • Presentation should address the following: • Motivation • Problem description • Approach • Advantages • Disadvantages • What would be your approach?

  5. Implementation • Implement a key technique: • More than one technique presented in some papers. • Identify one technique and implement it. • Language/package of your choice. • Reproduce at least some of the results

  6. Report • Consist of three parts: • Part I: Summary & Critique • Overview of the paper. • Advantages & disadvantages • Approach you would adopt • Part II: Implementation • Decisions about package/language chosen • Problems encountered • Results • Part III: Division of work • How did you divide the work • Comments on your experience in working as a team.

  7. Grading scheme • Project is 24% of the grade • Maximum of 100 points • Breakdown: • Presentation: 25 • Implementation: 40 • Report: 35

  8. Paper #1 • Title: Log-logistic Software Reliability Growth Model • Overview: • Describes a finite failure NHPP software reliability growth model. • Implementation: • Maximum likelihood estimates of model parameters.

  9. Paper #2 • Title: Software Failure Rate and Reliability Incorporating Repair Policies • Overview: • Simulation approach to incorporate repair into software reliability growth models • Implementation: • Rate-based simulation procedure to incorporate repair

  10. Paper #3 • Title: An Architecture-Based Software Reliability Model • Overview: • Reliability analysis of different architecture styles such as batch-sequential, parallel/pipe-filter etc. • Implementation: • Reliability analysis methodology for any two styles

  11. Paper #4 • Title: Reliability Simulation of Component-Based Software Systems • Overview: • Simulation approach for architecture-based reliability analysis • Two types of applications: terminating and control system with feedback loop. • Implementation: • Simulation procedure for terminating application

  12. Paper #5 • Title: Reliability Analysis of Pipe and Filter Architecture Style • Overview: • A methodology for reliability analysis of pipe and filter architecture • Linear topology with and without feedback • Implementation: • Expressions for reliability analysis for linear topology with and without feedback

  13. Paper #6 • Title: Quantifying the variance in application reliability • Overview: • Determine how variances in component reliabilities can be propagated to the variance in application reliability based on architecture • Taylor series expressions, theory of random sums • Implementation: • Variance quantification expressions

  14. Paper #7 • Title: Assessing Uncertainty in Reliability of Component-Based Software Systems • Overview: • Determine how variances in component reliabilities can be propagated to the variance in application reliability based on architecture • Two techniques: Method of moments, Monte Carlo simulation • Implementation: • Any one of the techniques for variance quantification

  15. Paper #8 • Title: Software Reliability Analysis with Component-Level Fault Tolerance • Overview: • Architecture-based reliability analysis, some components may have fault tolerant configurations • Implementation: • Expressions for reliability analysis which incorporate coverage parameters of components

  16. Paper #9 • Title: Variance Expressions for Software Reliability Growth Models • Overview: • A methodology to compute the variance in the reliability prediction obtained using NHPP model • Taylor series expressions for the mean and variance of a function of random variable • Implementation: • Expressions for quantification of variance

  17. Paper #10, #11, .. • Any other paper that you like

  18. Logistics • Papers will be assigned on a first-come, first-serve basis. • Presentations will be held in class a week after Thanksgiving break: • Dec. 6 – 4 groups • Dec. 8 – 5 groups • Report will be due on Dec. 8 • No class in the week of Nov. 29. • Final exam will be assigned Dec. 8, and due Dec. 15 • I will be happy to answer questions!

More Related