30 likes | 124 Views
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: 1 st : machine code—binary streams: CPU 50s 2 nd : assembly—readable codes: english like code
E N D
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
Software crisis, late 60s early 70s (COBOL) late projects, over-budget, unreliable, hard to maintain hard to maintain yy 19992000 • Skip list: 212? data structure and math express lines:
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