User`s guide

6 IBM Rational DOORS Surrogate Module Synchronization
6-14
6
Scroll through the surrogate module. Notice that the objects with requirements (the
engine torque block and transmission subsystem) retain their links to the DOORS
formal module, as indicated by the red triangles.
7
Save the surrogate module.
Detailed Information About The Surrogate Module You Created
Notice the following information about the surrogate module that you created in
“Resynchronize to Include All Simulink Objects” on page 6-12:
• The name of the surrogate module is sf_car_doors, as you specified in the DOORS
synchronization settings dialog box.
• DOORS object headers are the names of the corresponding Simulink objects.
• The Block Type column identifies each object as a particular block type or a
subsystem.
• If you delete a previously synchronized object from your Simulink model and then
resynchronize, the Block Deleted column reads true. Otherwise, it reads false.
These objects are not deleted from the surrogate module. The DOORS software
retains these surrogate module objects so that the RMI can recover these links if you
later restore the model object.
• Each Simulink object has a unique ID in the surrogate module. For example, the ID
for the surrogate module object associated with the Mux block in the preceding figure
is 11.
• Before the complete synchronization, the surrogate module contained the
transmission subsystem, with an ID of 3. After the complete synchronization, the
transmission object retains its ID (3), but is listed farther down in the surrogate
module. This order reflects the model hierarchy. The transmission object in the
surrogate module retains the red arrow that indicates that it links to a DOORS
formal module object.