C++ method called when an object is destroyed.

Ambiguity caused by multiple inheritance paths.

Type-safe reference to a method in C#.

Technique widely used in .NET application architecture.

Architecture whose components operate across multiple machines.

Business area represented by a software system.

Software representation of business concepts and rules.

Design approach centered around business domains.

Service containing domain logic not naturally belonging to an entity.

Architectural rule controlling dependency direction.

Graph showing dependencies between components.

Transaction involving multiple independent resources.

Lock shared among multiple system instances.

Accumulated cost from poor design decisions.

People responsible for creating the product increment.

Short daily team coordination meeting.

Shared criteria determining whether work is complete.

Criteria indicating work is sufficiently prepared.

Collaboration and automation between development and operations.

DevOps practices incorporating security throughout development.

External work or component required for progress.

Phase defining software structure and behavior.

Phase delivering software to users or production.

Connecting application data with interface elements.

Repository describing data elements and their properties.

Structured representation of data and relationships.

Automated flow that moves and transforms data.

Converting data into a storable or transferable format.

Organized method of storing and accessing data.

Organized collection of electronically stored data.

Structure improving speed of database searches.

Moving or modifying data/database structure between versions or systems.

Formal structure describing database organization.

System designed for analytical storage of large datasets.

Situation where processes wait indefinitely for each other.

Tool for inspecting and controlling program execution.

Finding and fixing software defects.