1 / 3

Exploring Software Engineering Paradigms and Generations: Solving the Software Crisis

This text delves into the history and evolution of programming languages, from machine code to object-oriented programming. It discusses the software crisis of the late 60s, early 70s, and offers insights on Software Engineering practices.

halla-sykes
Télécharger la présentation

Exploring Software Engineering Paradigms and Generations: Solving the Software Crisis

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. CS 322 week 1 Read syllabus, group work, clustering-based grading (fair) Why software engineering: ABET, what’s wrong with code+fix Four generations of Programming Language: 1st: machine code—binary streams: CPU 50s 2nd: assembly—readable codes: english like code 3rd: procedural: 3 types C(2.5)/Cobol/pascal: wirth, Dijkstra/PL1 4th: OO: java 95% inheritance: reuse, localize, DB: SQL-like: declarative (prolog) what to do; all other: how 3 prog. Paradigm: functional, imperative, logical 58, MIT LISP Haskell/scala: no side effects, lazy: eager, first-class object (short) recursion func

  2. Software crisis, late 60s early 70s (COBOL) late projects, over-budget, unreliable, hard to maintain hard to maintain yy 19992000 • Skip list: 212? data structure and math express lines:

  3. Course overview: shameless copycat of ordinary Engr investigation: meetings/talks/readings (in)feasible: early 60s, MIT: computer vision as a course project, security system: replace guards: compare human face vs id photo iris: violating, fingerprint: dirty false negative specification report: legal doc estimation and planning: $$+people+pl+… design: 2 levels data struct+ alg design implementation: coding+debugging (self) testing: different people avoid subjectivity alpha vesion: internal version, beta version: outsiders maintenance and evolution: diff version

More Related