Questions:
Write a test plan for the ATM system as a whole and the Login, Withdrawal, and Transfer modules, using the included specifications and use cases. You do not have to be detailed in the early sections, but both section 3 and section 4 should be as detailed as possible, i.e. use samples of the functional test vectors.
For Submission Test Plan Format (electronic copy):
1. General Information
1.1. Summary
Summarize the functions of the software and tests to be performed
1.2. Test Objectives
State the objectives to be accomplished by testing.
2. Plan
2.1. Software Description
Provide a chart and briefly describe the inputs, outputs, and functions of the software being tested as a frame of reference for the test descriptions.
2.2. Milestones
List the milestone events for the testing, from the plan itself i.e. the system checkpoints.
2.3. Testing (system checkpoint)
Identify the participating organizations and the system checkpoint where software will be tested
2.3.1. Requirements
State the resource requirements including:
2.3.1.1. Equipment
Show the expected period of use, types, and quantities of the equipment needed.
2.3.1.2. Software
List other software that will be needed to support the testing that is not part of the software to be tested.
2.3.2. Tests to be Conducted
Reference specific tests to be conducted at this checkpoint.
2.4. Testing (system checkpoint)
Repeat 2.3 as necessary for all checkpoints.
3. Specifications and evaluation
3.1. Specifications
3.1.1. Business Functions
List the business functional requirements established by earlier documents.
3.1.2. Structural Functions
List the detailed structural functions to be exercised during the overall test.
3.1.3. Test/Function Relationships
List the tests to be performed on the software and relate them to the functions in 3.1.2.
3.1.4. Test Progression
Describe the manner in which progression is made from one test to another so that the entire test cycle is completed.
3.2. Methods and Constraints
3.2.1. Methodology
Describe the general method or strategy of the testing.
3.2.2. Extent
Indicate the extent of the testing, such as total or partial. Include any rationale for partial testing.
3.2.3. Data Recording
Discuss the method to be used for recording the test result and other information during testing.
3.2.4. Constraints
Indicate anticipated limitations on the test due to test conditions, such as interfaces, equipment, personnel, databases.
3.3. Evaluation
3.3.1. Criteria
Describe the rules to be used to evaluate test results, such as range of data values used, combinations of input values used, maximum number of allowable interrupts or halts.
3.3.2. Data Reduction
Describe the techniques to be used for manipulating the test data into a form suitable for evaluation, such as manual or automated methods, to allow for comparison of the results that should be produced to those that are produced.
4. Test Descriptions
4.1. Test (identify)
Describe the test to be performed (these are the functional tests you need to do and the condition under which it will operate).
4.1.1. Control
Describe the test control such as manual, semi-automatic, automatic insertion of inputs, sequencing of operations, and recording of results.
4.1.2. Inputs
Describe the input data and input commands used the test.
4.1.3. Outputs
Describe the output data expected as a result of the test and any intermediate messages that may be produced.
4.1.4. Procedures
Specify the step-by-step procedures to accomplish the test. Include test setup, initialization, steps and termination.
4.2. Test (identify)