|
RootCause is a powerful and flexible tool that can be used in a
wide variety of ways, but it isn't the right tool for everyone. Read
through the questions below to see if it is likely to be a good fit for you.
Your system
-
Does your application have more than a million lines of code?
-
Are you using Java, compiled languages, and maybe JNI?
-
Does your application fit the
system requirements?
-
Are you in a post-development environment, such as integration, testing, or production?
-
Do you have to work with the system as it is, without making changes to the software?
Your position
-
Are you a senior engineer—someone everyone turns to when they need help
with the most difficult problems?
-
Is it your responsibility to get this problem fixed?
The problem you are trying to solve
-
Are you unable to get the information you need about what's happening with your application from the tools you already have?
-
Do you need to get down to the source-code level (or at least get down deeper than your current tools can)?
-
Do you believe the problem is in third-party software, but can't prove it?
-
Is the problem at a user site and you can't duplicate it (or you can't reproduce the environment)?
-
Would it be useful to be able to prototype a fix in the user's environment without changing the application code?
If you answered yes
to 5 or more of the questions, RootCause is likely to be a good
fit for you.
Take the next step
|
