Allow more customized control of requirement major/minor Version
We use requirement versions to determine when re-validation (re-review) of a requirement is necessary. Currently, we can only customize the major/minor version change due to requirement edits on custom attributes - we need this on all attributes. Example: we only want to re-review on updates to rqmt text (standard attribute), safety/derived flags and justifications (custom attributes), and changes that affect traceability up (Trace-From, but not Trace-To). Our review processes would be much more efficient if we could adjust the revision roll (Major/Minor/None) for any attribute - standard or custom.
Caliber 11.5 introduces the ability to allow users to decide if a change should cause a minor or a major version increment. This is a per-project setting.
Control over minor/major is a wide-spread request – but the details vary greatly from customer to customer.
Therefore, we provide a manual means of controlling minor/major as we currently have no plans to introduce a comprehensive and fully customizable workflow engine in Caliber.
Laki Vlachos commented
This is still listed as "More Info Needed", but I have not seen any updates after the post from Marty below. Customization of the version control is still a desire for us. Thanks!
No problem - thanks for looking at this feature: we would like to use the major vs. minor version to determine impact assessment of a requirement change. For example, to determine when to re-review a requirement: major version roll - definitely review it; minor version roll - probably ignore the change from a review standpoint. No increment is probably an option we can live without. "Custom" (or user-defined) attributes are no problem - Caliber provides excellent selection of major vs. minor. We cannot see that "standard" attributes are customizable - tell us how if this is incorrect. Distinction between Trace-To and Trace-From would be essential to optimizing our review process and here is why: when we review a requirement at any level, we review it for content, attributes, and whether it fulfills the requirement of the (parent) specification that it traces-from. If the trace-from changes, we want to review it to see that it still meets the parent requirement. If a lower tier (child) specification changes a trace-to this requirement, we don't care about that; its the responsibility of reviews of that lower tier specification that need to address that change. As a programmer, I imagine the trace-to/trace-from are somehow linked in the Caliber programming. But as a user, I can see where these are indeed separate attributes, have separate fields in the GUI, and thus should be able to have separate major/minor version control? Thanks! -Marty