User`s guide

Requirements Links for Library Blocks and Reference Blocks
5-19
Requirements Links for Library Blocks and Reference Blocks
In this section...
“Introduction to Library Blocks and Reference Blocks” on page 5-19
“Library Blocks and Requirements” on page 5-19
“Copy Library Blocks with Requirements” on page 5-20
“Manage Requirements on Reference Blocks” on page 5-20
“Manage Requirements Inside Reference Blocks” on page 5-21
“Links from Requirements to Library Blocks” on page 5-24
Introduction to Library Blocks and Reference Blocks
Simulink allows you to create your own block libraries. If you create a block library,
you can reuse the functionality of a block, subsystem, or Stateflow atomic subchart in
multiple models.
When you copy a library block to a Simulink model, the new block is called a reference
block. You can create several instances of this library block in one or more models.
The reference block is linked to the library block using a library link. If you change a
library block, any reference block that is linked to the library block is updated with those
changes when you open or update the model that contains the reference block.
Note: For more information about reference blocks and library links, see “Libraries” in
the Simulink documentation.
Library Blocks and Requirements
Library blocks themselves can have links to requirements. In addition, if a library block
is a subsystem or atomic subchart, the objects inside the library blocks can have library
links. You use the Requirements Management Interface (RMI) to create and manage
requirements links in libraries and in models.
The following sections describe how to manage requirements links on and inside library
blocks and reference blocks.