The Requirements Management Interface (RMI) stores externally stored requirements links in a file whose name is based on the model file. Because of this, before you create requirements links to be stored in an external file, you must save the model with a value file name.
You add, modify, and delete requirements links in external storage the same way you do when the requirements links are stored in the model file. The main difference is when you change externally stored links, the model file does not change. The asterisk in the title bar of the model window that indicates a model has unsaved changes does not appear when you change requirements links. However, when you close the model, the RMI asks if you want to save the requirements links modifications.
There are several ways to save requirements links that are stored in an external file, as listed in the following table.
|Analysis > Requirements Traceability > Save Links As||Save the requirements links in an external file using a file name that you specify. The model itself is not saved.|
|Analysis > Requirements Traceability > Save Links||Save the requirements links in an external file using the default file name, model_name.req, or to the previously specified file. The model itself is not saved.|
|File > Save||Save the current requirements links to an external file named model_name.req, or to the previously specified file. Any changes you have made to the model are also saved.|
|File > Save As||Rename and save the model and the external requirements links. The external file is saved as new_model_name.req.|