ayodhya

 Profile Answers by ayodhya 

• Mar 4th, 2007

 

To give detail description of requirements we'll crete child req

alankarrahi

 Profile Answers by alankarrahi 

• Mar 5th, 2007

 

As one of the main purpose of TD and QC software is Requirement Managament, Child requirements are therefore created to map the client requirements with the test cases.


Hope this helps..


Regards,
Alankar

vasubha

• Jul 6th, 2007

 

Creating Child requirements to the main requirement is to evaluate into the sub requirements related to the main requirements. By this way we can link the test sets and the associated defects. The coverage of the requirement is shown clearly by this way.

sarega99

 Profile Answers by sarega99 

• Jul 1st, 2010

 

Any requirement document should have Parent and Child requirements.
Parent requirement will give you a high-level description of the requirements.
Child requirements will give more indepth details about a particual requirement
eg.
PR.1.0 ---> External User login(Parent Requirement)
CR.1.1 --->External username(Child Requirement)
CR.1.2 --->External password(Child Requirement)

siva

• Aug 15th, 2011

 

Any requirement document should have Parent and Child requirements.
Parent requirement will give you a high-level description of the requirements.
Child requirements will give more in depth details about a particular requirement
eg.
PR.1.0 ---> External User login(Parent Requirement)
CR.1.1 --->External username(Child Requirement)
CR.1.2 --->External password(Child Requirement)