The process of identifying and visualizing relationships between different components, systems, or tasks. It shows what depends on what and helps identify potential bottlenecks or failure points.
From Latin 'dependere' (to hang from) and 'mappa' (cloth, map). The practice formalized in systems engineering during the 1960s and became crucial in software architecture planning.
Dependency mapping is like creating a family tree for your technology - you discover that your simple app actually relies on 47 different services! The scary part is that most companies don't realize how complex their dependencies are until something breaks.
Complete word intelligence in one call. Free tier — 50 lookups/day.