Requirements Branches

Why Use Branches?

Branches are helpful when you want to change requirements for new features or update existing ones without affecting the current requirements that are being used for development and testing.

Types of Branches in Almware

Almware offers two types of branches for different needs:

Partial Copy Branches

This type lets you select and work with only the specific artifacts you need. For example, if you want to make a small change that doesn’t impact other requirements, you can create a branch for just those specific artifacts. When finished, you can merge your changes back into the main set of requirements.

Baseline Branches

Baseline is used to capture the complete set of requirements (including specifications) in the current state. For example, when you have completed the current version and want to save the state of the requirements artefacts for history and comparison later.

Key Features for Using Branches

Switching Branches

You can change branches using the switcher in the top right corner. By default, you’ll see artifacts from the baseline. While working in branches, you can use the same search and navigation tools as in the baseline, except for tools related to planning (e.g. requirements status view), which are only available for current baseline requirements.

Managing Branches

You can create new branches from the artifact browser or the branch management section. All created branches can be found in the Requirements - Branches section. The branch management section shows which artifacts are in a branch and any differences from the baseline.

Merging Branches into the Baseline

You can merge a branch back into the baseline, which updates the baseline with the branch’s changes and creates new versions of the baseline artifacts.