The Small Contractor and the Small ComputerStanford University, 1980 - 87 pages |
From inside the book
Results 1-3 of 19
Page 47
size test cases are used and the results are compared with manual tallies . System testing should be as concerned with error possibilites and exceptions as it is with ordinary cases . The end user should be involved in the system test .
size test cases are used and the results are compared with manual tallies . System testing should be as concerned with error possibilites and exceptions as it is with ordinary cases . The end user should be involved in the system test .
Page 51
The need to every number does not exist , but it is worth examining those those traced manually to see if the software performs the same functions . A topic worth examining separately that relates to actual program operation is error ...
The need to every number does not exist , but it is worth examining those those traced manually to see if the software performs the same functions . A topic worth examining separately that relates to actual program operation is error ...
Page 56
One reason commonly stated by interviewees for acquiring a computer is that it is better suited than a manual system to handle the growth in the volume of transactions that must be processed . This is especially true of repetitive ...
One reason commonly stated by interviewees for acquiring a computer is that it is better suited than a manual system to handle the growth in the volume of transactions that must be processed . This is especially true of repetitive ...
What people are saying - Write a review
We haven't found any reviews in the usual places.
Contents
THE SMALL COMPUTER ELEMENTARY CONCEPTS | 5 |
5 | 20 |
THE SMALL CONSTRUCTION CONTRACTING ENVIRONMENT | 33 |
Copyright | |
6 other sections not shown
Common terms and phrases
accounting advantages agreement alternative application arrangement attempt basis begin benefits better called changes Chapter common complete computer system consideration considered construction contract contractors cost data base deal decision defined depends determine devices difficult discussed disk documentation effects environment errors established examined example execution exist failure Figure Finally firm function future given hardware human implementation important in-house information system installation insure involves issues knowledge language lease look machine maintenance manual memory method nature necessary needs objectives Once operating operating system organization packages particular perform period personnel physical present problems programs purchase reason record reference relates requirements reviewed scheme service bureaus situation specific storage tape tasks term terminals testing things Three types understand usually vendor