Linking Requirements

Hi Paul,

The drag/drop gesture from a requirement to another requirement is used to create a parent/child relationship (i.e. nested requirements), so you will need to create references via the Requirement Details form.  I guess we could add a variant drag/drop gesture to create references, e.g. Shift+drag or right-mouse drag.  Definitely a power-user type feature since it wouldn't be very discoverable.  Is the select referenced requirements dialog sufficient, or does it become unwieldy after a certain number of requirements? (Keep in mind that you can sort requirements by multiple columns by shift-clickin on the column headers in the selection dialog).  Other thoughts?

Hi Doug,

 I guess we could add a variant drag/drop gesture to create references, e.g. Shift+drag or right-mouse drag.

I would definitely make use of this feature. I do similar to what Paul has described.....within the business domain, the BRD template that we use at our company requires the business to supply us (IT) with specific (uniquely defined) "objectives" as well as specific (uniquely defined) "business requirements" (high level stakeholder requirements/needs/features).

Accordingly in CC I have defined two custom requirement types, namely 'Business Objectives' and 'Business Requirements' to capture these.

Then, we (IT) in the solution domain link all of the detailed functional/non-functional requirements back to the business domain. Also within the solution domain we separate all of the business rules and link requirements to those.....so the drag and drop feature would be very handy indeed. (I'd vote for the right-mouse drag......you could also make the right-mouse drag work for requirements <=> Use Cases too for consistency purposes, and keep the current left-mouse drag in place as well for those used to that).

Thanks

Adam

Within the solution domain, I

Oh yeah!

Me, too!

I was just going through this with my team on a (for us) big project.  Drag and drop would be a huge help for us, since we also use Business Requirments and Project Objectives as requirements types in CC.

Hi Tom (and Adam and Paul),

We added this capability to our latest release (version 2012).  You can select multiple requirements in the main list, then drag them, and while holding the shift key, drop them on another requirement to create the reference instead of creating a nested requirement. This works in the project browser too if you don't need to handle more than one requirement at a time.

There is one small issue that I should mention which we will fix - if you have references to the requirement(s) being dragged, CaseComplete may tell you that reference fix-up is required because it needs to renumber the child requirements. Since it's not creating child requirements, just ignore this message (press OK) and the requirement-to-requirement reference will be created.

Doug

Hi Doug!

Best news I have heard in a while!  We are just in the process of upgrading to 2012, so I can't wait!!!

Ciao!

Tom