Need a testing plan that includes unit integration and system testing as Jesse requested. Also, need a reminder about careful documentation.
What will be an ideal response?
A testing plan must address unit, integration, and system testing. The first step is unit testing, which involves a test of each data entry program or function using both valid and invalid data, as well as a test of each report generated by the system.
The next step is integration testing. Programs or functions that create or modify files used by other programs must be linked and tested with those other programs. In a database environment, this would involve testing all relationships and multi-table queries. Finally, all programs must be tested together in a system test, along with all system utility functions, including backup and recovery procedures.
There is no standard answer for the documentation memo, but students should include references to the various types of documentation discussed on pages 528–532, including program documentation, system documentation, operations documentation, and user documentation.
You might also like to view...
Write a line of code that will insert the number 2.56 just before the last element of a vector of floating point values called aVector.
What will be an ideal response?
Figure 5-21 is an example that’s not well aligned. Explain what you would do to improve the alignment. It may be helpful to create a photocopy of the example and draw on it.
Expression Builder can be opened by selecting Builder located in the Query:
A) Results group. B) Type group. C) Show/Hide group. D) Setup group.
When used with integer conversion specifiers, the letters h and l (“el”) are called __________.
a) height modifiers b) length modifiers c) complements d) adjustors