By this point it should be possible to identify most of the risks the project faces.
4. Create dynamic models using state charts, state tables, and interactions by:
??“ Identifying all the class life-cycles.
??“ Identifying the timing constraints.
??“ Summarizing complex interactions using class collaboration diagrams.
The ability to submit a fragment of a PIM for validation at this stage is a key factor in using this
approach. By identifying problems at this point a test team can obtain great leverage on the system??™s
eventual quality. It will have the effect of:
??“ Greatly speeding system testing.
??“ Validating requirements early.
??“ Identifying performance requirements and constraints.
5. Define action behavior using an
Action Specification Language
(ASL).
6. Identify domain??“domain interfaces (domain contract). There is a need to check the interfaces
between domains: since a bridge provides a mapping between two (or more) domains, the scope
of the ASL used to describe it is no longer that of a single domain, and may thus be ambiguous.
7. Create
Processor-Independent Module/Platform-Specific Implementation
(PIM/PSI) tests using the
use cases and sequence diagrams and the ASL (to define external stimuli). This involves:
??“ Identifying use cases specific to a domain to act as baselines.
??“ Identifying bridges to act as the baselines for multiple domain testing so as to be able to answer
the question
???have we tested each domain interface????
??“ Creating test scripts capable of exercising each domain and each domain??“domain interface.
Pages:
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176