Bergland, G.D., "A Guided Tour of Program Methodologies," IEEE Computer, October 1981.
Discusses four software design methods: structured analysis, functional decomposition, data flow design, and data structure design.
Bersoff, Edward H.; Henderson, Vilas D.; and Siegel, Stanley G., Configuration Management: An Investment in Product Integrity. Englewood Cliffs, N.J.: Prentice-Hall, 1980.
Discusses the principles of configuration control, auditing, and status accounting in software development projects.
Boar, Bernard H., Application Prototyping: A Requirements Definition Strategy for the 80s. New York: John Wiley & Sons, 1984.
Discusses software prototyping as a method for defining the user requirements for a system.
Boehm, Barry W., "A Spiral Model of Software Development and Enhancement," Computer, May 1988.
Discusses the risk driven spiral model for software development, its focus on early prototyping and simulation, current usage of the model, and advantages of this process model over other software models available.
Boehm, Barry W., "Software Engineering," IEEE Transactions on Computers, December 1976.
Provides a survey of software engineering technology in several of the life cycle phases and discusses software trends.
Boehm, Barry W., Software Engineering Economics. Englewood Cliffs, N.J.: Prentice-Hall, 1981.
Gives an in-depth explanation of the COnstructive COst MOdel (COCOMO) for estimating resources, staffing levels and costs of a software development project. Discusses the impact of numerous cost drivers associated with a project such as: product attributes, computer attributes, and personnel attributes.
Boehm, Barry W. and Papaccio, Philip N., "Understanding and Controlling Software Costs," IEEE Transactions on Software Engineering, October 1988.
Discusses key issues in estimating software development costs.
Booch, Grady. "Object-Oriented Development," IEEE Transactions on Software Engineering, February 1988.
Discusses key issues in object-oriented development.
Brooks, Frederick P., "No Silver Bullet," IEEE Computer, April 1987.
Discusses the nature of software development projects and why there are no easy ways (silver bullets) for making large improvements in productivity, reliability and simplicity.
Brooks, Frederick P., The Mythical Man-Month: Essays on Software Engineering. Reading, Massachusetts: Addison-Wesley Publishing Company, 1975.
Discusses the difficulties of managing large software projects and other software management issues.
Buckley, Fletcher J., Implementing Software Engineering Practices. New York: John Wiley & Sons, 1989.
Provides guidance and examples for establishing software engineering standards and practices within an organization. Discusses current IEEE and DoD standards.
Cortese, Amy, "Estimating Tools reap 85% Accuracy, Some Say," Computerworld, November 14, 1988.
Brief discussion of current state of software costs estimation tools.
DeMarco, Tom, Structured Analysis and System Specification. New York: Yourdon, 1978.
Provides details of structured software design techniques.
DeMillo, Richard A.; McCracken, W. Michael; Martin, R.J.; and Passafiume, John
F., Software Testing and Evaluation. Menlo Park, California: The Benjamin/Cummings Publishing Company, 1987.
Provides a discussion of software testing techniques and an overview of current defense practices gathered from interviews and surveys with military and industrial personnel. Also includes data sheets on numerous testing tools.
Deutsch, Michael S., Software Verification and Validation: Realistic Project Approaches. Englewood Cliffs, N.J.: Prentice-Hall, 1982.
Discusses software testing methodologies and the use of verification and validation techniques throughout the entire software life cycle.
Fairley, Richard E., Software Engineering Concepts. New York: McGraw-Hill Book Company, 1985.
Provides a comprehensive description of the entire software development life cycle from concept definition through maintenance. Also includes many good examples of software engineering concepts. Very good section about planning the software development effort.
"IEEE Standard for Software Unit Testing," ANSI/IEEE Std. 1008-1987, December 29, 1986.
Discusses planning for, implementing and measuring software unit testing.
IEEE Standard for Software Verification and Validation Plans, Std. 1012-1986, November 14, 1986.
Provides a complete guide for the development of a standard verification and validation plan throughout the life cycle of a software development project.
Kemerer, Chris F., "An Empirical Validation of Software Cost Estimation Models," Communications of the ACM, May 1987
Provides an evaluation of four popular software cost estimation models: SLIM, COCOMO, Function Points and ESTIMACS.
Kirk, Frank G., Total System Development for Information Systems. New York: John Wiley & Sons, 1973.
Discusses a disciplined method for developing a software system. Includes an activities network which is used as the framework for describing the total system development effort.
"Managing Software Development: Solving the Productivity Puzzle," Course Moderator's Guide, John Wiley & Sons, Inc., 1985.
Provides good overview of key points in the software development process with emphasis on the management of a software project.
Meyer, Bertrand, Object-Oriented Software Construction, Englewood Cliffs, NJ: Prentice Hall, 1988.
Describes how object-oriented software is developed.
Musa, John D.; Iannino, Anthony; and Okumoto, Kazuhira, Software Reliability: Measurement, Prediction, Application. New York: McGraw-Hill, 1987.
Describes the basics of software reliability measurement, provides the procedures and formulas for applying the measurements, and also details the theoretical background of software reliability.
Myers, Glenford J., The Art of Software Testing. New York: John Wiley & Sons, 1979.
Describes the various types of software testing and the tools and techniques commonly used. Also provides discussions of test case design, software debugging and program inspections, walkthroughs, and reviews.
Myers, Glenford J., Software Reliability: Principles & Practices. New York: John Wiley & Sons, 1976.
Describes what needs to be done during each of the various stages of software development to produce reliable software.
Perry, William E., A Structured Approach to Systems Testing, Second Edition. Wellesley, Massachusetts: QED Information Sciences, 1988.
Comprehensive discussion of software testing throughout the entire life cycle. Includes test, documentation, review and audit checklists and examples.
Peters, Lawrence J., Software Design: Methods & Technologies. New York: Yourdon Press, 1981.
Discusses the role of and issues of software design. Includes descriptions of tools and techniques used in software design.
Quirk, W. J., ed., Verification and Validation of Real-time Software. New York: Springer-Verlag, 1985.
Provides an array of articles concerning software development methods and standards.
Smith, David J. and Wood, Kenneth B., Engineering Quality Software: A Review of Current Practices, Standards and Guidelines including New Methods and Development Tools. London: Elsevier Applied Science, 1987.
Discusses software standards and guidelines in several different countries. Provides checklists for software design, design reviews, programming standards, testing, change control, documentation, and project management.
Vincent, James; Waters, Albert; and Sinclair, John, Software Quality Assurance: Volume I, Practice and Implementation. Englewood Cliffs, N.J.: Prentice-Hall, 1988.
Discusses the factors of software quality, software metrics and software audits. Provides numerous checklists, forms, and algorithms for assessing and measuring the appropriate factors.
Wallace, Dolores R. and Fujii, Roger U., "Software Verification and Validation: An Overview," IEEE Software, May 1989.
Discusses methods and standards which support the use of verification and validation throughout the life cycle of a software project.
Wood, Bill; Pethia, Richard; Gold, Lauren Roberts; and Firth, Robert, "A Guide to the Assessment of Software Development Methods," Technical Report CMU/SEI-88-TR-8 ESD-TR-88-009, Carnegie-Mellon University Software Engineering Institute, April 1988.
Discusses software methods and ways to determine if the methods satisfy a software development organization's needs.