Creating Requirements in Linked Libraries
You can create a requirement link for the contents of a library
model. If you copy a library linked object to a Simulink model
and disable the link, the software copies the contents of the linked
object, including requirement links, to the model. Any navigation
control in the requirements document still links to the object in
the library.
You can also create a requirement link for the copy of a library
linked object in a model (Model 1 in the following graphic). If you
then push the change to the library, the software copies the requirement
link to the library. However, any navigation control in the requirements
document still links to the object in Model 1.
If you then link to that library object from another model (Model
2) and disable the link, the software copies the link to the requirement.
Any navigation control in the requirements document still links to
Model 1, creating the situation illustrated in the following graphic.
 | Deleting Requirement Links from Simulink Objects | | Creating a Requirements Report |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
Get this Simulink Kit
Store 
