Prev | Current Page 270 | Next

Peter Farrell-Vinay

"Manage Software Testing"

756
Personal use 0.144
Operators 0.062
System administrator 0.020
Support desk staff 0.018
FIGURE 7.13 Product use process model
Open new
document
Document
available
Enter text
Insert file
Insert
picture
Close
document
Save
document
Modify
picture
Document
modified
Change text
format
Spell-check
text
Close word
Open existing
document
Open word
112 Manage Software Testing
Some functions should be duplicated: mission- or safety-critical functions might exist in training and
operational modes. Each will thus need quite different approaches to testing.
Each function will have a number of parameters, each with a range of values. Some will dominate
processing more. Thus for example in Word, the ???Ctrl+n??? feature is used where n = { P(rint) | A(ll) |
S(ave) | F(ind) | . . . } . This will have a big effect on document structure. Conversely changing the typeface
of the ???Normal??? style involves little processing other than a lot of inheritance but has as many values as
Word has typeface files.
Testing (in Word) thus requires at least that you use:
??? Ctrl+n, where n = { O(pen) | P(rint) | A(ll) | S(ave) | F(ind) | N(ew document) . . . }
??? Normal style (typeface = { Ariel | Times New Roman | OpenSymbol | Bodoni Ornamental }).
Input variables such as ???Ctrl+n??? are key input variables. These differentiate one function or operation
from another. Additionally each interacts with another. The probability of a user hitting ???Ctrl+S(ave)???
is heavily dependent on their having hit ???Ctrl+O??? first.


Pages:
258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282