1 / 9

Build Software or Build Airliners

Build Software or Build Airliners. Conley Read cread@cs.ucr.edu March 3, 2005 CS 245, Software Evolution Dr. Doug Tolbert. Overview. The Biggest Beast True Feats of Engineering The Boeing 747 Software Systems There is no “Silver Bullet” Your Questions Bonus: Complexity and Time.

kiral
Download Presentation

Build Software or Build Airliners

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. Build Software or Build Airliners ConleyRead cread@cs.ucr.edu March 3, 2005 CS 245, Software Evolution Dr. Doug Tolbert

  2. Overview • The Biggest Beast • True Feats of Engineering • The Boeing 747 • Software Systems • There is no “Silver Bullet” • Your Questions • Bonus: Complexity and Time

  3. The Biggest Beast • The Boeing 747 • 1970: 4.5 million parts, 3 million pins, rivets • 2003: 6 million parts, 3 million pins, rivets • Windows TM Operating System • Windows XP: 40 Million Lines of Code • Windows 2000: 20 Million Lines of Code • Linux Operating System • Kernel ver. 2.6: 5.7 Million Lines of Code

  4. Reliability Specification Owner Frozen Requirements No Unspecified DCRs Verification Budgets Schedule Complexity Innovation Near-term Requirements DCR stream In-place Evolution People Management Personalities Engineering Common Ground

  5. No “Silver Bullet” • Innovation in aerospace, not the 747! • Complexity per Year: 1% vs. 20% in Software • Boeing 747 35yrs Reliable WW2 technology • Software 49yrs Constant Innovation • Reinventing Engineering • Reliability follows Innovation • Being First means Learning the Hard Way • Build Software, not Airliners

  6. Your Questions? Bonus: Coming up Next!

  7. Complexity Over Time

  8. More Questions?

  9. Thank you! ConleyRead cread@cs.ucr.edu March 3, 2005 CS 245, Software Evolution Dr. Doug Tolbert

More Related