Information Technology Reference
In-Depth Information
instructor name reduces the original estimate of the 3-year completion certifi cate
master fi le by about 57 Mbytes in hard disk storage. The offsetting increase in hard
disk storage due to the new certifi ed instructor master fi le is only 140 Kbytes. The
real downside is expected to be the additional processing time necessary to validate
instructor certifi cation codes on each student completion input and convert instructor
certifi cation codes to instructor names for all certifi cate printing.
13.3.5 Completion of the Test Strategy
Your last testing step in the Analysis stage is to begin the “P” (Premeditation) in
the SPRAE testing method by completing your test strategy. Based on the bathtub
model of test planning, you know that your test plans will start with details from the
development team's Design stage. Figure 13.2 shows a likely test strategy based on
the ten use cases and draft architecture design.
Software testing techniques
Static tests White box Black box Workload
Software platform by
layer of operation
Application under
development
New (4)
Connectivity
(private, public)
New (3)
Data resources
(disk space, data mgmt)
New (2)
Lock and key
Security (local and remote)
Operating system
(cycles and memory)
New (1)
Preliminary
investigation +
Analysis
+ Design
Preliminary
construction
Final
construction
Ship or
Install
Post
implementation
PDM
Figure 13.2
Testing strategy chessboard for the DSA certificate processing system
This strategy shows that the fi rst concern will be the speed and capacity of the
workstation hardware as described in the draft architecture design.
The second concern will be the functionality of the database management system
as described in the draft architecture design. Of particular concern is the architecture
support of use case-04 for printing student completion records on the approved
completion certifi cate form. These concerns will drive the choice of the database
management system before any detailed design work can be started by the development
team. All other use cases have quite a bit of latitude in their actual implementation.
The third concern is the speed of architecture connectivity that will adequately
support use cases -07 and -08.
The fourth and fi nal concern is the set of use cases -03 to -06 that defi ne the
software application primary functionality to be developed. This row of the test
strategy will follow familiar testing patterns for new applications under test.
Search WWH ::
Custom Search