Reuse and synchronization
Reuse in Jama Connect is much more than a copy/paste mechanism. It’s a full suite of features that allows for complex capabilities like:
Maintaining a library of common requirements
Branching a project to create a variant product
Comparing differences between a local version of a requirement and its source library version
Reuse and synchronization methods detect variance and highlight the impact of that variance across releases and projects. These methods are useful whether your product keeps the same requirements as a previous version; if it integrates and improves on original requirements; or if you include custom requirements for each product.
To save time and effort for your teams:
Reuse common product requirements across projects.
Sync reused items to help determine and track variance across projects.
When you apply reuse and synchronization methods within your requirements management configuration infrastructure, you maximize your requirements resource management. You can modify and evolve existing work quickly while maintaining your requirements lineage.
Library approach
A library project houses a collection of requirements maintained by a librarian or curator (permissions-based).
The curator of a library can pull differences back into the library when needed.
Project members can pull and push updates between the project and the library.
Branching approach
Projects are branched by project duplication.
Synchronization is enabled during project duplication and differences are monitored between containers and items.
Jama Connect recommends creating a project baseline just after duplication. A baseline captures the state of the project at the time of duplication and is used for baseline comparisons.