Inability of software to perform its required function.

Defect that can cause software failure.

Change made to correct a software problem.

Data type representing floating-point numbers.

Reusable block of code performing a task.

Loop commonly used for controlled iteration.

Function treated as a normal value.

Programming paradigm emphasizing functions and immutable data.

Variable stored as part of an object or class.

Creates objects without exposing creation details.

Provides a simplified interface to complex functionality.

Requirement describing what software must do.

Software running primarily in the user's interface.

Development involving both frontend and backend.

Browser API for making network requests.

Server that sends requests on behalf of clients.

Web interface element used to collect user input.

Individual data attribute in a record.

Field referencing a key in another table.

Returns records from both sides, matching where possible.

Database routine that generally returns a value.

Normalization level requiring atomic values and proper rows.

Testing required software functionality.

Working but simplified implementation used for testing.

Testing with automatically generated or unexpected inputs.

Test that inconsistently passes or fails.

Branch created for developing a feature.

Personal copy of another repository.

Downloading remote changes without integrating them.

Configuration controlling whether functionality is enabled.

Cloud model executing functions without server management.

Storage exposing files and directories.

Switching operation to a backup system after failure.

System controlling network traffic according to rules.

Investigation of digital evidence after an incident.

Data-link-layer unit containing network data.

Ability to continue operating despite component failures.