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
>
AmHome
>
AMScenariosV2
(30 Sep 2010,
JimConallen
)
(raw view)
---+ Discussion Document: OSLC AM 3.0 Scenarios This document is a working document for the workgroup to use to dicusss what scenarios we need to support for the post 2.0 spec. Supported Scenarios: ---++ *Goal*: Support the ability to associate/link change requests to change sets instead of directly to resources. *Prerequisites*: * AM repository with history enabled (change tracking) * AM system with a connection to a CM system * Multiple change requests created in the CM system that will require modification of the same resource(s) in the AM repository * Each change request assigned to a user, could be the same user or different users, the scenario uses different users *Outcomes*: * Change request 1 linked to a change set in the AM repository * Change request 2 linked to a change set in the AM repository * Given a change request find the change set(s) and all Resource(s) affected in the AM repository * Given a resource find all change request(s) that affect the resource in the AM repository <strong>Scenario<br /><br /></strong> * User1 establishes a context in the AM tool 1 User 1 opens existing AM repository - Proj1/Wksp1 1 User 1 selects an existing change request - CR1 from a list of assigned requests retrieved from the CM system 1 All changes made will now be tracked and related to the active change request CR1 * User1 assesses the scope of the change request 1 Locate AM resource(s) Res1 impacted by the request - CR1 * User1 Applies required changes 1 Open AM resource - Res1 and make required changes (Res1 is locked while being modified) 1 Save AM resource - Res1 1 Change set created and association with the active change request - CR1 is established 1 Resource Res1 is unlocked * User2 establishes a context in the AM tool 1 User 2 opens existing AM repository - Proj1/Wksp1 1 User 2 selects an existing change request - CR2 from a list of assigned requests retrieved from the CM system 1 All changes made will now be tracked and related to the active change request CR2 * User2 Assesses scope of Change Request 1 Locate AM resource(s) impacted by the request- Res1 * User2 Applies required changes 1 Open AM resource - Res1 and make required changes (Res1 is locked while being modified) 1 Save AM resource - Res1 1 Change set created and association with the active change request - CR2 is established 1 Resource Res1 is unlocked * User3 reviews the changes for each change request 1 Opens existing AM repository - Proj1/Wksp1 1 Selects CR1 and is able to view a list of the changes made to Res1 on behalf of CR1 1 Selects CR2 and is able to view a list of the changes made to Res1 on behalf of CR2 ---++ *Goal*: In architecture artifacts (object x) an architect (role) would create a link from a high-level design object (object y), such as a data controller component, to a high-level testing artifact (object z), such as a test plan.
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r6
<
r5
<
r4
<
r3
<
r2
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r6 - 30 Sep 2010 - 13:42:47 -
JimConallen
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