Skip to main content


WSAA Impact Analysis - New Data element depth: different from IA Level

 News
 
Abstract
WSAA Impact Analysis - New Data element depth: different from IA Level
 
Content
New Data element depth: different from IA Level
This is a configurable impact analysis improvement. Previous “versions” of WSAA have not differentiated between the depth of analysis of data elements and the level of analysis of the impact analysis in general. Going forward, this differentiation can be made, if the user wants to configure it.

By configuring the depth of impacts on data elements (instead of using IA level for the depth of data element analysis) clients can:
- differentiate between the general level of impact analysis and the depth of analysis of data elements.
- analyze data elements completely, even if the general level of IA is limited.
- not limit the general level of their impact analysis, and limit the analysis of impacted data elements
This makes it easier to explain and adjust impact analysis constraints to meet user requirements. Since this same PTF has the data caching improvement implemented, long running analyses will better handle deeper analysis of data element impact traversals. And if the user chooses to reduce impacts by configuring multiIncomingImpacts to be false, then analysis will be better suited to deal with long running analysis of deep data element traversal.

By not changing anything, clients will continue to use analysis level specified in the IA Wizard as the data element depth, as was implemented in the past. The results will be that the depth of Data Element impact traversal will continue to match the level set by the user for the IA; the max being 100 levels, when IA is "unlimited".
They will continue to get potentially incomplete analysis of high usage data elements. By continuing to use the same value for the general impact analysis level and the depth of data element analysis, impact analysis will remain consistent with previous impact analysis runs, however it will remain difficult to explain the incomplete results that may be produced.

Configurable in wsaa-impact-analysis.xml:
Parameter: DEDepthLimit: depth of data element traversal (0 indicates no limit, -1 indicates use IA level for limit, values greater than 0 indicate maximum data element impact traversal depth)
Default: -1


Do you need more help?

For additional assistance, contact IBM Rational Client Support:
Submit a Service Request (SR)

 
 
 

Copyright and trademark information

IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Rate this page

Please take a moment to complete this form to help us better serve you.

This material provides me with the information I need.






This material is clear and easy to understand.






Did the information help you to achieve your goal?

What updates, improvements, or related information would you like to see in this document?

Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.


Input the verification number to submit feedback:



Maintenance Window

Unscheduled Maintenance Window

There is no unscheduled maintenance scheduled at this time.

Document information

Product categories:

Software

Software Development

Analysis, Modeling, Design & Construction

WebSphere Studio Asset Analyzer

Analysis


Operating system(s):

AIX, OS/390, Windows, z/OS


Software version:

5.1


Software edition:

All Editions


Reference #:

1298924


IBM Group:

Software Group


Modified date:

2009-02-25

Translate my page