Hi all,
I was trying to show the Parent-Child relationship among requirements in one module. I have created a linkset so that the requriements are able to link to others in the same module. However I am having a hard time to articulate which ones are parents and which ones are children.
My questions are:
1. Is that a way in DOORS displaying "child of" and/or "parent of" linkt type for requirements?
2. What to do if there is a Grandparent-Parent-Child relationship?
I was wondering if anyone out there have the same need as mine in terms of clearly picturing the relationships, and how you have done it?
Any thoughts/ideas?
Cheers,
Angela
BPA - Wed May 05 19:50:19 EDT 2010 |
|
Re: Link between Parent and Child requirements
llandale - Thu May 06 18:33:23 EDT 2010
Perhaps you mean you created a 'LinkSet Pairing' to support the linking, using the Module Properties screen.
It seems to me the direction of you link will determine the Hierarchy, where links go from source 'child' to target 'parent' when the link means 'satisfies'; perhaps you say "Object Child satisfies Object Parent". Link from source Parent to target Child when the link means 'justifies' or 'drives': Object Parent justifies Object Child". The vast majority of folks use links to 'satisfy' parent requirements. Test objects 'test' or 'prove' requirements. Requirements 'are derived from' Use Cases. Test Plans 'implement' Test Procedures. Since the source object 'owns' the link, you generally source the link in the object that is driving the relationship.
So lets have child requirements 'satisfy' parent ones by linking from child to parent. You use the Analysis wizard to trace links at depth 1 (children or parents) or depth 2 (grandchildren or grandparents); but may have to de-conflict the layout for circular linking. You have a link module and either do incoming links (to show children) or outgoing links (to show parents).
|
|
Re: Link between Parent and Child requirements
SystemAdmin - Fri May 07 03:33:57 EDT 2010 llandale - Thu May 06 18:33:23 EDT 2010
Perhaps you mean you created a 'LinkSet Pairing' to support the linking, using the Module Properties screen.
It seems to me the direction of you link will determine the Hierarchy, where links go from source 'child' to target 'parent' when the link means 'satisfies'; perhaps you say "Object Child satisfies Object Parent". Link from source Parent to target Child when the link means 'justifies' or 'drives': Object Parent justifies Object Child". The vast majority of folks use links to 'satisfy' parent requirements. Test objects 'test' or 'prove' requirements. Requirements 'are derived from' Use Cases. Test Plans 'implement' Test Procedures. Since the source object 'owns' the link, you generally source the link in the object that is driving the relationship.
So lets have child requirements 'satisfy' parent ones by linking from child to parent. You use the Analysis wizard to trace links at depth 1 (children or parents) or depth 2 (grandchildren or grandparents); but may have to de-conflict the layout for circular linking. You have a link module and either do incoming links (to show children) or outgoing links (to show parents).
problems for traceability.
|
|
Re: Link between Parent and Child requirements
MikeGehringer - Thu May 27 15:48:08 EDT 2010
Hi Angela,
DOORS does not dictate the relationship, thus links are either in or out. You need to establish a convention that says all links will begin with the child and end with the parent. This way, like Pekka stated, it is understood that an outlink will take you to the parent. This also allows a lower tier group to not have to have edit access to a higher tier.
To complete the picture, we have the higher order tier allocate the requirement to the lower tier (they have an attribute within which they select the lower tier group). The lower tier can then filter on the higher tier module and then link their requirements up to the higher order document.
Hope that makes sense.
Mike G>
|
|