It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×12,005
×3,954
×403
×92
×42
×3

question asked: Mar 03 '13, 10:19 p.m.
question was seen: 7,305 times
last updated: Nov 12 '13, 12:36 p.m.

Related questions

RRDI and RRC - Count links

0
Chris Hardy (36●5●16●19) | asked Mar 03 '13, 10:19 p.m.
Hi,
I am hoping someone can give me an idea has to how to do the following.
Using RRDI I want to draw a pie chat for all requirement artifact, broken don into
artifacts with no links,
artifacts with at least one link

Is there a simple way yo do this?

4 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Chris Hardy (36●5●16●19) | answered Mar 05 '13, 11:37 p.m.
Working with a colleague of mine we finally found an answer using a join configured as a "Left Join"
I have stored the details here
0
permanent link
Sudhakar Frederick (801●1●36●31) | answered Mar 04 '13, 12:06 a.m.
JAZZ DEVELOPER
Hi Chris,
Appears we're both trying to kill the same bird:-)
I took a shot at this but my head's done in so I'm hoping someone from the RRDI/RM team can help.
Here's what I did so far.
For example, all Actors linked/Not Linked to Use Case Diagrams. I've been able to get something working :
Actors Linked/Not Linked to Use Case Diagrams
and the corresponding data :
Actor 2 UCD List

All good so far and I was almost happy. Except I changed the queries to use selectable parameters so the user can choose what type of requirement is linked/not linked to some other type. Then trouble. If I select Actor Linked/Not Linked to Feature I get:
Actors Linked/Not Linked to Features
with data :
ACtors 2 Features List
Which *seems* correct except that 2 actors are missing ("Financial Business Manager" and "Registered User"). In other words, I would expect that no matter what type of "target" requirements I select, the total number of source requirements remains 13.

I've tried all sorts of options but no success. The XML for the report is here.
Basically I have a query that has:
[Business View].[Requirement].[Requirement ID]
[Business View].[Requirement].[Name]
[Business View].[Requirement].[Requirement Type] with Filter [Requirement Type] in ?ReqType?
[Business View].[Requirement Related Requirements].[Name]
[Business View].[Requirement Related Requirements].[Requirement Type] with Filter [Link Type] in ('Link') or [Link Type] is null
[Business View].[Requirement Related Requirements].[Link Type] with Filter [Requirement Type2] in ?TargetType? or [Requirement Type2] is null
A data item [Linkage] which is 
IF ( [Link Type]='Link') THEN
	
    ( 'Linked' )
	
ELSE 
	
    ('Not Linked' )
A data item ID_Count which is 
count( distinct [Requirement ID])
The Chart has its measure set to ID_Count and Series set to Linkage.



Comments
Chris Hardy commented Mar 04 '13, 6:20 p.m.

Hi Freddie,
I didn't even get that far I'm afraid.
The issue I has is that I couldn't get counts of requirements that have at least one link or no links.
The question I have with your example is what happens when a requirement has more that one link to/from it?
0
permanent link
Sudhakar Frederick (801●1●36●31) | answered Mar 04 '13, 7:38 p.m.
JAZZ DEVELOPER
The count distinct for ID_Count *should* take care of duplicates
Comments
Chris Hardy commented Mar 04 '13, 9:27 p.m.

Ok, the problem is getting a distinct count of :
Requirements of type "Actor" with a link of type "Link" to Requirements of type "Feature"
vs
Requirements of type "Actor" with no links at all  + Requirements of type "Actor" with a link of type "Link" to a Requirement of any type.

The problem arises where an Actor with a link of type "Link" is linked to both a Requirements of type "Feature" and Requirement of any type.

What i think needs to happen is the count has to iterate (for loop ??) through at all links to/from the source requirement
If the requirements has any links to Feature then count it as linked
otherwise count it as not linked
If the requirement has no links count it as not linked

Not quite sure how to do this as yet

Hope this makes some sense?

0
permanent link
Sudhakar Frederick (801●1●36●31) | answered Mar 04 '13, 9:34 p.m.
JAZZ DEVELOPER
Yes, but looping isn't the answer. You should in theory be able to do:
Query for all requirements of type actor
Query for all Trace To requirements (or Requirements related Requirements with Link Type=Link) of type Use Case Diagram
Join the two queries and count all requirements of type actor and count those with/without links

I've tried this but I can't get the right data and can't work out what to Join on, and the implicit Join as above doesn't quite do it.



Comments
ross jones commented Nov 12 '13, 12:36 p.m.

folks,
I have run across a behavior of RRDI [which i consider a defect] related to counting artifacts of type requirement [it may apply to other types as well].
The behavior is that when RRDI is asked to count the artifacts of type requirement, it counts the number of unique instances of the data warehouse field "requirement ID", rather than the data warehouse field "reference ID". Reference ID is the unique identifier for artifact of type requirement, while "requirement ID" is unique identifier of EACH INSTANCE of the artifact, i.e. if you use the artifact in multiple locations in RM, e.g. module, collection, etc., RRDI returns the count of each time it is used rather than the true unique number of requirements. This behavior causes my reports to return the wrong number [count] for some reports I am running.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.