...
| Info | ||
|---|---|---|
| ||
In this article we explain how to use Requirement Yogi to refine specifications from high-level business requirements to low-level technical specifications. |
It all starts when you refine the high-level requirements...
...
- The technical requirements cover only 2 of your 3 functional requirements.
- All of the 3 functional requirements cover a business requirement.
- You can obviously click and see the items for each list.
- Since you want to complete the coverage, you can list all requirements which are missing a link.
For navigation purpose, we display the dependencies in the inline popup:
...
| Info | ||
|---|---|---|
| ||
The Coverage and Dependencies tabs are only displayed to users with the "Export Space" permission. It is due to the important memory consumption of such reports. The explanations are at the bottom of this page. |
Much better Excel export
Taking the opportunity of exporting the Dependency Matrix to Excel, we've also greatly extended the Excel export. It now exports in the native .xlsx format, so we use 2 sheets, frozen panes and hyperlinks.
Other screenshots
We add some new keywords for the search: "TO" and "FROM". Like the "JIRA" keyword, it allows you to search all requirements linked to and from another requirement, and you can specify the property name (i.e. "TO@implements" or "FROM@refines").
In the following screenshots, we show how dependencies appear in the search, how the coverage looks when there are several relationships, and how to configure an RY Property macro for a column that contains dependencies.
Technical Notes - Out of Memory Errors
...
We know that memory, processing power and database throughput are limited on your servers and we're very conscious of the cost of investigating out-of-memory errors. We've already made some efforts to measure, optimize and contain problems. We've also met boundaries because of the ActiveObjects API (the storage in AO_32F7CE tables), the SiteMesh decoration (which Confluence uses to add the top bar and footer in the HTML pages), and the Excel API. We believe we've done our best and we believe memory consumption will be the most reasonable in the most number of cases. If you meet problems and have further suggestions on how to optimize, we're available.