Tables as Requirement Artifact type
We are documenting requirements for a system where multiple customers in involved. There are some specific requirements for each customer. For example, If the business rule for one customer is Maximum payment amount can be made is $100. The same business rule for other customer is Maximum Payment amount can be $50. In order to document this in better way we wanted to add a table to indicate the customer and the respective business rules. See the sample table below.
|
Customer |
Maximum payment amount allowed |
|
Customer 1 |
$100 |
|
Customer 2 |
$50 |
|
Customer 3 |
$500 |
Please suggest what is the best way to create the table as reusable component which can be inserted by business analysts in the requirement documents and modify the details in it.
Accepted answer
One way is to create a business rule artifact called "Maximum payment amount" than contains just the table and then either embed or link to this business rule where it is used in other artifacts.
With embed you can control whether the full artifact is shown or just its name and it can be toggled as necessary.
Alternatively you can use modules where the business rule is included and has attribute values for each customer, in each module.
With embed you can control whether the full artifact is shown or just its name and it can be toggled as necessary.
Alternatively you can use modules where the business rule is included and has attribute values for each customer, in each module.
