Importing ReqIF
Import Configuration
 |
Make sure to map all attributes even the empty ones during import. Failing to do so will result in not being able to generate valid exports later.
|
Brief Summary of the recommended settings:
• Create a new Source when importing a specification for the first time.
• Enable including empty.
• Enable Remove absent items.
• Map all attributes.
The conversation to reconcile requirements between the OEM and the supplier is started by one or more requirement specifications sent by the OEM to the supplier. Each conversation should be mapped to a new “Source” in Codebeamer. When starting such a conversation a new source must be created even if a source has already been pre-selected . Automatic selection of the source does not always work reliably as many tools exporting ReqIF don’t include the necessary (recommended) information required to identify the conversation.
The name of the new source should be descriptive enough to easily identify it later when generating a response for the customer or when the OEM sends an update in scope of the conversation.
During initial import all attributes should be imported including the empty attributes. The attributes you as supplier are supposed to be populated when replying to the OEM are usually empty in the ReqIF received from the OEM. It is essential to establish the connection to the attributes definitions in the ReqIF during initial import to ensure the response you generate for the OEM is well formed.
The attribute ReqIF.ImportStatus is a virtual attribute indicating if an object in the ReqIF is new, updated or has been deleted using this update can be helpful once you receive updates from the OEM, therefore it is recommended to import it too.
Usually you will import the customer specification into new trackers. When doing that the attributes defined in the ReqIF and not already mapped to a corresponding attribute in Codebeamer should be mapped to new attributes.
If the ReqIF contains multiple object types, make sure to map all fields of all types.
The mappings in the tracker node are used to map attributes of the specification in ReqIF to the tracker in Codebeamer. Generally configuring any mapping in that section is not required and additional attributes created on that level will not be visible to the user in Codebeamer.