System Dependency Mapping
System dependency mapping identifies and models the dependencies of system components on each other to carry out their function.
How it works
The organization collects and models architectural information about the software, hardware, and products and maps the dependencies between systems, including each system's internal components and dependencies.
- Data exchanges identified in the network mapping efforts usually indicate such dependencies, but may not be part of the intended design.
- Architectural design artifacts and SMEs may need to be consulted to determine if dependencies are intended or otherwise essential.
- System depedency mapping can identify internal dependencies of standard and pre-built systems that should be incorporated into a complete system dependency model.
- System dependencies for critical systems--those supporting critical organizational activities--should be prioritized for supply chain risk analysis.
- System dependencies should identify the integral components of a given named system and their structure to form a system.
- System dependencies with a given system may be fixed by a particular product's configuration, and leveraging external knowledge bases about dependencies available (e.g., from package managers) is essential.
The following references were used to develop the System Dependency Mapping knowledge-base article.
(Note: the consideration of references does not imply specific functionality exists in an offering.)