Requirements

Generates a list of unique names of the requirements found in the model.

Options

• --model, -m

  The model(s), as a graphml file.
  This option can occur multiple times.

• --blocked, -b

  This option enables or disables the BLOCKED feature. When -b true GraphWalker will filter out elements in models with the keyword BLOCKED. When -b false GraphWalker will not filter out any elements in models with the keyword BLOCKED.
  Default is true.

More about requirements

Assume that there are requirements for a system under test, and there is a need to track what requirements are covered by tests, and what requirements were verified during an execution of a test. GraphWalker let's you add traceability by entering into a model, where specific requirements are to be verified.

The command above can be used to track requirement coverage of test models.

When executing tests, GraphWalker can report on the actual coverage of the requirement. Below is an example from the Amazon Shopping Cart example, when running:

mvn graphwalker:test

Output on the terminal in the end of the test:

  "requirementCoverage": 75,
  "requirementsPassed": [
    {
      "modelName": "ShoppingCart",
      "requirementKey": "UC01 2.2.3"
    },
    {
      "modelName": "ShoppingCart",
      "requirementKey": "UC01 2.2.1"
    },
    {
      "modelName": "ShoppingCart",
      "requirementKey": "UC01 2.2.2"
    }

Amazon shopping Cart example

To explain requirements, let's look at the Amazon Shopping Cart example. To the left there is a requirement document describing some feature. Click on it to have a look.

In GraphWalker Studio, we enter references into the model from the requirement document, so we know what requirements we cover.

In the animation below, when each vertex is selected, the Requirement field to the left is updated.

Let's have a look at the last vertex named v_ShoppingCart. The requirement attached to it is called UC01 2.3, which is a reference to the requirement document 2.3 Results. Meaning, that in the model, the vertex v_ShoppingCart is the part of the test that will verify that specific requirement.

Format of the requirement

The requirement in GraphWalker, is a string that should uniquely reference some external requirement.

GraphWalker accepts multiple requirements separated by commas. For example:

Some requirement 123, Antother requirement XFSGE