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
>
CmHome
>
CmScenarios
>
CmScenariosCRMassCreate
(18 Jan 2011,
SteveSpeicher
)
(raw view)
---+ Change Request mass submit This scenario will focus on creating a number of Change Requests from a requirements document. The intention is to populate a backlog from a given set of requirements in an automated way so the user is not forced to manually submit each Change Request individually. ---++ Scenario *Pre-conditions* * A requirement management (RM) repository exists * The RM repository has one or more requirements. * The requirements change management capability in the RM repository is enabled. * The RM repository is an OSLC RM 1.0 provider. * The RM repository is an OSLC CM 2.0 consumer. * A change management (CM) repository exists. * A change request type exists * The CM repository is a OSLC CM 2.0 provider * The CM repository is a OSLC RM 1.0 (2.0?) consumer with minimal set of needs (see [[#Notes_and_Todos][notes]]) * Cross-server communication is established between the RM and CM repositories *Post-conditions* * One Change Request is created for each Requirement * An ImplementedBy traceability link is created from the Requirement to the corresponding Change Request * An ImplementsRequirement traceability link is created from the Change Request to the corresponding Requirement. *Steps* <blockquote> *(Step 1) Administrator: Configure field mappings 1 In the requirements management repository, designate which Requirement fields will be used to fill values for Change Request fields during creation. For example, the Requirement text field will be used to fill in the description of the Change Request upon creation and the Requirement priority will be used to fill in the priority. *(Step 2) Requirement Engineer: Submit Change Requests 1 Open the Requirement(s) 1 Choose to submit a Change Request for each selected requirement *(Step 3) Requirement Engineer: Enter values for required fields 1 Provide a value for each field required by the change management repository to create a Change Request that was not already mapped in step 1. This action will only be done one time for the entire set of requirements and the values entered will be used for each Change Request created. </blockquote> ---++ Resources * *Requirement* * The requirement management tool is the _consumer_ of the CM 2.0 specification. The CM 2.0 spec do not declare a requirements resource type, but depend on the RM specification for such resource definitions. * *Change Request* * The change request, specified in CM 1.0 spec, is the resource used by the requirement to delegate/manage/govern its change management workflow. * The change management tool is the _provider_ of the CM 2.0 specification. * The change request will persist a URI to the requirement, to enable the delegated UI to browse and display requirements. -- Main.BrianSteele - 13 Jan 2011
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 18 Jan 2011 - 15:28:24 -
SteveSpeicher
Main.CmScenariosCRMassCreate moved from Main.CmScenariosBacklogPopulation on 18 Jan 2011 - 15:28 by
SteveSpeicher
-
put it back
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