Understanding the vocabulary of software development is essential for any professional working in a tech-adjacent role.

Software Development Vocabulary

Software Development Life Cycle. The process used by teams to design, develop, and test high-quality software.

A methodology that focuses on iterative development, where requirements and solutions evolve through collaboration.

A specific framework within Agile that uses fixed-length iterations called sprints to manage complex software builds.

A set period (usually two to four weeks) during which specific work must be completed and made ready for review.

A prioritized list of features, bug fixes, and infrastructure work that the team needs to address.

Minimum Viable Product. A version of a product with just enough features to satisfy early customers and provide feedback for future development.

The implied cost of additional rework caused by choosing an easy or quick solution now instead of a better approach that would take longer.

The excessive expansion or addition of new features in a product, often leading to delays and over-complication.

A set of practices that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle.

Continuous Integration and Continuous Deployment. A method to frequently deliver apps to customers by introducing automation into the stages of app development.

Application Programming Interface. A set of rules that allow different software entities to communicate with each other.

The part of a software system that the user interacts with directly (the user interface).

The part of the software that handles data processing, server logic, and database management; invisible to the user.

Refers to a developer or technology that covers both the frontend and backend portions of an application.

Quality Assurance. The process of testing software to ensure it meets requirements and is free of defects.

The process of restructuring existing computer code without changing its external behavior to improve non-functional attributes.

The measure of a system's ability to handle a growing amount of work by adding resources.

An old method, technology, or computer system that is still in use but may be inefficient compared to current standards.

An architectural style that structures an application as a collection of small, independent services.

Often called a "repo." A central location where data (specifically source code) is stored and managed.

A system that records changes to a file or set of files over time so that you can recall specific versions later (e.g., Git).

A tier of IT infrastructure where software is run. Common types include Development (Dev), Staging, and Production (Prod).

The process of making a software system or update available for use.

User Acceptance Testing. The final phase of testing where actual users test the software to see if it handles required tasks in real-world scenarios.

A document that outlines the technical requirements, design, and architecture for a piece of software.