You can create SysML requirements, supporting items (Actors, Comments, Constraints, Problems, Rationales, Requirement Diagrams, Use Cases and Use Case Diagrams) and traceability relationships in either the Modeler or DOORS environment; Integration for IBM Rational DOORS synchronizes Requirements and their supporting items between the two environments.

It is worth remembering that when you create a model item or diagram in the Modeler model, that item or diagram is not going to be represented in the DOORS surrogate module until a synchronization is performed. This makes creating requirements and traceability links in Modeler, rather than in DOORS, advantageous because the model items and diagram are available for linking without having to perform a synchronization; however, there are other issues that you should consider.

Typically, you will start a project with requirements defined in a Modeler Model or in a DOORS surrogate module:

After you have synchronized your requirements between Modeler and DOORS, you can create and maintain those requirements in DOORS, Modeler or both environments.

You should make a decision as to whether you are going to create and maintain requirements in Modeler, DOORS or both, and then set up your Integration for IBM Rational DOORS Mappings accordingly:

If a requirement has been changed in both environments a clash can occur. When a clash occurs, you are prompted to resolve the clash, either before or during the synchronization depending on whether the Perform Clash Analysis check box is selected.

When Integration for IBM Rational DOORS synchronizes Modeler Requirements with a DOORS surrogate module, the following item types can be included in the synchronization:

In the DOORS surrogate module, the preceding item types are represented as formal objects that have their 'SysML Model Element Type' attribute set to either Actor, Comment, Constraint, Problem, Rationale, requirementDiagram, Use Case or Use Case Diagram.

If you want to use the preceding item types to extend the definition of your requirements, we recommend that you create and define these items in the Modeler environment, because it is easier to do so.

You can create and define formal objects in the DOORS surrogate module and then make Integration for IBM Rational DOORS create the preceding items in the Modeler Model, but it is not so easy to do so.

When Integration for IBM Rational DOORS synchronizes a Modeler Package with a DOORS surrogate module or surrogate module, you can include the following SysML relationship types in the synchronization:

In the DOORS surrogate module or surrogate module, the preceding traceability relationships are represented as links that have their ART Link Type attribute set to either allocatedTo, derivedFrom, refines, satisfies, tracesTo or verifies.

If you want to use the preceding traceability relationships with your requirements, we recommend that you create and define these relationships in Modeler because it is easier to do so.

You create the links in the DOORS environment, but when synchronizing them to Modeler you will be prompted to select the traceability relationship type to create for each link in the Modeler model.

The Link Synchronization Direction options determine whether traceability links are exported from Modeler to DOORS, imported from DOORS to Modeler, or both:

If a traceability relationship has been changed in both environments a clash can occur. When a clash occurs, you are prompted to resolve the clash, either before or during the synchronization depending on whether the Perform Clash Analysis check box is selected.

When deciding on how you are going to create and maintain your requirements, supporting items and traceability relationships, you should also consider the following factors as well.