|
| CMSC 435: Software Engineering |
| Basic Information |
| Name | Office | Office Hours | |
| Marvin Zelkowitz | AVW 4121 | Mon 10am-11 & Wed 11am-noon | mvz@cs.umd.edu |
| In general whenever my door is open - Usually in the mornings. It is best to email first to make sure I am around. |
| Course News |
| Lectures |
| Date | Lecture Topic | Slides | Textbook and other references |
| 1/27 | Introduction & Overview, Software engineering and system engineering | ch1 | Chapter 1 |
| 2/1-3 | Processes, Project description |
ch2
ch2-b (Revised 2/8/05) proj-org | Chapter 2 |
| 2/8-10 | Project management, Risk | ch3 (Revised 2/10/05) | Chapter 3 |
| 2/15-17 | Requirements | Ch4 |
Chapter 4
UML tutorial: Sequence diagrams - Robert Martin The formalization of message sequence charts - S. Mauw |
| 2/22 | Specifications, Group presentations on your group project organization | ch4-b | |
| 2/24-3/1 | Software architecture and design | ch5 (Reformatted 2/23/05) |
Mary Shaw, "Making choices: A comparison of styles for software architecture,"
IEEE Software, 1995, vol. 12, no. 6, pp. 27-41.
Chapter 5 Chapter 6 |
| 3/3 | Software reuse | ch5-b (Revised 3/8/05) | |
| 3/8 | Configuration management | ch6 | |
| 3/10 | Testing | ch8 |
Chapter 8
Chapter 9 |
| 3/15 | Reliability | reliability | |
| 3/17 | Midterm | Sample midterm
Spring 2005 midterm with answers | Material assigned references, slides and class presentations |
| 3/22-24 | Spring Break | NO CLASSES | NO CLASSES |
| 3/29-31 | Formal specifications | formal | "The role of verification in the software specification process," by M. Zelkowitz, Advances in Computers 36, Academic Press (1993) 43-109 (pdf). Paper is 55 pages. We will probably only discuss 1-16. |
| 4/5 | Verification, Inspections, Cleanroom | inspections |
"Advances in Software Inspections" by M. Fagan, IEEE Trans. on Software
Engineering (12)7 (July, 1986) 744-751.
Notes from Tom Gilb |
| 4/7 | Lab exercise: An inspection
Due: Project 2 due. Due: Revised WBS and Risk reports | An in-class inspection will be held on a module of your project. | |
| 4/12 | Maintenance | ch11 |
Chapter 10
Chapter 11 |
| 4/14 | Experimentation in software engineering
Due: Topic for final paper Due: User guide for TSAFE | Experimentation |
Chapter 12
Experimental validation in software engineering by M. V. Zelkowitz and D. Wallace, Information and Software Technology (November, 1997) 734-744 |
| 4/19-21 | Cost modeling and metrics | metrics | |
| 4/26 | Defect and complexity models | ||
| 4/28 | |||
| 5/3 | Process improvement
Due: Final TSAFE project 3 Due: Effort for April through May 3 and Defect report | ch13 | Chapter 13 |
| 5/5-10 | Agile development | agile |
An introduction to agile methods
Chapter 14 |
| 5/12 | Review
Due: Final paper | Review of class material | |
| 5/16 8-10am | Final | Sample final exam |
| Practice problems |
| Class Project |
Group project: See description of TSafe system in ~mvz/tsafe/tsafe-project-spring-2005.doc.
Individual report: Topic due: April 14. Final report due May 12, 2005.
Investigate some project that failed due to software.
Explain the problem. What happeneded?
Why did it occur? What in the development process failed
to permit the failure of the software? How could this have been avoided?
If you had to pick liability, who was to blame? Has anything been done to avoid
this in the future?
If you are not sure of what project to discuss, see Dr. Zelkowitz first. If you pick something discussed in class (e.g., Ariane 5 failure, Therac 25), make sure you go well beyond what was discussed in class. Other possible choices: NASA Mars mission failures, IRS tax moderization system, Denver airport baggage handling.
| Class Resources |