With the possibilities of impact and status analysis and reports across all projects, you always keep the overview and control of the huge "W"s (Who, What, When, With what, Where, How, Why) – even in most ambitious IT environments:

While the process is being executed in SCOUT², all dependencies are registered. Thus, it is possible to display all the modules and processes that have been involved when creating an object and to check if an executed process is still current or if it has to be re-started. In addition, the effects of a module modification are analysed – which created objects are affected – Impact Analysis.

If dependencies have been registered for a dependency object during its creation, too, these dependencies are listed as a sub tree. SCOUT² provides special check, rebuild and make processes to enable this information to be evaluated easily.

• Impact Analysis – The entire development process is documented in detail. Any information about all development objects and processes are stored centrally, currently, across all projects and for all user. This information basis as well as the entire analysis and report functions are configurable and expandable, to meet your specific requirements.
• Reliable Process History – To increase the reliability of the process history and dependency analysis, SCOUT² stores the process information no longer per user, but together with the process results. Then you can see anytime in the Object List the details of all processes that affect a specific object. Not only those you executed by yourself.