The Rational RequisitePro-XDE Integration can associate the XDE model and any of its packages to distinct RequisitePro projects. You must associate the model with a RequisitePro project before you can associate any packages to RequisitePro projects, but you do not have to associate packages to the same RequisitePro project as the model. You must have project structure permissions in RequisitePro to associate an XDE model with the project. You must belong to the Administrators group or a user group with the permission "Can manage project structure."
The association includes the following information:
RequisitePro project
Default requirement type: controls the choice of attributes, such as priority or status, that you use to define and manage requirements associated with model elements.
Default document type: determines the template for your Word document and a default requirement type for all requirements in that document.
These associations affect subsequent associations between model elements in the model or package and RequisitePro documents and attributes. Elements contained within the package inherit the default settings for the package, not the model. Package associations do not affect use cases that may have been previously associated with a different project.
These associations to RequisitePro are treated as default information for creating associations between model elements and requirements. For any given model element, the default project is the closest package association in the hierarchy. The search will start with the element’s parent package; if that is not associated, then it will proceed to that package’s parent for an association, and so on. If no packages in the hierarchy are associated to a project, then the model’s association is used. Disassociating a model or package from a project removes the default information for creating new associations but does not remove or otherwise change existing associations.
The integration does not discriminate between packages, storage units, and controlled units. However, you must take certain considerations into account when saving packages that are under source control. We recommend that you develop and implement your source control strategy in your model before you create associations between elements in storage units and requirements.