[oslc-rm] Minutes from bi-weekly call available

[Ian Green1]

In the normal location [1].  Next meeting is scheduled for 21 March 4pm 
GMT.

Much of the meeting was discussion of representation of hierarchical 
representations of requirements.  There was consensus around the 
following:
        - we're focussing on organizing requirements into hierarchies and 
have not considered other approaches (tagging, etc.)
        - ordering is important and this points to a weakness in the 2.0 
current resource model where ordering is not expressible
        - there is no single hierarchy
        - we recognise that it is resources which need to be organized 
(not only requirements, for example)
        - need to consider impact on providers as well as consumers

Ian took an action to refine the sample resource model (see [2]) so that 
RM resources could represent such a sample specification.

Some additional  thoughts.  This straw man allows representations of 
ordered directed graphs (graphs where the edges are ordered).  Such a 
design is flexible but offers some challenges for providers and consumers:

        - ensuring that graphs are acyclic (if this is a requirement for 
the provider) may be expensive
        - exploring the hierarchy may be awkward and chatty since it is is 
a level-oriented structure - there is no way to "GET" the graph
          in a single request, for example
        - there is no means, other than perhaps by query, to navigate 
"backwards".
        - inability to model "atomic" tree fragments (for example, a 
subsection of a specification)


[1] http://open-services.net/bin/view/Main/RmMeetings20110307
[2] 
http://open-services.net/bin/view/Main/RmRequirementsOrganizationScenarios

best wishes,
    -ian

ian.green at uk.ibm.com (Ian Green1/UK/IBM at IBMGB)
Chief Software Architect, Requirements Definition and Management
IBM Rational





Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-rm_open-services.net/attachments/20110308/8a4abf14/attachment-0003.html>