1 / 19

Semat: Software Engineering Method and Theory or What are we doing here?

Semat: Software Engineering Method and Theory or What are we doing here?. Richard Mark Soley, Ph.D. A Programmer I Know. Definitions Are Hard. What’s an Engineer? An Engineer is someone who can do for fifty cents what any damn fool can do for a dollar. (Mark Twain)

lilith
Download Presentation

Semat: Software Engineering Method and Theory or What are we doing here?

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. Semat: Software Engineering Method and TheoryorWhat are we doing here? Richard Mark Soley, Ph.D.

  2. A Programmer I Know

  3. Definitions Are Hard What’s an Engineer? • An Engineer is someone who can do for fifty cents what any damn fool can do for a dollar. (Mark Twain) • The optimist says the cup is half full; the pessimist claims it’s half empty. Engineers say the cup is twice as big as it needs to be. (Anonymous) Unfortunately, we need to do better than that.

  4. Because Agreements Are Hard B A B A A B

  5. Conceptual Inertia • “The Structure of Scientific Revolutions” (Thomas Kuhn, 1962) • A scientific community cannot practice its trade without some set of received beliefs • The infamous Paradigm Shift

  6. From Here to Eternity

  7. More Paradigm Shift

  8. The 20th Century Reformation

  9. Our 21st Century Reformation

  10. 1911 1913 1921 1927 1933 Some Bad News

  11. And Some Worse News

  12. We Need a (Useful) Theory

  13. Call for Action Software engineering is gravely hampered today by immature practices. Specific problems include: • The prevalence of fads more typical of fashion industry than of an engineering discipline. • The lack of a sound, widely accepted theoretical basis. • The huge number of methods and method variants, with differences little understood and artificially magnified. • The lack of credible experimental evaluation and validation. • The split between industry practice and academic research. We support a process to refound software engineering based on a solid theory, proven principles and best practices that: • Include a kernel of widely-agreed elements, extensible for specific uses • Addresses both technology and people issues • Are supported by industry, academia, researchers and users • Support extension in the face of changing requirements and technology

  14. The Schema of Our Effort

  15. Tracks of our Tears • Definitions • Theory • Universals • Kernel Language • Assessment

  16. “Tracks” of our Tears • This introduction (nearly over!) • Everyone who sent a position in time gets to introduce his position (briefly) • Five track discussions in plenary • Introduction by Track Chair • Open Discussion • Troika partners give closing position

  17. We Started This Craziness

  18. But It Takes a Community

  19. Please Be Patient • There are many points of view here • There are many more in the wider industry • None of us are patient… • …but all of us need to consider other points of view. The focus is on delivery of v.1 in one year, so don’t be too patient 

More Related