[oslc-rm] Minutes from last meeting available

[Dong Bing Li]

Hi Ian and All,

Some quick thoughts:

* where does the "new feature" come from? we regard it as a requirement
from customer?
If so, should we add 1 more step before #1 step:
0. Rebecca go thru new requirements from customers and raise a new
Stackholder Needs to the team. And assign a new task to Bob (which is #1)
to analyze the Stackholder Needs.

* should Bob regard Rebecca's new feature as Top level Requirement or as
Collection?
The reason I'm doubting with Collection approach is: Collection is kind of
an unordered group, you don't know which requirement in the collection is
the one root cause. It might lost the original information from the
request. i.e. for test, the original request is like a best User Acceptant
test. But with the collection, it is very hard to identify which
requirements are candidate for the User Acceptance test.
So, I'm wondering should we use a requirement to represent the original
request, and associate with the new created Collection as elaboratedBy?

* will Review be an OSLC resource?
In the whole process, review takes an important job to trigger the left
processes and actions. And I had heard form several system customers, that
they have very tight review process for requirement management. Do we want
to add this to RM spec?

* are we expecting to establish a scenario that's cover the basic
end-to-end lifecycle, or we only focus on the interaction for each domain
with RM?
In either case, I'd love to volunteer myself for QM, thanks =).


****************************************************
Scarlett Li
Rational Quality Manager Development, IBM CDL
Tel:(8610) 8245-3764
3/F Ring Building, 28 Zhongguancun Software Park
No.8 Dongbeiwang West Road Haidian District Bejing P.R. China 100193
****************************************************
"After all, tomorrow is another day."



From:	Ian Green1 <ian.green at uk.ibm.com>
To:	oslc-rm at open-services.net
Date:	2013-04-24 00:02
Subject:	[oslc-rm] Minutes from last meeting available
Sent by:	"Oslc-Rm" <oslc-rm-bounces at open-services.net>



Hello there,
Minutes from last meeting available at [1].

During the meeting we went through the RmGenericAppDevScenario at [2].  The
motivation for this was to better understand the resources involved in this
"basic" scenario.

We took actions to review this scenario offline and to feedback on this
list and suggestions or changes.   I'd like to encourage stakeholders to
contribute to this effort.

In particular, we want to decorate the scenario with the types of resources
involved (for example, Requirements and RequirementCollections, TestCases,
designs etc.), and the types of links that might exist between them.  We
might arrive at a picture similar to the one the Jazz folks created at [3],
but (hopefully) somewhat simpler.

We're doing this so that we can more clearly see the structure in these
relationships.

I took the action to document the OSLC RM resources and the link types
involved, Jim for AM, and Clyde took an action to update a gap in the
scenario.

[1]
http://open-services.net/wiki/requirements-management/meeting-17-4-2013/
[2]
http://open-services.net/wiki/requirements-management/RmGenericAppDevScenario/

[3] https://jazz.net/wiki/bin/view/Main/CALM2010LinkTypes

best wishes,
   -ian

ian.green at uk.ibm.com (Ian Green1/UK/IBM at IBMGB)
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
_______________________________________________
Oslc-Rm mailing list
Oslc-Rm at open-services.net
http://open-services.net/mailman/listinfo/oslc-rm_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-rm_open-services.net/attachments/20130424/bd1450cf/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-rm_open-services.net/attachments/20130424/bd1450cf/attachment.gif>