Objectives:
Required text:
Pressman, Roger S. 1997. Software Engineering: a Practitioner's Approach, 4th edition. New York, New York: The McGraw-Hill Companies, Incorporated.
Recommended texts:
Behforooz, Ali, and Frederick
J. Hudson. 1996. Software Engineering
Fundamentals. New York, New York: Oxford University Press.
Pfleeger, Shari Lawrence.
1998. Software Engineering: Theory and
Practice. Upper Saddle River, New Jersey: Prentice-Hall,
Incorporated.
Recommended text references:
Humphrey,
Watts S. 1995. A Discipline for Software Engineering.
Reading, Massachusetts: Addison-Wesley Publishing Company.
Peters, James
F., and Witold Pedrycz. 2000. Software Engineering: An
Engineering Approach New York, New York: John Wiley & Sons,
Incorporated.
Sommerville,
Ian. 1996. Software Engineering, 5th edition.
Wokingham, England: Addison-Wesley Publishing Company.
Steward, Donald V. 1987. Software Engineering with Systems
Analysis and Design. Monterey, California: Brooks/Cole Publishing
Company.
Recommended literature:
Cusumano, Michael
A. 1991. Japan's Software Factories. Oxford,
United Kingdom: Oxford University Press, Incorporated.
Weinberg, Gerald M. 1971.
The Psychology of Computer Programming.
New York, New York: Van Nostrand Reinhold.
Weinberg, Gerald M. 1992.
Quality Software Management: Volume
1 Systems Thinking. New York, New York: Dorset House Publishing.
Wiener, Lauren
Ruth. 1993. Digital Woes: Why We Should Not
Depend on Software. Reading, Massachusetts: Addison-Wesley
Publishing Company.
Yourdon, Edward. 1992.
Decline & Fall of the American
Programmer. Englewood Cliffs, New Jersey: Prentice-Hall,
Incorporated.
Topic | Pressman | Behforooz & Hudson | Pfleeger |
Overview | 1-2 | 1.0-1.2, 2 | 1 |
Managing Software Engineering | |||
Project management concepts | 3 | 3 | |
Metrics | 4 | 14 | 11 |
Project planning | 5 | 1.3, 14 | 3 |
Risk analysis | 6 | 16 | 3.4 |
Scheduling and tracking | 7 | 1.4-1.5 | 3.1 |
SQA | 8 | 18 | 4.2 |
Configuration management | 9 | 6.2 | 8.1 |
Doing software engineering | |||
Overview | 10, 11, 19 | ||
Analysis | 12, 20 | 4, 8 | 4 |
Design | 13, 14, 21 | 7, 8 | 5 |
Testing | 16, 17, 22 | 10, 11, 12 | 7 |
Metrics | 18, 23 | 14 | 11 |
Advanced topics, as time permits | |||
Cleanroom | 25 | 12.4 | |
Reuse | 26 | 11.4 |
Administration:
Midterm examination (February 24) 30%
Final examination (April 20, set by University Calendar Committee) 30%
Class project 30% Specification
details
Homework problems 10%
The class project will be done in teams of 4 (or 5 to accommodate class size not divisible by 4). Choice of team members will be yours. I plan to hand out initial project specifications January 13; the projects will be due April 13 (with interim deliverables).
Examinations and homework problems will be done individually, in accordance with the College of Engineering honor code (this class is under the jurisdiction of that code).
Availability of help:
Office hour in the Science Building microcomputer laboratory
5-6pm Tuesdays and Thursdays.
Day phone (313)-592-2374
Campus Email address williame@umdsun2.umd.umich.edu
Ford Email address ewillia4@ford.com
Pertinent Web Sites:
Dave Hinkle, one of our own alumni, has graciously consented to have
his testimonial concerning the value of documentation placed on this web
site (click here).
The Association of Computing Machinery [ACM] has a special interest
group, SIGSOFT devoted to software
engineering.
The Institute of Electrical and Electronics Engineers, Incorporated
[IEEE] sponsors many publications and
conferences devoted to software engineering.
The Software Engineering Institute at
Carnegie Mellon University maintains an excellent web site.