|
|
|
| R2012a Documentation → Simulink Verification and Validation | |
Learn more about Simulink Verification and Validation |
|
|
|
|
| R2012a Documentation → Simulink Verification and Validation | |
Learn more about Simulink Verification and Validation |
|
| Contents | Index |
If you plan to use DOORS software with the RMI, make sure to install additional files to establish communication between the DOORS application and the Simulink software. Follow the instructions in Configuring the Requirements Management Interface (RMI).
The setup script automatically copies all the required DOORS files to the installation folders. However, the script may fail because of file permissions in your DOORS installation. If the script fails, change the file permissions on the DOORS installation folders and rerun the script.
Alternative, you can install the additional files into the folders specified manually, as described in the following steps:
Copy the following files from matlabroot\toolbox\slvnv\reqmgt to the <doors_install_dir>\lib\dxl\addins folder.
addins.idx addins.hlp
If you have not modified the files, replace any existing versions of the files; otherwise, merge the contents of both files into a single file.
Copy the following files from matlabroot\toolbox\slvnv\reqmgt to the <doors_install_dir>\lib\dxl\addins\dmi folder.
dmi.hlp dmi.idx dmi.inc runsim.dxl selblk.dxl
Replace any existing versions of these files.
Open the <doors_install_dir>\lib\dxl\startup.dxl file. In the user-defined files section, add the following include statement:
#include <addins/dmi/dmi.inc>
If you upgrade from Version 7.1 to a later version of the DOORS software, perform these additional steps:
In your DOORS installation folder, navigate to the ...\lib\dxl\startupFiles subfolder.
In a text editor, open the copiedFromDoors7.dxl file.
Add // before this line to comment it out:
#include <addins/dmi/dmi.inc>
Save and close the file.
Start the DOORS and MATLAB software.
Run the setup script:
rmi setup
By default, the RMI does not insert navigation objects into requirements documents. If you want the RMI to insert navigation objects when you create a link from any model object to a requirement, you must configure the RMI to do this.
Enable the RMI to insert navigation objects into the DOORS database:
Open any model. For example, open the Simulink model:
sldemo_fuelsys
Select Tools > Requirements > Settings.
The Requirements Settings dialog box opens.
Click the Selection Linking tab.
Enable Modify destination for bi-directional linking.
When you select this option, every time you create a selection-based link from a model object to a requirement, the RMI inserts navigation objects at the designated location. Using this option requires write access to the requirements document.
Set the Model file reference option to none (on MATLAB path).
For this exercise, you save a copy of the demo model on the MATLAB path.
If you are adding requirements to a model that is not on the MATLAB path, select absolute, to indicate an absolute path to the model.
In the Apply this user tag to new links field, enter one or more user tags to apply to the links that you create.
For more information about user tags, see Understanding Requirements Filtering.
Click Close to close the Requirements Settings dialog box.
Keep the sldemo_fuelsys model open.
When you enable Modify destination for bi-directional linking, the RMI inserts a navigation object into both the model and the requirement. For this tutorial, you need a formal module that contains requirements. The examples in the tutorial show a demo model used for the purposes of illustration.
Rename the sldemo_fuelsys model and save it in a writable folder on the MATLAB path.
Start the DOORS software and open a formal module that contains requirements.
Select the requirement that you want to link to by left-clicking that requirement in the DOORS database.
In the sldemo_fuelsys model, select an object in the model.
This example creates a requirement from the fuel_rate_control subsystem.
Right-click the model object and select Requirements > Add link to current DOORS object.
The RMI creates the link for the fuel_rate_control subsystem.
It also inserts a new DOORS object into the formal module—a Simulink reference
object (
) that enables you to
navigate from the requirement to the model.
Close the model.
Note When you navigate to a DOORS requirement, the DOORS module opens in read only mode. If you want to modify the DOORS module, open the module using DOORS software. |
If you have several model objects that correspond to a requirement, you can link all the model objects to that requirement with one navigation object. This eliminates the need to insert multiple navigation objects for a single requirement. The model objects must be available in the same model diagram or Stateflow chart.
The workflow for linking multiple objects to a DOORS requirement is as follows:
Make sure that you have enabled Modify destination for bi-directional linking.
Select the DOORS requirement to link to.
Select the model objects that need to link to that requirement.
Right-click one of the objects and select Requirements > Add link to current DOORS object.
A single navigation object is inserted at the selected requirement.
Double-click the navigation object in DOORS to highlight the model objects that are linked to that requirement.
If the Requirements Management Interface (RMI) is configured
to modify destination for bi-directional linking, the RMI inserts
a navigation object into your requirements document. This object looks
like the icon for the Simulink software:
Note In IBMRationalDOORS requirements documents, clicking a navigation objects does not navigate back to your Simulink model; you must select MATLAB > Select object to find the model object that contains the requirements link. In Microsoft Office requirements documents, clicking a navigation object highlights the model object that contains the requirements link. |
To use an icon of your own choosing for the navigation object:
Select Tools > Requirements > Settings.
Select the Selection Linking tab.
Select Modify destination for bi-directional linking.
Selecting this option enables the Use custom bitmap for navigation controls in documents option.
Select Use custom bitmap for navigation controls in documents.
Click Browse to locate the file you want to use for the navigation objects.
For best results, use an icon file (.ico) or a small (16×16 or 32×32) bitmap image (.bmp) file for the navigation object. Other types of image files may give unpredictable results.
Select the desired file to use for navigation objects and click Open.
Close the Requirements Settings dialog box.
The next time you insert a navigation object into a requirements document, the RMI uses the file you selected.
In Inserting Navigation Objects into DOORS Requirements, you created a link between a DOORS requirement and the fuel_rate_control subsystem in the sldemo_fuelsys model. Navigate the links in both directions:
With the sldemo_fuelsys model closed, go to the DOORS requirement in the formal module.
Left-click the Simulink reference object that you inserted to select it.
Select MATLAB > Select item.
Your version of the sldemo_fuelsys model opens, with the fuel_rate_control subsystem highlighted.
Log in to the DOORS software.
Navigate from the model to the DOORS requirement. In the Model Editor, right-click the fuel_rate_control subsystem and select Requirements > 1. "<requirement name>" where <requirement name> is the name of the DOORS requirement that you created.
The DOORS formal module opens with the requirement object and its child objects highlighted in red.
IBM Rational DOORS software is a requirements management application that you use to capture, track, and manage requirements. The Requirements Management Interface (RMI) allows you to link objects in a Simulink model to requirements managed by external applications, including the DOORS software.
When you create a link from a model object to a DOORS requirement, the RMI stores information about the DOORS object in the model. This information allows you to navigate from the model to the associated requirement.
You can configure the RMI to insert a navigation object in the DOORS database. This object helps you to navigate from the DOORS requirement to the model object.
To insert navigation objects into the DOORS database, you must have write access to the DOORS database.
If you try to synchronize your Simulink model to a DOORS project, you may see the following errors:
-E- DXL: <Line:2> incorrectly concatenated tokens -E- DXL: <Line:2> undeclared variable (dmiRefreshModule) -I- DXL: all done with 2 errors and 0 warnings
If you see these errors, exit the DOORS software, rerun the rmi setup command at the MATLAB command prompt, and restart the DOORS software.
 | Navigation from Requirements Documents | Microsoft Office |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
