THE CORE AIM OF VOCABULARY MASTERY · SOFTWARE DEVELOPMENT VOCABULARY · REQUIREMENT → CODE → TEST → DEPLOY → MAINTAIN
Software development vocabulary is the language used to plan, build, test, release and maintain software. Terms such as requirement, repository, branch, commit, pull request, build, deployment, bug, regression and technical debt describe different parts of the development lifecycle.
The core aim of vocabulary mastery for software development vocabulary is lifecycle clarity. Learners should be able to distinguish code from product behaviour, development from deployment, testing from debugging, and feature work from maintenance. Strong software vocabulary makes teamwork easier because everyone can name the same stage, artefact or failure mode.
This page is the Software Development Vocabulary owner inside the eduKateSG Vocabulary hub. For code-level terms, use Programming Vocabulary. For wider digital terminology, use Technology Vocabulary.
Central proposition: Software development vocabulary is mastered when the learner can place each term in the lifecycle from idea to maintained product.
The 60-Second Software Development Vocabulary Router
- Planning: requirement, user story, acceptance criteria, backlog.
- Version control: repository, branch, commit, merge, pull request.
- Quality: test, bug, regression, defect, review.
- Build: dependency, package, compile, artifact, build pipeline.
- Release: deploy, release, rollback, environment, production.
- Maintenance: patch, refactor, technical debt, incident.
The Software Development Architecture
| Stage | Core terms | Core question |
|---|---|---|
| Plan | requirement, user story, acceptance criteria | What should the software do? |
| Build | code, dependency, module | How is it implemented? |
| Review | commit, pull request, code review | How are changes checked? |
| Test | test case, defect, regression | Does it behave correctly? |
| Release | build, deploy, rollback | How does it reach users? |
| Maintain | incident, patch, refactor | How is it kept healthy? |
A Worked Example: Commit vs Pull Request
A commit records a set of changes in version control. A pull request or merge request asks for a set of changes to be reviewed and integrated into another branch. One records changes; the other usually supports collaboration and review around those changes.
A Worked Example: Bug vs Regression
A bug is a defect in software behaviour. A regression is a bug in which something that previously worked stops working after a change. The second term therefore describes the history of the failure as well as the failure itself.
Deployment Is Not the Same as Release
A deployment moves software into an environment. A release makes functionality available to users or customers. Some teams deploy before releasing through feature flags or staged rollout, so the terms should not automatically be treated as synonyms.
Software Vocabulary for Collaboration
Teamwork terms such as review, handover, owner, blocker, dependency and incident help teams coordinate. These words are most useful when ownership, scope and next action are explicit.
How to Learn Software Development Vocabulary
- Map terms onto a real development lifecycle.
- Use a real repository and issue tracker.
- Compare commonly confused terms directly.
- Read build and deployment logs.
- Explain each artefact in plain language.
- Connect incidents to the stage where they occurred.
- Use vocabulary in retrospectives and project updates.
Common Software Development Vocabulary Mistakes
Calling every change a feature
Repair: distinguish feature work, bug fixes, refactoring and maintenance.
Confusing deployment and release
Repair: identify when software moved and when users gained access.
Treating test and debug as synonyms
Repair: testing detects problems; debugging investigates and fixes them.
Using technical debt as a vague complaint
Repair: identify the concrete future cost created by the current design or shortcut.
Frequently Asked Questions
What is software development vocabulary?
It is the language used to plan, code, review, test, deploy, release and maintain software.
What terms should beginners learn first?
Start with requirement, repository, branch, commit, pull request, bug, test, build, deploy and release.
What is technical debt?
It describes future maintenance or change cost created by design choices, shortcuts or deferred improvements.
What is a regression?
It is a defect where previously working behaviour breaks after a change.
How can I learn software development vocabulary?
Use real repositories, issue trackers, tests and deployments so every term connects to an artefact or action.
Where This Article Fits in the eduKateSG Vocabulary Ecosystem
- Vocabulary Hub — the broad route.
- Programming Vocabulary — code concepts.
- Technology Vocabulary — broader systems.
- Project Management Vocabulary — planning and execution.
- Professional Vocabulary — team communication.
The Software Development Vocabulary Standard
Software development vocabulary reaches its core aim when words reveal where a change sits in the lifecycle, what artefact it affects and what action comes next.
That is the standard: shared language that lets teams build and maintain software together.