Re: Organizing/prioritizing requirements ... via a tag filter

Jaro - yes, that sounds useful, if it can be done. We had noted that the
requirements themselves were not tagged so we did not have an easy way
to gather them by deliverable. Could you demonstrate what you describe
below for the group?

Thanks,
kc

On 9/1/17 2:49 AM, Jaroslav Pullmann wrote:
> 
>  Dear Karen, dear all,
>  
>> determine the requirements for the three deliverables
> 
>  couldn't we use the tags to filter accordingly?
> 
>  There are 3 deliverable tags (content_negotiation, dcat, profile)
>  with every use case tagged with at least one of them.
> 
>  The spec reader might create a view filtered by deliverable and further
> tags.
>  Only matching use cases and their related requirements were visible:
> Tag > UC > Req.
> 
>  Does this simple approach fit the task or are there exceptions, where e.g.
>  requirements are relevant for a deliverable while none of the related
> UCs does?
> 
>   Best regards
>  Jaroslav
>  
>  
>> Some possible organizing principles are:
>>
>> - which requirements are for which deliverables? (Yes, some requirements
>> may be valid for more than one deliverable.)
>> - what are the logical categories that requirements fall into within
>> each deliverable?
>> - what is the priority for each requirement? (e.g. absolutely required;
>> required if possible; nice to have but not required)
>>
>> Following are some examples from previous working groups that the team
>> is aware of. If you know of others please reply with them.
>>
>> - https://www.w3.org/TR/dwbp/#challenges (DWBP challenges)
>> - https://www.w3.org/TR/dwbp/#requirements (DWBP requirements)
>> - https://www.w3.org/TR/shacl-ucr/#requirements (SHACL requirements)
>>
>> Please give some time to this and share an ideas with the group.
>>
>> kc for the team
>>
> 

-- 
Karen Coyle
kcoyle@kcoyle.net http://kcoyle.net
m: 1-510-435-8234 (Signal)
skype: kcoylenet/+1-510-984-3600

Received on Saturday, 2 September 2017 17:18:34 UTC