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
>
AMContext
>
AmImpactAnalysisDetailedScenario
(06 Apr 2011,
JimConallen
)
(raw view)
---+ OSLC Architecture Management Scenario: Impact Analysis ---++ Overview The developer is presented with a [[CmSpecificationV2#Resource_ChangeRequest?sortcol=table;table=up][change request]] or a set of change requests. These may be changes in requirements, test plans or any other external resource that can affect the integrity of the design captured in the AM service provider. The user examines the AM resources to acces the impact of the change. ---++ Pre-conditions * A requirement motivating a change request has already been processed (linked to the change request and test plan). * The AM service provider manages the archiecture resources. These existing resources have been established ( [[AMScenariosV3CRLinking][CLM Linking]]). * Individual architecture resources have various types of links to requirements, test cases, and other resources both within and outside of the AM service provider. * The change reqest(s) have links to other resources, including AM resources. ---++ Main Flow The developer starts a new impact analysis, by selecting a pre-defined/configured impact analysis type. An Impact Analysis is policy/rule driven. It can be configured to perform the analysis in different ways, following different link types and resource types. The developer associates the change request(s) with the impact analysis, and invokes it. The system starts the impact analysis, based on the rules/policies configured in the impact analysis type. The developer reads the change request, and identifies the set of requirements and resources that will change. The user requests the list of AM resources that have direct links to/from any of the resources that will change. As a general rule links between target and source are impacted. However some link types this might not be the case (i.e. owning-project). Policy/rule driven impact analysis should be configurable (specify which link types are part of impact). The impact analysis creates assessment nodes - with links. (reified statement on link, with info relevant to the impact analysis). [this is similar to the suspect links in Req Pro] ---++ Post-conditions * A document/report summarizing the impact of the potential change? * A set of assessment nodes.
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 - 06 Apr 2011 - 11:44:24 -
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