Getting started

Getting started

Overview

easeRequirements for Azure DevOps allows you to manage your requirements in a tree structure, review them in document or tabular format, analyze the dependencies and links between them and create snapshots (baselines) of the requirements at a particular moment. easeRequirements is seamlessly integrated in Azure DevOps. This page explains how to quickly get started with easeRequirements for Azure DevOps.

The installation and configuration described in this page can only be done by users with administration permissions.

Installation

An administrator can install the easeRequirements for Azure DevOps extension through the Azure Marketplace.

Navigation in easeRequirements

You access easeRequirements for Azure DevOps from the Boards menu:

easeReq-for-AzDO-main-screen.png

Components of easeRequirements

The Requirements Tree allows you to create, manage, read, and export your project requirements. In the middle section, you can use the tree to navigate and organize requirements. On the right side, you have the choice of three different views:

  • The Detail View shows the details of a single requirement or folder.

  • The Reading View shows one or more requirements in a textual format.

  • The Tree Table View shows one or more requirements in a tabular format.

The Baselines module allows you to view and manage baselines. A Baseline is a snapshot of the project requirements tree at a specific point in time for future reference. This snapshot includes the whole tree with all work items and provides a stable point for managing changes.

The Coverage View allows you inspect and manage the relationship and coverage between different work items.

The Traceability Matrix allows you to view and manage the links between your project work items to ensure correctness and coverage.

Configuring Azure DevOps for Requirements Management

We highly recommend that your administrator configure your Azure DevOps processes with requirements management in mind, although this configuration is optional.

Requirements Work Item Types

We recommend that you create specific work item types for requirements. Examples would be types such as Customer Requirement, Functional Requirement, System Requirement. To add new work item types in Azure DevOps and assign them to your process, follow the official documentation from Azure DevOps on how to Add or Modify a Work Item Type.

Folder Work Item Type

In order to organize requirements in the Requirements Tree, it is essential to have a Folder work item type. Folders allow you to categorize and group related requirements together. By organizing requirements into folders, you create a hierarchical structure that reflects the system architecture or the logical relationships between different components. This helps in maintaining a clear overview of the requirements and makes it easier to navigate and locate specific requirements within the tree.

To structure the Requirements Tree infolders, you need to tell easeRequirements which work item type should be used for folders. You don't need to create a new work item type for that, but we highly recommend that you do so instead of reusing a default work item type (like Issue or Epic).

Only project administrators can configure the Folder work item type.

To configure the folder work item type for a project:

  • Select the desired project.

  • Open the Project settings.

  • In the Extensions section select Requirements settings

  • In the field "Folder work Item type", select the desired work item type

Related pages