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? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiraplan/best-practices/2691.aspxthreadId=2691Gabe Johnson (gabe.johnson@oroliads.com) 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? Thu, 13 Oct 2022 14:46:09 -04002025-09-08T03:26:15-04:00/Support/Forum/spiraplan/best-practices/2691.aspxmessageId=5770David J (adam.sandman+support@inflectra.com) Hi Gabe, Normally wed 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 Thu, 20 Oct 2022 21:31:42 -04002022-10-20T21:31:42-04:00/Support/Forum/spiraplan/best-practices/2691.aspx#reply5770messageId=5773Ilia Poliakov (ilya.polyakov@edetek.com) My experience is that you should track requirements into Spiras projects that means your products. And additionally to create Spiras 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 prooducts requirements via associations and by it you will have whole tracebility. Spiras Project What requirements means Product A Features of the Product A Product B Features of the Product B Customer AA Bundles that were or going to be delivered. Might have multiple to multiple relations to all products. Customer BB Bundles that were or going to be delivered. Might have multiple to multiple relations to all products. OR Customer support Customers as a level-1 requirement and bundles with their timeline under it. Fri, 21 Oct 2022 09:25:37 -04002022-10-21T09:25:37-04:00/Support/Forum/spiraplan/best-practices/2691.aspx#reply5773messageId=7252kenvin roll (rollkenvin@gmail.com) This approach of using a base product for core requirements and creating variants is efficient. It promotes consistency and simplifies management across different product lines. Great recommendation, David! https://www.inflectra.com/Support/Forum/spiraplan/best-practices/2691/Quote/5770.aspx Mon, 19 May 2025 07:56:55 -04002025-05-28T07:32:48-04:00/Support/Forum/spiraplan/best-practices/2691.aspx#reply7252messageId=7374Federico Merritt (fwsmgqehkwwisqljci@nespf.com) I like that idea too, it definitely makes handling different product versions less messy. Thanks for sharing the link, Ill check it out. Mon, 08 Sep 2025 03:26:15 -04002025-09-08T03:26:15-04:00/Support/Forum/spiraplan/best-practices/2691.aspx#reply7374