Information Technology Reference
In-Depth Information
capability will be started after the historical data entry screens are fi nished. When
all three Final construction tasks have been completed, an additional week of regre-
ssion testing will be scheduled to ensure that the three newly completed tasks have
not adversely affected any of the previously tested code.
Here is a recap of the additional use cases that impact the Final construction use
case suite, the test plan, and the test cases.
Use case-11: DSA Certifi cate Records—out-of-state Reporting
Use case-12: DSA Completion Records—historical Completions
Use case-13: DSA Completion Records—production Cutover
One fi nal suggestion is made by the testing team. Because the development and
testing of the current certifi cate record processing fl ow will be curtailed in prepara-
tion for the redesign, the Final construction stage can begin a week early, the last
planned week of the Preliminary construction stage. The revised development and
testing schedule are refl ected in the Final construction test plan.
13.6 FINAL CONSTRUCTION STAGE
13.6.1 StaticTesting
The static testing of Final construction documentation follows the same pattern we
saw in Design and Preliminary construction. The fi rst documents tested will be the
new use cases and process fl ow in the architecture design. Then the programming
specifi cations derived from the requirements are static tested. Then the program-
ming code written from the specifi cations are static tested. The new static testing for
this stage will be the DSA end user documentation: User Guide and Administrator
Guide. Because CPI will install the new system, there will be no formal Installation
Guide for DSA.
The pivotal document for this stage will be the architecture design, which con-
tains the redesign of the basic certifi cate record processing fl ow. The tester's job is
focused on asking hard questions like, “How do you know that this new design will
be more stable and works better than the original design?” If the developer does his
homework, he can give the tester very concrete reasons why the new design is better.
If the developer has not done his homework, then he will most likely become de-
fensive with answers like, “because I'm the design expert.” Specifi c defi ciencies are
discovered in the old design and, as a tester, you know it will take specifi c deliberate
action to correct these defi ciencies.
13.6.2 FunctionalTesting
As soon as the new and revised documentation is declared correct by static testing,
the Final construction stage programming, code debugging, and code testing be-
gin. The fi rst code to be functionally tested in this stage is the historical data entry
screen. Many parts of the completion data entry screen test script should be reusable
Search WWH ::
Custom Search