Skip Navigation LinksHome Page > Forums > SpiraPlan Forums > SpiraPlan Best Practices > Product with multiple sof...
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.
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?
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.
My experience is that you should track requirements into Spira's projects that means your products.
And additionally to create Spira's projects that means your customers. Or to create one project "Customer support" where as a requirements create delivered bundles to customers. Those requirements should be associated to your prooduct's requirements via associations and by it you will have whole tracebility.