ReqIF Element and Next Design Mapping Table
The ReqIFIntegration package automatically generates a metamodel (metaclass/field/enumeration, etc.) on the Next Design side based on the type definitions (SpecType, etc.) included in the ReqIF file, and imports the requirements model according to that metamodel.
This page summarizes the concept of mapping relationships when no customization is performed (using the default behavior).
Mapping of Type Definitions (Metamodel)
| Main Elements on the ReqIF Side | What is Done on the Next Design Side (Default) |
|---|---|
| DataTypeEnumeration | Creates and updates enumeration types (including enumeration values). |
| SpecificationType | Creates and updates metaclasses, and creates and updates fields corresponding to standard and custom attributes. |
| SpecObjectType | Creates and updates a metaclass, and creates and updates fields corresponding to standard and custom attributes. |
| SpecRelationType | Creates and updates a metaclass, and creates and updates fields corresponding to standard and custom attributes. |
| RelationGroupType | Creates and updates a metaclass, and creates and updates fields corresponding to standard and custom attributes. |
Metaclasses and enumerations are automatically generated based on the ReqIF Identifier. (The generated names will vary depending on the content of the ReqIF.)
Standard Attribute (Default Field) Mapping
Each metaclass has attributes commonly handled in ReqIF mapped as default fields.
| ReqIF Attribute | Next Design Default Field |
|---|---|
| Identifier | Identifier |
| Description | Desc |
| LastChange | LastChange |
The Description field in ReqIF corresponds to the Desc field by default in Next Design.
In addition to the above, the following default fields are associated with RelationGroupType:
| ReqIF Attribute | Next Design Default Field |
|---|---|
| SourceSpecification | SourceSpecification |
| TargetSpecification | TargetSpecification |
| SpecRelations | SpecRelations |
Custom Attribute (SpecAttribute) Support
SpecAttributes (strings, numbers, dates, booleans, XHTML, enumerations, etc.) included in SpecType are, by default, incorporated into the Next Design metaclass as "fields with the same name".
- Example: If
Attr_String_1is defined in ReqIF, anAttr_String_1field will also be created in Next Design. - The field type is determined by the data type in ReqIF.
Enumeration Mapping
ReqIF enumerations are imported as enumerations in Next Design.
-
Enumeration values are created and updated based on the enumeration value elements in ReqIF.
-
After import, they can be used as values for enumeration fields.