Mapping Table: DOORS Artifact Types to Jama Connect Item Types in ReqIF Imports

Kemi
Kemi
  • Updated

This table provides a predefined mapping of common DOORS artifact types and their corresponding Jama Connect item types to ensure correct alignment during ReqIF imports.

1. Standard Mapping of DOORS Artifact Types to Jama Item Types

 
 
 

DOORS Artifact Type

Equivalent Jama Connect Item Type

Notes

Requirement

Requirement

Standard requirement mapping

Heading

Heading

Used for structuring hierarchy

Module

Component or Set

Represents a collection of requirements

Test Case

Test Case

Direct mapping to Jama test cases

Test Step

Test Step

Must be inside a test case in Jama

Use Case

Use Case

May require a custom item type

Risk

Risk

If not available, create a custom item type

Change Request

Change Request

May require enabling in Jama

Decision

Decision

Can be mapped to an existing item type

Stakeholder Need

Business Requirement

Ensure traceability to system requirements

Business Rule

Business Rule

May require enabling in Jama

Functional Spec

Functional Requirement

Standard requirement mapping

System Requirement

System Requirement

Direct mapping in Jama

Design Specification

Design Specification

Can be mapped to a requirement or a document item

Architecture

Architecture

Requires a custom item type in Jama

Interface Requirement

Interface Requirement

Direct mapping in Jama

Performance Spec

Performance Requirement

Ensure correct item type mapping

 
 

2. Best Practices for Mapping DOORS Artifact Types to Jama

Verify the artifact types in the ReqIF file before import.
Ensure Jama has a matching item type for every artifact type in DOORS.
If an artifact type does not have a direct mapping, create a custom item type in Jama.
Use a standardized mapping template for repeatable ReqIF imports.
Validate mappings in a test environment before executing full imports.

3. Handling Custom DOORS Artifact Types

  • If DOORS artifact types do not match standard Jama item types, you can:

    • Map them to an existing item type that fits logically.

    • Create a custom item type in Jama to maintain traceability.

    • Use a generic "Other" category and refine the classification post-import.

4. Conclusion

  • DOORS artifact types correspond to Jama item types, with direct mappings for most common artifacts.

  • For unmatched artifact types, custom item types in Jama may be required.

  • Proper mapping ensures that requirements, test cases, and design specifications align correctly in Jama Connect.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.