This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
RmHome
>
RmScenarios
>
RmCALMReviews
(06 Jul 2009,
IanGreen
)
(raw view)
---++++ RM workgroup C/ALM review comments Please add your review comments on the C/ALM scenarios here. Dominic Tulley: I think it is a weakness of the approach here that the scenarios that "join" RM to other areas are not shared with the other areas. So their scenario for joining with RM may not align well with what we come up with here. --- -- Main.RainerE - 29 Jun 2009 comment to Scenario 2 * the expression "Change Request" should be replaced by the expression "Implementation Request" * the scenario does not explain where this Change Request comes from, except "interested parties". <br />From my point of view, it is vital for the OSLC definition, how you communicate with the interested parties<br />e.g. verbal, by e-mail, or via an other "system" like a help desk or customer support center --- -- Randy Vogel - 01 Jul 2009 Overall comments on Scenarios: * What about requirements prioritization and release scoping as a scenario? * Should the scenarios distinguish between traditional and Agile development approaches? Comments on Scenario A: * As discussed during the workgroup call, we should find a better name for "change request". My suggestion would be to use work item which will tie nicely with the ALM work. * For step 2, have we considered a variation for the test plan to be automatically created? * We should consider creation of design documents similar to the test plan. These documents will be created and linked to the requirements for traceability. * The scenario should have an end step "Requirement is marked as complete/delivered". Comments on Scenario B: * In step 2, it's probably more likely that a requirement will be updated rather than created to reflect the change request. This could get interesting to provide an automated way to create the linkage. Comments on Scenario C: * Step 3 could also have as a sub-step "Code is implemented" to reflect that a requirement hasn't been implemented. -- Main.IanGreen - 06 Jul 2009 * What is a "requirement set" - Is "requirement collection" a better term, in the context of these scenarios. * Consider Brenda's ammendments to Scenario B, which can be found [[ChangeRequestScenario2][here]]. * Impact on specification needs induced by RCR?
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r5 - 06 Jul 2009 - 12:15:07 -
IanGreen
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback