Hi Thomas,
> does the requirements tree appear now as you wanted it to appear?
I think I would have liked to fold them by clicking on them, but well, it's already much better like this!
>
> Now, if you edit requirements, the selection of associated requirements classes is displayed at the end of the editor.
> Does this satisfy your requirement?
Yes.
>
> When you edit requirements you see now a select list for associations with use cases and not a list of check boxes.
> You can select multiple use cases in order to relate requirements to use cases.
> The same appears now for the requirements classification.
Well actually the fact of having them in one small box (4 lines) would almost allow to put them back on top, with the use cases and requirement coverage.
Btw I don't get why the allowed values for that choice menu are other requirements.
>
> Related to your comment during the discussion.
> If you have a requirement in mind and you are not sure if it is already contained in the requirements db, just create an new requirement.
> I can look if there is already a requirement in the db with the same semantics in order to delete duplicates.
Great!
I'd expect that you mail us before deleting duplicates. This would probably be very useful for the person who created the requirements, and for the others, who could also see what's happening during requirement elicitation.
Cheers,
Antoine
>
> -----Ursprüngliche Nachricht-----
> Von: DCMI Architecture Forum [mailto:[log in to unmask]] Im Auftrag von Antoine Isaac
> Gesendet: Dienstag, 8. Juli 2014 18:02
> An: [log in to unmask]
> Betreff: Feedback DB validation requirements
>
> Dear all,
>
> Following the discussion in today's call on
> http://purl.org/net/rdf-validation
>
> I had extra comments:
>
> - the left menu with the requirement 'tree' is hard to follow. Is there a way in Drupal to make the branches (un)fold upon a click, not a mouse-over?
>
> - the number of classes for requirements really high. As such in the edition form, it's really standing between the editor and the most important stuff (the description of the requirement). Is it possible to put the requirement classification part at the end of the edition template? And to remove some of the tickboxes?
>
> Best,
>
> Antoine
>
|