External component required by software.

Supplying required dependencies to an object externally.

Managing libraries and components required by software.

Installing and making software available for use.

Automated workflow for building, testing, and releasing software.

Marking functionality as obsolete or discouraged for future use.

Reusable solution template for common software design problems.

Practices combining development and operations collaboration and automation.

System whose components operate across multiple computers.

Platform for building and running containers.

Representation of concepts and relationships in a problem domain.

Design approach centered on business domain concepts.

Software enabling an operating system to communicate with hardware.

Resolving method or function behavior at runtime.

Determining variable types during program execution.

Layer responsible for accessing stored data.

Object encapsulating database access operations.

Expression connecting data to an interface or component.

Definition of data structure exchanged between systems.

Accuracy and consistency of stored data.

Large repository storing raw data in various formats.

Establishing correspondence between fields or data structures.

Discovering useful patterns in large datasets.

Structuring data to reduce redundancy and anomalies.

Maintaining copies of data across systems.

Checking data against defined rules.

Communication link between software and a database.

Software enabling applications to communicate with databases.

Group of database operations treated as one unit.

Code that is never executed or needed.

Graph showing relationships between software dependencies.

File recording exact dependency versions.

Isolated environment used for deploying application versions.

Document describing software architecture or design.

Cache shared across multiple application instances.

Database distributed across multiple machines or locations.

Tracking requests across multiple distributed services.