Use Case:
How Discoverer can change impact analysis

The Problem

System with way too many connections nobody can make sense of.

A situation many companies face – as their homegrown system architecture grows, the complexity of such system increases. And because speed trumps the correct process every time, the documentation often falls behind. In the end, there is a system of countless databases, flat files, and transactions, all combined across many applications, jobs, functions and processes. Without anyone knowing how exactly are they connected.

The Challenge

Making changes and/or integrating new systems into the current environment.

At this stage, pulling a report or obtaining information on what is influenced by what
is almost impossible. Doing it manually is difficult, time consuming and inaccurate.

The Solution

Discoverer presents one coherent environment that enables the visualization of all dependencies. You just load in the respective data, process it and see all existing real or embedded relations.

Discoverer enables visibility through the following functionalities.

• RESOURCES – objects, entities, databases, files
• TECHNOLOGIES – schedulers, programs, jobs,
• STATISTICS – graphs, code lines, dashboards
• DEPENDENCIES – relations, statistics, dependencies,
  analytical capabilities, dead code analytics
• USAGE – MSU, database, file, FTP, mainframe screens,
  file access, FTP access, web page access,
• DEAD AND ZOMBIE CODE ANALYTICS
• EXPORTER – Archi, CSV, XML, XLS
• EXTERNAL TOOLS – access to an internal graph
  database, full-text search capabilities, BI/reporting

Mobile access shows the data loaded in real time to managers, architects, analysts and support teams. They are thus able to follow the structures and references of the embedded objects. The exact analytical and statistical information is handy any time, even while in a meeting. No need to waste time gathering requirements or keep a requestor
waiting.

Assessing the size and impact of any change is quick and easy, ready to be used during an agreement and assessment of compacity or while preparing the solution for an end customer, even during the requirement gathering phase.

The application is web-based, running on any device with standard web and mobile widgets displaying Discoverer’s analytical data in easy-to-read charts.

The resulting charts combine data from multiple applications and data sources to display year-over-year changes and comparisons – a view that before Discoverer’s arrival did not exist across multiple platforms or toolsets as a standalone screen.

Once one or more projects or programs are optimized, the same algorithm enables an X Language application that does not require any changes to the underlying environment. Therefore the risk of overlooking mandatory dependencies is minimized. And so is the time needed for change impact analysis.

The Result