Notes

  1. Construx's ladder differentiates between "analytical" and "inspectional" reading levels. For details on this distinction, see Steve McConnell, "How to Read a Technical Article," IEEE Software, Nov./Dec. 1998, pp. 128f.

  1. Fishman, Charles, "They Write the Right Stuff," Fast Company, December 1996.

  1. McConnell, Steve, Software Project Survival Guide, Redmond, WA: Microsoft Press, 1998.

  1. See www.construx.com/profession.

  1. Davis, Alan M., 201 Principles of Software Development, New York: McGraw-Hill, 1995.

  1. Sommerville, Ian, Software Engineering, 6th Ed., Boston, MA: Addison-Wesley, 2000.

  1. Pressman, Roger S., Software Engineering: A Practitioner's Approach, 5th Ed., New York: McGraw-Hill, 2001.

  1. Brooks, Frederick P., Jr., "No Silver Bullets Essence and Accidents of Software Engineering," Computer, April 1987, pp. 10 19.

  1. DeMarco, Tom, and Timothy Lister, "Programmer Performance and the Effects of the Workplace," Proceedings of the 8th International Conference on Software Engineering, August 1985, pp. 268 272.

  1. Manager's Handbook for Software Development, Revision 1, Document number SEL-84-101, Greenbelt, MD: Goddard Space Flight Center, NASA, 1990.

  1. McConnell, Steve, Rapid Development. Redmond, WA: Microsoft Press, 1996.

  1. Gibbs, W. Wayt, "Software's Chronic Crisis," Scientific American, September 1994, pp. 86 95.

  1. Recommended Approach to Software Development, Revision 3, Document number SEL-81-305, Greenbelt, MD: Goddard Space Flight Center, NASA, 1992.

  1. See www.computer.org/certification.

  1. See www.pmi.org.



Professional Software Development(c) Shorter Schedules, Higher Quality Products, More Successful Projects, [... ]reers
Professional Software Development(c) Shorter Schedules, Higher Quality Products, More Successful Projects, [... ]reers
ISBN: N/A
EAN: N/A
Year: 2005
Pages: 164

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net