User`s guide

7 Navigation from Requirements Documents
7-10
Microsoft Office
In this section...
“Why Add Navigation Objects to Microsoft Office Requirements?” on page 7-10
“Enable Linking from Microsoft Office Documents to Simulink Objects” on page 7-10
“Insert Navigation Objects in Microsoft Office Requirements Documents” on page
7-11
“Customize Microsoft Office Navigation Objects” on page 7-12
“Navigate Between Microsoft Word Requirement and Model” on page 7-13
“Navigate with Objects Created Using ActiveX in Microsoft Office 2007 and 2010” on
page 7-14
Why Add Navigation Objects to Microsoft Office Requirements?
You can use the Microsoft Word and Microsoft Excel applications to capture, track, and
manage requirements. The Requirements Management Interface (RMI) allows you to
link Simulink objects to requirements managed by external applications.
When you create a link from a Simulink object to a requirement in a Microsoft Office
document, the RMI stores the link data in Simulink. Using this link, you can navigate
from the Simulink object to its associated requirement.
You can also configure the RMI to insert a navigation object in a Microsoft Office
requirements document. This navigation object serves as a link from the requirement to
its associated Simulink object.
Enable Linking from Microsoft Office Documents to Simulink Objects
By default, the RMI does not insert navigation objects into requirements documents. If
you want to insert a navigation object into the requirements document when you create
a link from a Simulink object to a requirement, you must change the RMI’s settings.
The following tutorial uses the slvnvdemo_fuelsys_officereq example model to
illustrate how to do this.
The RMI can insert navigation objects into the following Microsoft Office applications:
• Microsoft Excel
• Microsoft Word