Application dependency mapping: every connection, clickable
See how every program, job, proc, copybook, table and file connects, upstream and downstream, in an interactive, color-coded map. Refactor with confidence, find redundant code and plan modernization from the real architecture.
What is application dependency mapping (ADM)?
Application dependency mapping (ADM) gives a clear, detailed view of code dependencies that helps developers understand the relationships between the components of a system.
Developers can refactor with confidence, knowing how a modification will affect the system, which leads to more efficient and safer updates. A shared visual representation of the architecture improves collaboration, complements written documentation and helps new team members get up to speed.
By highlighting dependencies, developers can find and remove redundant or deprecated code. ADM also supports risk management by pinpointing critical dependencies that would be risky to change, so mitigation can be planned in advance.
Without SMART TS XL
- Architecture diagrams drawn once and never updated
- Hidden callers found after a change goes live
- Redundant code nobody dares remove
- Modernization plans built on assumptions
With SMART TS XL
- Maps generated from the code, always current
- Every caller and every use shown before you change anything
- Dead and deprecated code highlighted
- Waves planned from real interconnections
Dependency mapping solutions by SMART TS XL
Interactive, color-coded maps
Programs, modules, jobs and data shown in the colors of their type, with hyperlinks between them.
Upstream and downstream
See what calls an element and what it calls or uses, level by level, and where the impact zones are.
Accurate impact analysis
Predict how a change in one part of the code affects the rest of the system.
Detect issues early
Find risky dependencies early to reduce bugs and errors.
Built for modernization
Plan and execute updates from a clear view of how the existing codebase connects.
A shared picture
One visual reference for developers, architects and new team members.
Build a dependency map in seconds
Choose an element
A program, job, proc, copybook, table or file.
FOJOT405Map it
Callers on one side, what it calls and uses on the other.
3 up · 4 downExpand
Open more levels until you reach the edges of the system.
Level 2 · level 3Act
Export the map, run impact analysis or plan a wave.
Report · wave planDependency Mapping, in plain English
Everything on this page also works as a question. Ask ASK AI inside SMART TS XL, or the assistant your team already uses through the MCP Connector. It calls SMART TS XL, reads the indexed code and answers with the source behind every fact. Read-only, under the same permissions your people have.
What calls FOJOT405, and what does it call?
FOJOT405 is run by job PAYR0100 through proc BUIR005. It calls ZAQXAPEM, reads DAILY.TRANS, includes copybook CLMREC and updates DB2 table INV_PAYMENT.
- 3 upstream
- 4 downstream
- 1 DB2 table
ILLUSTRATIVE QUESTIONS AND RESULTS
Why dependency maps matter
Detect potential issues early
With SMART TS XL identifying dependencies, you get accurate impact analysis that predicts how a change in one part of the code affects the rest of the system, reducing bugs and errors.
Crucial for legacy modernization
Dependency maps are essential for legacy system modernization. SMART TS XL shows the interconnections within the existing codebase so updates can be planned and executed safely.
Living documentation
A visual reference that complements written documentation, generated from the code, so it never goes stale.
Easier maintenance
With a clear understanding of dependencies, maintaining and updating code becomes more straightforward and less error-prone.
Proven on 5.7 billion lines of code
Questions about dependency mapping
Which elements appear on the map?
Programs, jobs, procs, parms, copybooks, DB2 and other database tables, VSAM and flat files, CICS transactions, and distributed code such as Java and .NET, each in its own color.
Is the map built by scanning running systems?
No. It is built from the indexed source and definitions, so it shows the dependencies written in the code, including paths that rarely run.
Can an AI assistant read the dependency map?
Yes. Through the MCP Connector, an assistant can run the same cross-reference reports and explain the dependencies in plain English.
See dependency mapping on your own code.
In a live session we load a sample of your portfolio and run dependency mapping in the web interface and through the AI assistant you already use.
New to SMART TS XL? See how the platform fits together →

