PLEASE SUBMIT ALL WRITTEN ASSIGNMENTS IN WORD, NOT PDF SO I CAN COMMENT ON THEM. ALSO, PUT YOUR LAST NAME IN YOUR ASSIGNMENT NAME.
Put all your writeups for each week in ONE file. Do not submit a bunch of small files for each week.
The readings listed below must be completed before the session in which they are listed so we can discuss them and your written assignment. They are thus due at 9am on the day of class.
Read, summarize, and critique
Leveson, The Therac-25 Accident (pdf)
Flying in Place: The FAA's Air Control Fiasco (pdf)
Davis, Software Lemmingineering
Brooks, No Silver Bullet
Leveson,
The Role of Software in Spacecraft Accidents
Software and the Challenge of Flight Control
Augustine, Yes But Will it Work in Theory?
Leveson, Why is Software Engineering Difficult?
Read only
Engineering a Safer World: Chapter 3
Read and summarize only
Booten and Ramo, The Development of System
Engineering
Papers on history of SE by Miles, Machol and Miles,
Pickering
Leveson, System of Systems
Read, summarize, and critique
Excerpts from a Mike Griffin paper
Griffin, How Do We Fix System Engineering
Read only
Wikipedia on
Software Development Processes
Read, summarize, and critique
Paulk, et.al, The Capability Maturity Model for
Software
Bach, The Immaturity of CMM
Bach, Enough About Process: What we Need are Heroes
Gray, No Cowboy Programmers!
Mackey, Mars versus Venus
McConnell, Cargo Cult Software Engineering
Martin, eXtreme Programming
Highsmith and Cockburn, Agile Software Development: The Business of Innovation
Pressman,Can Internet-Based Applications be Engineered?
email about Agile experiences
Learning from Failure in Systems Engineering
Software Defects and Agile
Question for Class Discussion: What project characteristics are
most important when selecting an appropriate life cycle model?
Lawrence, Wiegers, Ebert: The Top Risks of Requirements Engineering
Leishman and Cook, Requirements Risks Can Drown Software Projects
Read and summarize.
Wing, A Specifier's Introduction to Formal Methods
(This one may be tough reading for some of you -- you can skim it if you
are feeling overwhelmed by the discrete math)
Read and summarize only:
Leveson, Intent Specifications
The writing assignment for 16.355 for the last week is equivalent to a
"take home final exam" and includes the following three papers
for the usual summary and citique except for the Leveson one:
Shapiro, Splitting the Difference ...
Bach, What Software Reality is Really About
Leveson, Software Engineering ... Do not critique
my paper. Instead write a page or so on what you would have written if you
were asked to do what I was, i.e., what do you think the future of software/system
engineering should be in the next 25 years
