mauney@ncsu.UUCP (Jon Mauney) (08/29/85)
%A William E. Howden %T The theory and practice of functional testing %J Software %V 2 %N 5 %P 6-17 %D SEP 1985 %X viewing programs as syntheses of requirements, design, and programming functions allows programmers to address a wide variety of errors-- even subtle and difficult-to-find missing code faults %A Nathan H. Petschenik %T Practical priorities in system testing %J Software %V 2 %N 5 %P 18-23 %D SEP 1985 %X During the system test phase, "thorough testing" can pass the limits of practicality. Test case selection, based on simple priority rules, is one solution to the problem of practicality vs. thoroughness %A John V. Guttag %A James J. Horning %A Jeanette M. Wing %T The Larch family of specification languages %J Software %V 2 %N 5 %P 24-36 %D SEP 1985 %X Larch specifications are two-tiered. Each one has a component written in an algebraic languages and another tailored to a programming language. %A Gideon Frieder %A Gabor T. Herman %A Craig Meyer %A Jayaram Udupa %T Large software problems for small computers: an example from medical imaging %J Software %V 2 %N 5 %P 37-47 %D SEP 1985 %X Small computers can be called on to perform large tasks. Doing so requires careful organization of input, output, auxiliary data structures, and memory. %A Michael C. Gemignani %T Who owns what software produces? %J Software %V 2 %N 5 %P 48-52 %D SEP 1985 %X When programs rather than humans create products, the issues of product ownership create thorny legal problems which the law has yet to address. %A Ruth E. Davis %T Logic programming and Prolog: a tutorial %J Software %V 2 %N 5 %P 53-62 %D SEP 1985 -- Jon Mauney, mcnc!ncsu!mauney "The door's not shut on my genius, but... North Carolina State University I just don't have the time."