DATA CENTER AND SERVER | CLOUD
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 easeRequirements Detail View at the time the baseline is created.
Due to Requirements Reuse, baselines may contain requirements from different projects.
Operations
Purpose | Action |
|---|---|
Create baseline |
If a tree filter is in effect when a baseline is created, the resulting baseline only contains the items matching the filter. The selected components and fix versions (if any) are used to classify the baseline and have nothing to do with the issues. They are not used to filter the issues for the creation of the baseline. |
View baselines in a project |
|
View all baselines of all accessible projects |
|
View baseline details |
The following options to configure the display are available in the easeRequirements menu bar:
Data center The last two icons are named “Baseline View” and “Tree View”. Viewing a baseline in tree form shows you the structure of the requirements when the baseline was created. The following display options are available in buttons above the comparison table:
Additional buttons provide the following actions:
|
Compare baselines |
Data center The button is named Compare Selected Baselines. The following options to configure the display are available in the easeRequirements menu bar:
Data center The last two icons are named Tree View and Baseline View. Viewing a baseline in tree form shows you the structure of the requirements when the baseline was created. The following options are available in buttons above the comparison table:
|
Data center (ULTIMATE) |
|
Edit baseline details |
|
Delete baseline |
|
Baseline Signatures
Electronic signatures are integrated in the baseline approval process. For example, projects may require Change Control Board members to review baselines associated with key milestones. These baselines are distributed to members via links, each member providing a digital signature (using verification by email), mandatory free-text role (e.g. “Approver”), and comment (e.g. "approved" or "rejected").
DATACENTER User has to confirm his credentials via the password.
CLOUD User needs to request a code via email.
Once a signature has been submitted it cannot be changed or revoked.