Page 305 -
P. 305

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 Engi-
                          neering and Software Engineering (CMMI-SE/SW, V1.1: Continuous Representation). Carnegie
                          Mellon University Software Engineering Institute, 2001.
                          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.

                          Chapter 5. Reviews

                          Beck, K. Extreme Programming Explained: Embrace Change. Addison Wesley, 2000.
                          Gilb, T., D. Graham, et al. Software Inspection. Addison Wesley, 1993.

                          Software Engineering Institute. “Software Inspections.” Software Technology Roadmap. J. Fore-
                          man. Carnegie Mellon University Software Engineering Institute, 2004.

                          Standish Group. CHAOS: A Recipe for Success, The Standish Group International, 1999.
                          Wiegers, K. E. Peer Reviews in Software: A Practical Guide. Addison Wesley, 2002.

                          Williams, L., R. R. Kessler, et al. “Strengthening the Case for Pair-Programming.” IEEE
                          Software (July/August 2000).


                          Chapter 6. Software Requirements
                          Christel, M., and K. Kang. ”Issues in Requirements Elicitation,” Software Engineering
                          Institute, Carnegie Mellon University.

                          Gottesdiener, E. “Top Ten Ways Project Teams Misuse Use Case—and How to Correct

                          Them.” The Rational Edge (July 2002).
                          Kulak, D,. and E. Guiney. Use Cases: Requirements in Context. Addison Wesley, 2000.
                          Rumbaugh, J. “Getting Started: Using Use Cases to Capture Requirements.” Journal of
                          Object-Oriented Programming 7(5) (1994).
                          Thayer, R. H., M. Dorfman, et al. Software Requirements Engineering. Los Alamitos, Calif., IEEE
                          Computer Society Press, 1994.
                          Wiegers, K. E., Software Requirements, 2nd Edition. Microsoft Press, 2003.






                                                                                           BIBLIOGRAPHY  297
   300   301   302   303   304   305   306   307   308   309   310