[Book Cover]

Software RX: Secrets of Engineering Quality Software, 1/e

Rodney C. Wilson, Cadence Design Systems, San Jose, California

Published October, 1996 by Prentice Hall PTR (ECS Professional)

Copyright 1997, 192 pp.
Paper
ISBN 0-13-472663-4


Sign up for future
mailings on this subject.

See other books about:
    Software Reliability-Computer Science


Summary

This collection of software engineering essays for software development and test engineering practitioners includes everything from source code assertions to engineering discipline and rigor. Examples are used throughout to give readers a better understanding and feel for many best practices that can be applied to the development, test and release management of software work products.

Features


Reviews the various components necessary for implementing good software engineering practices, including...

  • Cross-functional communication.
  • Response to problems.
  • Code quality.
  • Structural integrity.
Serves as a tutorial on how to engineer quality software.
Combines—in a single source—information on all aspects of developing efficient software.
Includes references to software engineering gurus philosophies and puts these views into context.
Discusses key topics, such as...
  • Attitude—teamwork/team development and key core competencies.
  • Reviews—how to measure incremental success; tips and traps associated with the review process.
  • Design Specs—key issues surrounding this difficult document.
  • OOP Best Practices—the increased need for methodology in object-oriented analysis, design and implementation.
  • Prototypes, Specs and Reviews—best practices for the development of gui and non-gui software applications.
  • Assertions in source code—how to increase testability and reliability using assertions in source code.
  • Acceptance Testing—a success metric to ensure that what is delivered meets the customer acceptance criteria.
  • Checklist for Best Practices—summary of key methods, tools and processes for successful software engineering and product development.


Table of Contents
    1. Attitude Makes the Difference.
    2. The Phased Approach.
    3. Code and Design Reviews (Structured Reviews).
    4. Design Specifications.
    5. Object-Oriented Programming and The Project Team.
    6. Prototypes, Specifications and Reviews.
    7. Assertions.
    8. Acceptance Test.
    9. Teamwork.
    10. Checklist for Best Practices.
    11. Best-in-Breed Survey Results.
    Appendix A: Beta Test and Customer Acceptance Test Checklist.
    Appendix B: Ambiguity Reviews.

[Help]

© Prentice-Hall, Inc. A Simon & Schuster Company
Comments To webmaster@prenhall.com