]
8.3.5 Solution Criteria
[Describes:
??? How we will know that the solution resolves the problem (
what degree of leverage would it afford us
)
??? Characteristics
132
Manage Software Testing
??? Priorities
??? Minimal acceptability criteria (
to
, customers, and users),
??? What happens if we do nothing.]
8.3.6 Recommendations
[Describes:
??? The preferred choices
??? The justification
??? The costs
??? The implications
??? The alternatives considered
??? The reasons why they were rejected.]
8.3.7 Metrics
[Describes:
??? Solution process metrics
??? Solution outcome metrics.]
8.3.8 Strategy Document Checklist
1. What are the problems, deficiencies, and opportunities being addressed? Are these symptoms of
more basic concerns?
2. Is the context (i.e., problem, scenario, environment) consistent with ??™s overall
strategy?
3. Have assumptions and constraints been identified? Are they reasonable? How would changes in
them affect the results?
4. Have all reasonable alternatives been considered?
5. Were multiple measures of effectiveness used? Do they relate to the performance thresholds and
objectives established for the solution? To overall improvements in features?
6. Have all relevant costs been shown?
7. Are the models clearly identified? Are they appropriate to the system being evaluated? Are the
input parameters identified? Can the results be replicated?
8. Has the cost and operational effectiveness been validated through engineering analyses or tests?
9.
Pages:
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309