Welcome to the Jazz Community Forum
Variant management in ELM
We want to manage requirements for 2 different versions/variants and considering 2 options:
1. Maintain 2 separate streams - one for each variant
2. Use a custom attribute (multi value Enum type) that tells if the requirement is applicable for variant 1, variant 2 or both variants.
Which of these approaches is recommended by IBM? Considering database size and performance, which one will be better?
5 answers
I think the answer depends on how many variation points you will have, and whether you will have more than two variants eventually. If you use a custom attribute you likely should use separate streams also.
I've done this numerous times, both with and without GCM.
- what apps are you looking to use? Across the board or DNG only?
- how many variants do you have or is it unknown?
- are your users familiar with GCM or CM in general?
The way both DNG and ETM allow you to reuse data makes it a whole lot simpler to manage this - you can do it with GCM turned on and it is certainly a lot simpler, but you can also do this without any CM enabled and some rigour to your process by making use of workflow enabled artefacts (RM and QM) and reuse.
One of the more complex clients I helped was managing three base product variants and then a dozen client variants of one or more of the base ones. They were a small company using ELM SaaS and their size meant they had no access to GCM in their instance.
You wrote:
>>> Will the DB size double as soon as a new stream is created or only the differences between 2 streams are saved by DOORS Next?
The size will not double. There is reuse in the streams (until you make changes in one of the streams).
Comments
Chidambaram L
Apr 16, 7:15 a.m.Item 1 is the real method for Variant Management.
Davyd Norris
Apr 18, 9:22 p.m.