Identifying relationships between requirements of specific types

Hey Tom,

I think you can get to where you'd like to be by using a variable in a repeat statement. I've attached an sample of how this could look, but read on for an explanation...

Start off with a loop for all of the 'Business Requirements' type of requirements, (re)setting your initial variable value - use a $repeat statement limited to the appropriate type, and $set your variable. I used $$ProjObRef so it reflects some meaning, but it can be anything you like.

Switch the variable (reset it) if there are any referenced 'Project Objective' requirements. I used a $when/$endwhen section instead of nesting another repeat statement for some added template performance (be sure to use an appropriate conditional clause here, too), since we're just looking to see if any references exist and we don't actually need any other info on those requirements.

Next, use an $if statement to check the variable's value, and include keywords for the requirement ID, name, or whatever other requirement properties you'd like (this is the exception list) if the variable hasn't been changed up by the new setting inside the $when/$endwhen.

Tie up the snippet with an $endrepeat, and there you have it. Let us know if you have questions.

A caveat: by having a "top level" business requirement, I'm assuming you mean at the top level of your project. You could limit the scope of your reporting to only include the top level package to report on just that level of requirements. If you instead mean "non-nested" requirements (not including any children in your list), you should add "and IsTopLevel = True" to the first line of the example.

Jason,

Working pretty well. I've got a small amount of tweaking to do to get it completely clean (I have a $blankValue set, and it seemed to be implemented whenever there were no referenced requirements at all). Overall, I like the concept and I think I will find it very useful.

Thanks!

Tom

Jason,

Here's the actual code I have implemented:

$set $$ProjObRef false

New Listing

$repeatRequirementsSortID where Type = ‘Business Requirement’ and IsTopLevel = True and not ID contains ‘BRD’ and ReferencedRequirements Exist

$set $$ProjObRef false

$whenReferencedRequirements where Type = ‘Project Objective’

$set $$ProjObRef true

$endWhenReferencedRequirements

$if $$ProjObRef = false

$ID $Name has no references to project objectives.

$endif

$if $$ProjObRef = true

$ID $Name has references to project objectives.

$endif

$endRepeatRequirements

For some reason, when I run it, I get a list of the requirements which have (and do not have) references to project objectives, but I am also getting a number of rows/records interspersed in the listing which are showing the $BlankPropertyValue. I don't really know how to identify when these items are being generated. I'm playing with it, but do you have any quick insights?

Tom

Looks like this one's on us, Tom. There's a problem with $endwhen that's causing your blank property values to be displayed. If you didn't have blank values set - or temporarily reset $BlankPropertyValue to nothing - you'd get an empty line, instead.

I've got this reported & tracked in our internal defect system; the fix should be coming to CC 2013 soon!

Jason

Shades of my days as a Fortran programer! It ain't pretty, but it's working the way I need:

$set $$ProjObRef false

$repeatRequirementsSortID where Type = ‘Business Requirement’ and IsTopLevel = True and not ID contains ‘BRD’ and ReferencedRequirements Exist

$repeatReferencedRequirements where Type = ‘Project Objective’

$showOnce

$set $$ProjObjRef true

$endShowOnce

$endRepeatReferencedRequirements

$if $$ProjObjRef = true

$ID $Name has references to project objectives

$endif

$if $$ProjObjRef = false

$ID $Name does not have references to project objectives.

$endif

$set $$ProjObjRef false

$endRepeatRequirements

Thanks!

Tom