Skip to main content

Advertisement

Log in

Testing network management software

  • Papers
  • Published:
Journal of Network and Systems Management Aims and scope Submit manuscript

Abstract

A fourth wave of computer-based network management systems is here. Experienced network managers worry about the reliability of software. This discussion provides ways of testing software to improve software and system reliability, and it proposes a “reliability footprint” in-process metric to monitor the effectiveness of a test program. Systematic ways of moving from debugging to assuring reliable network management systems are emphasized.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Rent this article via DeepDyve

Similar content being viewed by others

References

  1. J. Baumert, New SEI maturity model targets key practices,IEEE Software, pp. 78–79, Nov. 1991.

  2. L. Bernstein and J. J. Appel, Requirements or prototyping? Yes!, AT&T Bell Laboratories, USA Bell Communications Research, Inc., USA.

  3. B. W. Boehm, A spiral model of software development and enhancement,COMPUTER, pp. 61–72, May 1988.

  4. H. S. Burns and R. A. Halliburton, Tackling productivity and quality through customer involvement and software technology, IEEE Global Telecommunications Conference, November 27–30, 1989.

  5. P. A. Currit, M. Dyer, and H. D. Mills, Certifying the reliability of software,IEEE Transactions on Software Engineering, Vol. SE-12, No. 1, pp. 3–11, Jan. 1986.

    Google Scholar 

  6. W. S. Humphrey, Characterizing the software process: A maturity framework. In T. DeMarco and T. Lister (eds.),Software State-of-the-Art: Selected Papers, Dorset House Publishing, New York, pp. 62–74, 1990.

    Google Scholar 

  7. W. S. Humphrey, T. R. Snyder, and R. R. Willis, Software process improvement at Hughes Aircraft,IEEE Software, pp. 11–23, July 1991.

  8. S. Kusumoto, K. Matsumoto, T. Kikuno, and K. Torii, Approaches to improving effectiveness of review activities in technical review process, International Software Quality Exchange '92 Conference Proceedings, Juran Institute, Inc., 11 River Road, Wilton, CT 06897, pp. 7B1–7B16, 1992.

  9. Y. Levendel, Improving quality with a manufacturing process,IEEE Software, pp. 13–25, March 1991.

  10. Luqi and W. Royce, Status report: Computer-aided prototyping,IEEE Software, pp. 77–81, Nov. 1992.

  11. M. L. McFarlane and A. Sutton, Structured, automatic testing—A hard slog, Cadence Design Systems, 2455 Augustine Drive, Santa Clara, CA 95054, Dec. 22, 1989.

    Google Scholar 

  12. M. S. Phadke,Quality Engineering Using Robust Design, Prentice Hall, Englewood Cliffs, NJ, pp. 5–6, 1989.

    Google Scholar 

  13. S. A. Sherer, A cost effective approach to testing,IEEE Software, pp. 34–40, March 1991.

  14. M. E. Staknis, Software quality assurance through prototyping and automated testing,Information and Software Technology, Vol. 32, No. 1, pp. 26–33, Jan./Feb. 1990.

    Google Scholar 

  15. A. Topper and P. Jorgensen, More than one way to measure process maturity,IEEE Software, pp. 9–10, Nov. 1991.

  16. T. Yoshida, Attaining higher quality in software development—Evaluation in practice,Fujitsu Science Technical Journal, Vol. 21, pp. 305–316, July 1985.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Bernstein, L., Yuhas, C.M. Testing network management software. J Netw Syst Manage 1, 5–15 (1993). https://doi.org/10.1007/BF01026825

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF01026825

Key words

Navigation