1 / 31

CS598-YYZ : Reliable and Robust Software Overview

CS598-YYZ : Reliable and Robust Software Overview. Yuanyuan (YY) Zhou TA: Feng Qin Volunteer TA: Qingbo Zhu. Returning students. Welcome. Food and Drinks!. Introduce Yourself. Name? What year? Where from? Research interest? Research group? Summer experience?

naida-giles
Télécharger la présentation

CS598-YYZ : Reliable and Robust Software Overview

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. CS598-YYZ : Reliable and Robust SoftwareOverview Yuanyuan (YY) Zhou TA: Feng Qin Volunteer TA: Qingbo Zhu

  2. Returning students Welcome

  3. Food and Drinks!

  4. Introduce Yourself • Name? What year? Where from? • Research interest? Research group? • Summer experience? • What is needed the most to improve software reliability? • What would software reliability situation be in 10 years?

  5. Introduce TAs and Volunteers • Official TA: Feng Qin • Volunteer TA: Qingbo Zhu • Volunteers: • Zhenmin Li • Pin Zhou

  6. Buzzwords • Software • Robustness? • the degree to which software can function correctly in the presence of invalid inputs or stressful environment conditions • Reliability? • the probability of failure-free software operation for a specified period of time in a specified environment • Availability? • the probability that the component/system is operational at a given time • Dependability? • property of a software system such that reliance can justifiably be placed on the service it delivers , and it subsumes the usual attributes of reliability, availability, safety, and security etc. • Real life analogy?

  7. Why Software Reliability? • High availability is required for many applications • Average cost for an hour downtime exceeds $6M [Gartner’98] • Software failure greatly reduces system availability • Account for 40% of system failures [Marcus’00] • Contribute to 55% of severe vulnerabilities [CERT] • Reason: people make mistakes • Bugs • Mis-configurations • Security holes

  8. Why Software Reliability? • Check the OSDI’04 schedule • 4.5/9 sessions are related to reliability • Check the SOSP’05 schedule • 3/7 sessions are related to reliability • A quote from a PC: • “SOSP’05 continues the trend of reliability” • Call for proposals on software dependability: • NSF • DARPA • DOD

  9. Topic Matrix • Each student signs up into a cell • Presentation (not required) • Class Project • Surveys Reports and Presentations • Cell surveys (Due 9/26) • Column Surveys (Due 10/24) • Row Surveys (Due 11/28)

  10. Accomplishments • If you can face the challenge… Basic reliability concepts Software bug detections New directions

  11. Specific Goals • Learn basic concepts to software reliability • Failure models, failure injection, general recovery,… • Get familiar with recent research via critiques and surveys • Mis-configuration detection, bug detection, software failure recovery,… • Understand interaction with other fields • OS, machine learning, Statistics, data mining, architecture, compilers, software engineering • Explore new ideas through group projects. • Improve skills • Presentation • Critical thinking • Creative thinking

  12. Another Goal: Magic Box! • Another goal: • Put some common tricks into your magic box! • After each paper, we will summarize what tricks you have added into the box! • You don’t need too many tricks in the magic box, the challenges are • What is the problem? • Which trick to use? (don’t pull out an elephant!)

  13. Big Celebration at End • Poster/demo session with snacks • Sorry, no wine & Cheese! • Potential publications! • DSN, Dec 9 • Usenix Security Symposium, Jan • ASPLOS, Mar 8th • OSDI, May 6 • FSE, May • ICSE, Sept

  14. Topics • Check schedule for details • http://www-courses.cs.uiuc.edu/~cs598yyz/schedule.htm

  15. Where are the Papers from? • SOSP & OSDI • ASPLOS • FTCS/DSN • PLDI • ICSE & FSE • ISCA & Micro • …

  16. Pre-requisite • Basic operating systems • A plus if you have some basic background on • Compilers, programming languages • Software engineering • Machine learning, statistics, data mining… • Distributed computing • Computer network • Architecture

  17. http://www-courses.cs.uiuc.edu/~cs598yyz/schedule.htm Critique assignment Preliminary Schedule

  18. Your Responsibility • Present 2 papers (5%) • Read papers & Writing critiques: Due every Monday (5pm) (Hand-in to TA) (30%) • 3 each week • Participate in discussions (10%) • Viki & classroom discussions • 3 Surveys reports and presentations (20%) • Class project and final report & poster (35%)

  19. Critiques • Why? • Critical thinking • Learn from others • Format: 1 page only for each paper • Brief summary of the paper (2-3 sentences): • Key contributions of this paper (what are different from previous work): • Shortcomings of this paper (at least 2 points) • How can you improve this work? • What ideas can you borrow from this work to apply to your own work or project? • A question that you want to discuss

  20. Presentation • 2 paper presentation • Pick your papers & cell topic by Sept 6 • Send me email about your selection • First come first serve • Each topic at most 3 students • 20 minutes presentation • I will stop you after 20 minutes • Grade: 1-10 • By me, TA and randomly picked 2 students

  21. Class Format?

  22. Class Format • Student presentations • Survey presentation • Discussion

  23. Plea for Participation • 10% grading • Classroom • Newsgroup • Kids-approved candy for • Every good question • Every good answer • At the end of semester • Count all your candy (my candy is “specially” marked) • If you eat the candy, …Yummy…. Well, you’ve already got your reward! • Don’t sue me for giving you too many candy ( I don’t ask you to eat them, right?)

  24. Class Projects • 35% towards your final grade • Almost all projects are pre-defined based on the topic matrix • Additional background literature reading (Survey) • Sept 13: class project selection • Oct 3rd: Project position paper due • Motivation, related work, idea, feasibility, evaluation plan, expected results • Dec 9: class project presentation & demo • Summary Paper (at least 6 pages, 10pt font, single space, double-column, 1in margin)

  25. Class Policies • No late submission (except documented family or medical emergency) • No “incomplete” (except documented family or medical emergency) • Independent work

  26. Grading • Final grades are based on distribution • 40-50% students get A-, A, A+ • 35-45% students get B-, B, or B+ • 5-10% students get C+, C-, C

  27. Enough motivation? Enough interests? Enough background? Enough time? Is This the Right Class for You?

  28. CS598YYZ Information Web: http://www.cs.uiuc.edu/class/fa05/cs598yyz/ • Office Assistant: • Sheila Clark Office: 3253 DCLPhone: 244-6621sdclark@ad.uiuc.edu • Time: 3:30 – 4:45 Tuesday/Thursday • Newsgroup: TBA • Office Hours: by appointments • Instructor: Yuanyuan (YY) Zhou Office: SC 4233 Phone:  4-4563 Email: yyzhou@cs.uiuc.edu • Teaching Assistant: Feng Qin office: SC 4217 Phone: 244-0432Email: fengqin@uiuc.edu • TA Volunteer Qingbo Zhu Office: SC4215 Phone: 244-3064 Email: qzhu1@uiuc.edu

  29. Who will do the next week’s presentation? • Up to 3 volunteers are needed • Advantages: • “Discount” for the presentation grades

  30. Questions?

More Related