...
Requirement Yogi allows you to add, edit and track requirement data without disturbing the viewers or the author of the original page. External properties are not visible on the original page but you can see them in the traceability matrix or when you click on the requirement popup. External properties are also exportable to Excel with the traceability matrix.
External Properties have types:
...
Decimal and Integer types allow the creation of aggregations in the traceability matrix: sum, min, max, count, and average.
Examples of use cases:
Estimate the total man hours of a parent requirement.
- Create an integer or decimal external property in your space (eg: "Man hours", or "Story points")
Use the tracability matrix to estimate the time investment for each requirement (Filter your traceabilty matrix with the search query: "to = '<ParentRequirementKey>' " to estimate cost of a parent requirement)
Use the edit toggle to quickly assign a cost to each requirement
- Use the SUM aggregator to calculate the total time cost.
Track the approval state of a requirement
We currently don't have an Enum type that would only allow a few values, so you will need to make use of the text type, and make sure to have the correct values (Beware capitalization and trailing spaces!). We plan to add this Enum type in the future.
- Create a text external property (eg: "Approval State")
- Add this property to the relevant requirements you want to track. We suggest having a set of possible values (eg: "Draft", "Ready for review", "Approved") and limit yourself to those.
Use the COUNT aggregator to count the requirements: COUNT(ext@<PropertyName>, criteria). (Eg: COUNT(ext@Approval\ State, ext@Approval\ State = 'Ready for review") )
Managing External Properties
...