文档介绍：Page i Tuesday, March 20, 2007 6:04 PM
WHAT EVERY
ENGINEER SHOULD
KNOW ABOUT
SOFTWARE
ENGINEERING
Page ii Tuesday, March 20, 2007 6:04 PM
WHAT EVERY ENGINEER SHOULD KNOW
A Series
Series Editor*
Phillip A. Laplante
Pennsylvania State University
1. What Every Engineer Should Know About Patents,
William G. Konold, Bruce Tittel, Donald F. Frei,
and David S. Stallard
2. What Every Engineer Should Know About Product
Liability, James F. Thorpe and William H. Middendorf
3. What Every Engineer Should Know About
puters: Hardware/Software Design,
A Step-by-Step Example, William S. t
and Carl F. Evert, Jr.
4. What Every Engineer Should Know About Economic
Decision Analysis, Dean S. Shupe
5. What Every Engineer Should Know About Human
Resources Management, Desmond D. Martin
and Richard L. Shell
6. What Every Engineer Should Know About Manufacturing
Cost Estimating, Eric M. Malstrom
7. What Every Engineer Should Know About Inventing,
William H. Middendorf
8. What Every Engineer Should Know About Technology
Transfer and Innovation, Louis N. Mogavero
and Robert S. Shane
9. What Every Engineer Should Know About Project
Management, Arnold M. Ruskin and W. Eugene Estes
*Founding Series Editor: William H. Middendorf
Page iii Tuesday, March 20, 2007 6:04 PM
10. What Every Engineer Should Know puter-
Aided Design puter-Aided Manufacturing:
The CAD/CAM Revolution, John K. Krouse
11. What Every Engineer Should Know About Robots,
Maurice I. Zeldman
12. What Every Engineer Should Know About
puter Systems Design and Debugging,
Bill Wray and Bill Crawford
13. What Every Engineer Should Know About Engineering
Information Resources, Margaret T. Schenk
and James K. Webster
14. What Every Engineer Should Know About
puter Program Design, Keith R. Wehmeyer
15. What Every Engineer Should Know puter
Modeling and Simulation, Don M. Ingels
16. What Every