In this blog post, you can learn
Let's get started.
In Analytics app, you can find Requirement Traceability tile. Next to this tile, there are Solution Process Traceability and Feature Traceability. SAP Cloud ALM for Implementation offers end-to-end traceability tools that you can track and trace Solution Processes, Requirements, and Features for your Project.
With these three traceability tools, you can drill down from the highest level to the lowest level of the entities. Since the status of each entity is maintained manually, it is crucial for the responsible person to manage and update the status according to the current situation. And these traceability tools support this action to be done in an easier and more convenient manner.
Here, we learn further details about a Requirement Traceability.
You can have a list view of the status of Requirements for a specific project, together with the status of Feature, User Story, Project Task, Test preparation, and Test Execution for each Requirement. The status of each entity is clearly and intuitively visualized with distinct colors like green, blue and red. Therefore, you can have a brief but comprehensive understanding about how the subordinate or related entities are going on and where the bottlenecks are.
First, there are various filters that you can adapt to the list, so that you can see what you want only. For example, you can sort out the data by selecting a specific Scope or Solution Process or Requirement Status.
Besides, you can also set a filter for each related entity such as Feature, User Story, Project Task, Test Preparation and Test Execution. Here, what we can pay more attention to is that there are three categories for each filter. Let's see a Project Task filter as an example. As you can see below, there are three categories: "No project task assigned", "Project tasks with status", "All project tasks with same status".
The first one is pretty intuitive. If you choose this, then the tool will display all Requirements which don't have any assigned project task. Then, what is the difference between the second category and the third one?
We should remember that more than one Project tasks can be assigned to one Requirement. If there are multiple number of Project tasks, then the status of each task can also vary. For this case, the second category shows you Requirements which have at least one Project task with a certain status that you choose. On the other hand, the third category filters Requirements which have all Project tasks with same status, which is, in this case, "Done". Therefore, you can see Requirements that every Project task is done.
Secondly, when you click the status bar, you can see the details of each entity by status and move to the specific page such as Feature Overview, Task Overview (Example below), Test Cases Overview, and Test Execution Overview. Of course, you can move on to the detail page of each item by clicking it as well.
Lastly, as I mentioned above, you can trace and drill down to the lower level of the entity relationship through the traceability tools. Here, you can jump into Feature Traceability tool directly as you can see below.
From this posting, you've learned when you can use a Requirement Traceability tool and what functions this tool provides. In case you have further questions, you can always search Q&A in the community or post your own question with SAP Cloud ALM tag.
Hope you found this information useful. Please visit the Expert Portal and this master blog post for more information on SAP Cloud ALM for Implementation.
Please feel free to reach out to us if you are looking for more information. We would love to hear from you!
- When you can use a Requirement Traceability tool
- What functions a Requirement Traceability tool provides
Let's get started.
1. When you can use a Requirement Traceability tool
In Analytics app, you can find Requirement Traceability tile. Next to this tile, there are Solution Process Traceability and Feature Traceability. SAP Cloud ALM for Implementation offers end-to-end traceability tools that you can track and trace Solution Processes, Requirements, and Features for your Project.
With these three traceability tools, you can drill down from the highest level to the lowest level of the entities. Since the status of each entity is maintained manually, it is crucial for the responsible person to manage and update the status according to the current situation. And these traceability tools support this action to be done in an easier and more convenient manner.
Here, we learn further details about a Requirement Traceability.
You can have a list view of the status of Requirements for a specific project, together with the status of Feature, User Story, Project Task, Test preparation, and Test Execution for each Requirement. The status of each entity is clearly and intuitively visualized with distinct colors like green, blue and red. Therefore, you can have a brief but comprehensive understanding about how the subordinate or related entities are going on and where the bottlenecks are.
2. What functions a Requirement Traceability tool provides
First, there are various filters that you can adapt to the list, so that you can see what you want only. For example, you can sort out the data by selecting a specific Scope or Solution Process or Requirement Status.
Besides, you can also set a filter for each related entity such as Feature, User Story, Project Task, Test Preparation and Test Execution. Here, what we can pay more attention to is that there are three categories for each filter. Let's see a Project Task filter as an example. As you can see below, there are three categories: "No project task assigned", "Project tasks with status", "All project tasks with same status".
The first one is pretty intuitive. If you choose this, then the tool will display all Requirements which don't have any assigned project task. Then, what is the difference between the second category and the third one?
We should remember that more than one Project tasks can be assigned to one Requirement. If there are multiple number of Project tasks, then the status of each task can also vary. For this case, the second category shows you Requirements which have at least one Project task with a certain status that you choose. On the other hand, the third category filters Requirements which have all Project tasks with same status, which is, in this case, "Done". Therefore, you can see Requirements that every Project task is done.
Secondly, when you click the status bar, you can see the details of each entity by status and move to the specific page such as Feature Overview, Task Overview (Example below), Test Cases Overview, and Test Execution Overview. Of course, you can move on to the detail page of each item by clicking it as well.
Lastly, as I mentioned above, you can trace and drill down to the lower level of the entity relationship through the traceability tools. Here, you can jump into Feature Traceability tool directly as you can see below.
3. Conclusion
From this posting, you've learned when you can use a Requirement Traceability tool and what functions this tool provides. In case you have further questions, you can always search Q&A in the community or post your own question with SAP Cloud ALM tag.
4. Next steps
Hope you found this information useful. Please visit the Expert Portal and this master blog post for more information on SAP Cloud ALM for Implementation.
Please feel free to reach out to us if you are looking for more information. We would love to hear from you!
- SAP Managed Tags:
1 Comment
