A branch is a separate line of development that starts from a defined configuration or version.
It allows teams to change work products without affecting the main line. For example, one branch may contain bug fixes. Meanwhile, another branch may contain new features.
In requirements engineering, it can hold a separate set of requirement versions. Therefore, teams can develop releases or variants in parallel. Later, they may merge the changes into the main line.
However, parallel versions increase complexity. They can create conflicts, duplicate information, and unclear identifiers. Consequently, teams need clear versioning, traceability, and change control.
Careful branch management supports parallel development while protecting consistency and release stability.
« Back to Glossary Index