Import Overview
This page provides an overview of how the ReqIFIntegration package works when importing ReqIF files.
Supported File Formats
-
The ReqIF import function allows you to specify files in XML format (
.reqif) or compressed format (.reqifz). -
If
.reqifzcontains multiple ReqIF data, only the first ReqIF file found will be imported.
Importing Request Type Definitions
Executing "Import Request Type Definitions" converts the type definitions contained in the ReqIF file into the Next Design metamodel and creates a view definition for browsing.
Converted Metamodel
Type definitions are converted into the Next Design metamodel according to the following correspondences:
| ReqIF Type Definition | Next Design Metamodel |
|---|---|
| SpecificationType/SpecObjectType/SpecRelationType/RelationGroupType | Metaclass |
| DataTypeEnumeration | Enumeration Type |
| Standard Attributes (Identifier, Description, LastChange) | Field |
| Custom Attributes (SpecAttribute) | Field |
For details, please refer to the ReqIF Element and Next Design Correspondence Table.
View Definition for Viewing
When importing type definitions, a view definition for viewing the requirement model is also automatically generated.
| View Name | Target | Mime Type | Content |
|---|---|---|---|
| Requirement | Specification | Tree Grid | Lists requirements in a hierarchical structure. Includes column definitions corresponding to fields. |
| Detail | SpecObject | Form | Displays details of individual requirements. Includes control definitions corresponding to fields. |
Type Definition Update Import
When you repeatedly execute "Import Required Type Definitions" for the same project, the existing metamodel will be updated if one exists.
Metamodel Update Decision
The LastChange attribute included in each type definition (SpecType, DataType, etc.) in ReqIF is compared with the last modification date recorded in the metamodel on the Next Design side. If they differ, an update is performed.
Updated Content
During the update, the following information will be overwritten with the information in the ReqIF file:
- Class name, field name
- Display name
- Enumeration type, enumeration value
The update import does not overwrite the existing view definition itself. Column definitions and control definitions are added to the automatically generated view definition as needed. View definitions added by the user are maintained.
Type Definition Deletion Confirmation
If type definitions (classes, fields, enumerations, enumeration values) that do not exist in the ReqIF file remain in Next Design, a deletion confirmation dialog will appear.
-
Select [Yes]: Deletes the corresponding type definition. Deleted type definitions are output to the Output tab.
-
Select [No]: Continues import without deletion. Candidate type definitions for deletion are notified in the Output tab.
This deletion is performed as part of the import process and can be undone with a single undo.
Importing Requirements
Executing "Import Requirements" imports the requirement objects (SpecElementWithAttributes) contained in the ReqIF file as models in Next Design.
Prerequisites for Execution
Before executing "Import Requests," select a model of type "__ReqIF_ReqIFContent" in the Model Navigator. If the model does not exist, add it before selecting.
Importing Hierarchical Structure
Request objects are imported according to the ReqIF structure (hierarchical structure under Specification).
Updating Request Import (Re-import)
When "Import Requests" is executed repeatedly for the same project, existing models will be updated if they exist (hereinafter referred to as "updating import").
-
By default, the Identifier of the request object is used to determine if an existing model is identical (search key).
-
For data where the Identifier changes with each update, the updating import may not be able to identify the existing model, and it may be treated as a new import.
In this case, you can change the key used for the updating import (the attribute treated as an ID) in "Import Settings."
Deletion Confirmation
When updating and importing, if there are models (candidates for deletion) that do not exist in the ReqIF file but only exist in Next Design, a deletion confirmation dialog will be displayed.
-
Select [Yes]: Deletes the candidate model. The full path of the deleted model will be output in the Output tab.
-
Select [No]: Continues the import without deletion. The candidate model will be notified in the Output tab, so delete it manually if necessary.
This deletion is performed as part of the import process and can be undone with one undo.
Hierarchy Position and Order Change
When updating and importing, if the hierarchy position or order of siblings of the requirement objects changes in the ReqIF file, the models in Next Design will also move automatically.
-
Parent Element Change: If the parent of the requirement object changes in the ReqIF file, the models in Next Design will also move under the new parent.
-
Order Change: If the order of siblings changes in the ReqIF file, the order of the models in Next Design will also change.