Baselines

Overview

A baseline represents the state of a set of requirements at a specific point in time. A baseline might represent a project milestone, such as an important review or a new release. Baselines are used to identify changes in a set of requirements.

Baselines can be created at any level of a project hierarchy. A baseline contains the state of each requirement, including child requirements, starting from the selected folder and extending through all folders in that hierarchy. The state of an issue consists of the values of the fields included in the R4J Detail View at the time the baseline is created.

Thanks to Requirements Reuse, baselines may contain requirements from different projects.

Usage

Purpose

How to invoke

Purpose

How to invoke

Create baseline

Right click the desired folder for the baseline in the project tree view, select Create Baseline, enter the name and description of the new baseline and select Create.

If a tree filter is in effect when a baseline is created, the resulting baseline only contains the items matching the filter.

View all baselines

Select Requirements > View All Baselines from the R4J dropdown. The resulting table lists the baselines in all R4J projects. The table can be filtered and reordered by column.

View baselines in a project

Select Baselines in the project tree view. The resulting table of baselines can be filtered and reordered by column.

Compare baselines

In the list of baselines, select the two baselines you wish to compare and select Compare selected baselines. Baselines from different projects can be compared.

In general, comparing baselines in different projects is not useful, since the two sets of items do not overlap. However, if you are practicing Requirements Reuse, comparing baselines in different projects can be valuable. For example, suppose you have a “catalog” project, consisting of standard requirements. A new project starts by including all the requirements in the catalog. A comparison of baselines in the two projects would now show no differences. As the project progresses, it replaces standard requirements with project-specific copies when the needs of the project diverge from the standard. A comparison of baselines in the two projects would now display exactly those copies and hence show how the project has diverged from the standard catalog.

View baseline details

In the list of baselines, select a baseline to open the Baseline Details. The buttons above the details allow you to perform the following actions:

  • Select the fields to be displayed.

  • Expand or collapse the details of the contents of a baseline.

  • Export the content of a baseline to XML or Excel.

  • Add a signature to a baseline. See Baseline Signatures.

Edit baseline name and description

In the list of baselines, select the edit icon.

Delete baseline

In the list of baselines, select the delete icon.

A comparison of two baselines lists every requirement that is in at least one of the baselines. In the case of requirements that exist in both baselines, the values of the fields in each revision are displayed side by side. Fields with different values in the baselines are highlighted. In the case of requirements that exist in only one baseline, all fields in the revision are highlighted. An indication that the requirement is missing in the other baseline is displayed.

The fields displayed in the comparison can be changed by selecting Display Fields and selecting or deselecting fields in the list.

The following quick filters are provided:

Only Changed Issues

Only requirements that are contained in both baselines and have different values for at least one field are listed.

Only the fields included in the list of displayed fields are taken into consideration when determining if a requirement has changed. That is, if the value of a field is different, but the field is not included in the current setting of Display Fields, the requirement is not regarded as being changed.

Only on Left Side

Only issues that are contained exclusively in the left baseline are displayed.

Only on Right Side

Only issues that are contained exclusively in the right baseline are displayed.

Baseline Signatures

Baselines can be electronically signed. For example, a project may require that the members of its Change Control Board review the baselines of important milestones. Baselines are provided to the members via links. Each member is expected to sign off with a digital signature and mandatory free text comment (e.g. approved, rejected).

Once a signature has been submitted it cannot be changed or revoked.