Chapter 2. Software Project Planning


Brooks, F. P. The Mythical Man-Month: Essays on Software Engineering. Addison Wesley, 1995.

Christensen, D.S. "Value Cost Management Report to Evaluate the Contractor's Estimate at Completion." Acquisition Review Quarterly (Summer 1999).

Fleming, Q. W., and J. M. Koppelman. "Earned Value Project Management: A Powerful Tool for Software Projects." STSC CrossTalk: The Journal of Defense Software Engineering (July 1998).

Humphrey, W. S. Managing the Software Process. Addison Wesley, 1989.

Leffingwell, D., and D. Widrig. Managing Software Requirements: A Unified Approach.Addison Wesley, 2000.

Leffingwell, D., and D. Widrig. Managing Software Requirements: A Use Case Approach. Addison Wesley, 2003.

Parkinson, C. N. Parkinson's Law: The Pursuit of Progress. John Murray, 1958.

Paulk, M. C., B Curtis, M.B. Chrissis, and C.V. Weber. Capability Maturity Model Registered Trademark Integration (CMMI Superscript SM ), Version 1.1: CMMI Superscript SM for Systems Engineering and Software Engineering (CMMI-SE/SW, V1.1: Continuous Representation). Carnegie Mellon University Software Engineering Institute, 2001.

Paulk, M. C. The Capability Maturity Model: Guidelines for Improving the Software Process. Addison Wesley, 1995.

Potter, N. S., and M. E. Sakry. Making Process Improvement Work: A Concise Action Guide for Software Managers and Practitioners. Addison Wesley, 2002.

Thayer, R. H. Software Engineering Project Management. IEEE Computer Society, 1997.

Wiegers, K. "Saving for a Rainy Day." The Rational Edge (April 2002).

Wiegers, K. E. Software Requirements. Microsoft Press, 1999.

Wiegers, K. E. Peer Reviews in Software: A Practical Guide. Addison Wesley, 2002.



Applied Software Project Management
Applied Software Project Management
ISBN: 0596009488
EAN: 2147483647
Year: 2003
Pages: 122

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