3156-3 - COMS W3156: Software Engineering, Fall 2001...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
COMS W3156: Software Engineering, Fall 2001 Lecture #3: Intro to software engineering and the project: the big catch-up lecture Janak J Parekh janak@cs.columbia.edu
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Administrativia (I) Website is your friend You are expected to be up-to-date on the readings, in particular – the course is about to “speed up” Questionnaire If you have not yet filled it out, do it today We will be determining TA office hours and recitations using this information
Background image of page 2
Administrativia (II) This should be the last set of slides to be posted so late – use the later PDF’s for notes Bulletin board accounts created! Username is your UNI, password is last 4 digits of your SSN. If you can’t login: Make sure you’ve done the questionnaire! Otherwise, email suhit@cs.columbia.edu
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Next class Schach, chapter 3; Lifecycles Will begin chapter 5 content, Tools, but reading not due next week Group proposals to be submitted Extremely simple: Group name List of people in group Should be between 4 and 6 people, preferably 5 More info on website later today
Background image of page 4
Today’s class I was going to include another anecdote, but we’re a little behind, so we’re going to play some catch-up today Topics to discuss Intro to Software Engineering Software Engineering Teams (Schach) Project introduction Process model overview XML
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Introduction to Software Engineering The practice, not the course In 1968, it was pointed out that software is delivered late , overbudget , and with many residual faults Err… not much has changed, has it? Played a game recently? Updated drivers
Background image of page 6
Bridges vs. operating systems Schach likes this example 1. Crash: a bridge needs to be completely rebuilt; software is just rebooted 2. Imperfect engineering: we “accept” faults, while we cannot on a bridge… is software really engineered? 3. Complexity: software uses discrete states – a bit change != wind 4. Maintenance: no bridge is half-replaced, but this happens often with software
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Economics of software engineering Put simply, it’s not apparent If a particular development mechanism is cheaper, that does not necessarily imply better – code that’s more difficult to maintain may be the result Yet, the cheaper mechanism may be adopted A tremendous amount of software development is maintenance and evolution – Schach’s cup of tea
Background image of page 8
Maintenance aspects Software, as previously mentioned, is not a build-once-and-throw-away process – that’s
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 44

3156-3 - COMS W3156: Software Engineering, Fall 2001...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online