Test each PIM by executing use cases on each domain using a simulator and a special-purpose
code generator.
10. Test a set of PIMs by executing use cases on sets of domains and thus test the domain??“domain
bridges. Note that this may reveal further requirements which may affect system test readiness.
11. Define PIM to PSI mapping rules.
12. Incorporate PIM/PSI mapping rules into the PIM compiler.
13. Create a Platform-Specific Model (PSM) compliant with a component model such as CORBA,
using a supplied or purpose-built VEE plus optional manual modifications. It may interface with
existing systems using such protocols as IIOP, RMI, or SOAP, and also with such middleware as
CCM, J2EE, or MQSeries. This generates environment-specific code.
14. Compile the environment-specific code to produce an executable.
15. System-test the executable on the target. Note that any defects found will lie in either the original models
or the mapping rules. At this point the key functionality should not, theoretically require testing. Testing
can thus concentrate on non-functional requirements such as performance and usability.
The advantages of the xUML approach are that:
1. Developers can build precise models.
2. The models can be executed and tested early.
3. The process is well-defined.
4. The system allows for the reuse of components.
Note that:
1. The model shown above has eliminated much of the iterative interaction which surrounds the
creation and validation of PIMS.
Pages:
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178