How do you mark requirements in Requisite Pro?
In the original use case template you will find the Section "1. Use case name". Replace this with the actual use case name that you propose to use e.g. Fetch user credentials. In the dialog that appears click "OK" don't give anything for the "name". The section would now look something like this [UCpending1Fetch user credentials]. Now save the document. The section would look like this [UC2Fetch user credentials]. Which means that your requirement is saved to the database. When you mark subsequent requirements in the same document specify the parent in the "Hierarchy" tab by choosing the use case name from the drop down. i.e. say you have a requirement "Fetch Financial authorisation limits" which is sub set of "Fetch user credentials" when you mark "Fetch Financial authorisation limits" as a requirement and specify that its a child of "Fetch user credentials" it would look like this [UC2.1Fetch Financial authorisation limits] this mechanism allows you to track requirements that have found their way to your code at a finer level of detail. i.e. Project progress tracking is finer because in MS Project (assuming you use it monitor your progress and you have trasfered the use cases to your schedule) if you have estimated a effort of 15 person days for [UC2Fetch user credentials] and assuming that you haven't specified hierarchy (no child requirements) then there would be a blip in your tracking GANTT chart (after 15 days) because until this requirement is finished fully (including unit testing) you would have to keep it pending, any attempt to indicate % completion would make your tracking GANTT highly subjective and suspect. So having child requirements allow you flag off ones that are complete (usually on a daily basis), the parent requirement would automatically show a progressive completion percentage.
In the original use case template you will find the Section "1. Use case name". Replace this with the actual use case name that you propose to use e.g. Fetch user credentials. In the dialog that appears click "OK" don't give anything for the "name". The section would now look something like this [UCpending1Fetch user credentials]. Now save the document. The section would look like this [UC2Fetch user credentials]. Which means that your requirement is saved to the database. When you mark subsequent requirements in the same document specify the parent in the "Hierarchy" tab by choosing the use case name from the drop down. i.e. say you have a requirement "Fetch Financial authorisation limits" which is sub set of "Fetch user credentials" when you mark "Fetch Financial authorisation limits" as a requirement and specify that its a child of "Fetch user credentials" it would look like this [UC2.1Fetch Financial authorisation limits] this mechanism allows you to track requirements that have found their way to your code at a finer level of detail. i.e. Project progress tracking is finer because in MS Project (assuming you use it monitor your progress and you have trasfered the use cases to your schedule) if you have estimated a effort of 15 person days for [UC2Fetch user credentials] and assuming that you haven't specified hierarchy (no child requirements) then there would be a blip in your tracking GANTT chart (after 15 days) because until this requirement is finished fully (including unit testing) you would have to keep it pending, any attempt to indicate % completion would make your tracking GANTT highly subjective and suspect. So having child requirements allow you flag off ones that are complete (usually on a daily basis), the parent requirement would automatically show a progressive completion percentage.
