This functionality is being introduced from RMsis version 1.8.7 onwards.

Introduction and Context

For many large systems, sometimes the System Requirements may be managed in other systems (like IBM DOORS), while specific software components may be developed using RMsis. This functionality is being implemented to support such scenarios.

Since the Requirements are managed externally and evolve there, they will exist inside RMsis in a READ_ONLY (committed) state. So a user will be able to cross reference them inside RMsis, but not modify them.

Once some evolution has happened, the Requirements can be re-imported into RMsis as the next version.

Procedure

Export the Requirements from external system with all their attributes in CSV format and import these in RMsis using the same.
In RMsis Database, a field External_ID is provided.
Map Requirement_ID of Externally Managed Requirements to External_ID in RMsis.
ID field should not be mapped during the import process.
System will commit the imported Requirements, as soon as the Requirement is imported.
User can create a new version by mapping Requirement_ID of Externally Managed Requirements to External_ID in RMsis and re-importing the Requirement again.

Expected usability issues and their resolution

Some usability issues are perceived in the re-import process. For example, the users might have created cross references to the imported Requirements within RMsis.If the number of Requirements is large, this can lead to lot of rework for the users. In order to resolve this problem, the following supporting functions will be provided (maybe in a later version)

Bulk operations to copy Requirement Links of any version to the latest version.
Bulk operations to move Requirement Links of any version to the latest version.
Bulk operations to Edit / Update dependencies.

Limitations of this approach

An RMsis-ID will be auto-generated on import and will be used for cross referencing inside RMsis.
External-ID cannot be used for cross referencing within RMsis (for traceability purposes)

Notes

There will be no special treatment for editable and non-editable attributes of a Requirement.
In case the user manually creates another version of a Requirement in RMsis (say n) and performs an import, we will create the version (n+1) during import.

Browser not supported