Closed Malvoz closed 3 years ago
The MapML Proposal has a similar section that should reflect any such changes.
IMO this section should reference the UCR MapML Fullfillment Matrix, I was thinking something along the lines of
Looks good to me.
But in this case, is linking evaluated to the evaluation issues redundant? Although it encourages others to engage in the evaluation, I'm not sure it's really all that useful.
I have found that when discussing the feature requirements, it can be quite surprising what is and is not a shared understanding, so I thought and think it might be useful to have a place for discussion. In fact if it's not obvious that a requirement is fulfilled by an example, it should be possible to link to that discussion from the UCR Fulfillment matrix and/or the example itself to find out the why's and the wherefores of requirements undershoot.
The Use Cases and Requirements section currently states:
IMO this section should reference the UCR MapML Fullfillment Matrix, I was thinking something along the lines of (improvements are welcome, of course):
But in this case, is linking evaluation issues redundant? Although it encourages others to engage in the evaluation, I'm not sure it's really all that useful.
to the