dependencies

Dependencies are relationships in which one component requires another to function, be delivered, or be completed. They arise in software, where a program relies on libraries, frameworks, or external services, and in project management, where the start or finish of a task depends on others.

In software development, dependencies form a directed graph. A project may have direct dependencies and transitively depend on others through those libraries. Dependency management specifies which versions are acceptable and how conflicts are resolved. Dependency types include hard dependencies (must be present) and soft or optional dependencies; static dependencies (resolved at build time) versus dynamic dependencies (resolved at runtime or via late binding).

Managing dependencies involves versioning, pinning, and using lockfiles to ensure reproducible builds. Risks include version conflicts, brittle builds, and supply-chain issues such as vulnerable or compromised components. Dependency gravity: transitive dependencies can bloom into many components.

Common practices include using package managers (npm, pip, Maven) and OS repositories (apt, yum), pinning versions, auditing for security and licensing, and employing containerization or virtualization to isolate environments. In project planning, dependency analysis informs scheduling, risk assessment, and critical-path identification.