I have a single product that consists of multiple pieces of software all maintained by my team.  There are also variants of this product that inherit a majority of the requirements from the base product but then might have a few additional requirements.  A particular release of the base product might contain several releases of support software.

Are components the correct this to use in this situation? i.e.

• Base Product
  • Product Variant 1
  • Product Variant 2
  • Software Package A
  • Software Package B

We also have various optional software products that may be installed into the Base Product.  Sometimes this might require changes to the Base Product and sometimes not.  Would these be considered separate products?  Can I connect requirements between products?

Hi Gabe,

Normally we'd recommend creating a base Spira product that contains the core system requirements. Then you can create product variants as their own Spira products that contain the different core requirements.

Then you can share the core requirements from the base product to the variant products using the 'Product Associations' feature.

For example:

• Core features
  • Core feature 1 (project PR1)
  • Core feature 2 (project PR2)
  • Core feature 3 (project PR3)
• Product variants
  • Product A (PR4)
    • requirements from PR1
    • requirements from PR2
    • Its own requirements
  • Product B (PR5)
    • requirements from PR1
    • requirements from PR3
    • Its own requirements

Regards

David