Requirements Management Interface

Synchronizing the Navigator with DOORS

What Synchronizing Does and When to Synchronize

You synchronize the object that is open in the Navigator to associate it with a project in DOORS.

• Synchronize the first time you open a given object in the Navigator. This causes DOORS to create a formal module called a surrogate exported module that represents the hierarchical structure of elements in the object. You can then use DOORS to associate requirements with the elements in that surrogate exported module.
• When you open an object in the Navigator that already has a DOORS surrogate exported module associated with it, the Navigator checks whether the object and module are synchronized. If the date of the model or M-file is more recent than the synchronization date for the DOORS module, you must synchronize again.
• Synchronize again whenever you:
• Change links in the DOORS project
• Make changes to the object in Simulink, Stateflow, or MATLAB

Synchronizing causes changes to be reflected in the Navigator for that object, and in the DOORS surrogate exported module for that object.

• Synchronizing automatically saves the object.
• For a Simulink or Stateflow node, the Requirements Management Interface stores information about the requirements with the object.
• For an M-file node, the Requirements Management Interface writes a commented line to the M-file. Do not modify this line. For example,

% Autogenerated requirements (do not modify) = { 'DOORS' 'engine' '1' 'true' }

Note    You must have write permission for the object in order to synchronize. If you do not have write permission for the object, you can still view the DOORS requirements associated with the object.

Stateflow Charts and MATLAB M-Files in the Navigator

How to Synchronize