1. 1.1 The Evolving Role of Software
What makes software so important?
The Law of Unintended Consequences
What are some positive and negative examples of the impact of software on society?
Do software engineers have a moral and/or ethical responsibility to ensure that the software they build does no serious harm?
The Lone Programmer

2. 1.1 The Evolving Role of Software
It takes software so long to be finished because…
Development costs are so high because…
We can’t find errors before we give software to our customers because…
We continue to have difficulty in measuring progress as software is developed because…

3. 1.2 Software Software is engineered Software doesn’t wear out
how is software different from other engineered artifacts?
Software doesn’t wear out
(see next slide)
Custom built versus component based software
why isn’t component based development more popular/successful?

4. Software: Wear vs. Deterioration

5. 1.3 The Changing Nature of Software
system software
application software
engineering/scientific software
embedded software
product-line software
WebApps (web applications)
AI software
which category is the most complex to develop?
what are the current “hot” types of software?

6. 1.4 Legacy Software What are legacy systems?
What factors can cause legacy software to require change?
If software maintenance takes more resources than new software creation then why do companies bother to modify software? Why don’t they develop new software instead?

7. 1.5 Software Myths
Myth: If we get behind schedule we can add more programmers and catch up (mythical man-month)
Myth: If I decide to outsource the software project to a third party, I can just relax and let that firm build it
Myth: Project requirements continually change, but change can be easily accommodated because software is flexible. …
Do the myths have any elements of truth?
What are some other software myths?