Prev | Current Page 224 | Next

Peter Farrell-Vinay

"Manage Software Testing"

The user??™s objectives (
?????¦I??™m trying to write a news story??¦???
)
3. Identify the safety-testing requirements
(see section B.10 in Appendix B) in terms of:
a. The user population
b. The safe and unsafe states, changes between them, and ability to recover from a failure
c. Hazards
d. Safety-related functions
e. Safety performance
f. Human interface
g. Testing requirements
4.
Identify the security-testing requirements
(see section B.11 in Appendix B) in terms of:
a. The user population
b. The secure and insecure states and interfaces
c. The 3rd-party security subsystems to be used
d. The threats and defenses
5.
Identify the performance-testing requirements
in terms of section B.14 in Appendix B. Also see
Chapter 16
for more on this.
6.
Identify the operational profile
as discussed in section 7.7.
7.
Identify feature interactions.
As the system is used (particularly operationally) subtle interactions
may emerge (for example, the use of tables in footers in Word 6.1, the instability in Word v.x
when inserting cross-references, etc.). To identify all the feature interactions you will need to:
a. Identify the features in each operational profile
b. Identify all the scenarios the users will adopt
c. Identify which feature interactions are
not
covered by a scenario (see section 15.10.10)
d. Identify test objectives to cover the missing interactions
e. Create a matrix of them (see Figure 15.


Pages:
212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236