Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Example with the Baseline blueprint:

Step 1. The baseline summary page

(Fresh page with the RY Baseline macro)

Image Modified

Step 2. After the first click

The record is created in the database.

The number of expected requirements is fixed.

The query is fixed.

Image Modified

Step 2 bis. Need to change the query?

If you change the query on the page, the record of
the baseline won't be updated, since it is already
created.

If you need to update it, click "Recount" on the
previous screen.

Image Modified

then click Recount.

Step 3. Freeze

When clicking "Freeze requirements",
a progress bar appears.

Image Modified

Step 4. Final

The two lines are a single component, it is not possible
to display the baseline name or status alone.

Image Modified

Example with the baseline wizard:

Step 1. Search

In the search, click Make baseline.

Image Removed

Image Added

Step 2. Choose the name

A title for the baseline will be automatically suggested.

Image Added

Step 3. Check the dependencies

This step suggests the dependencies which are
going out of this baseline.

Feature removal: We don't display this step when
the baseline is large (more than 1 page of results,
i.e. 600 requirements), because it is impossible to
calculate the results with accuracy without using large
amounts of memory. We keep this step for legacy
and teaching reasons.

Feature removal: There used to be an "Add" button
for the dependencies, there isn't anymore.

Image Added

Step 4. Choose options

In the past, the user could choose to freeze now or later;

Now, we have 2 options to choose.

Image Added

Step 5. The progress bar

Like in the other situations, the "Create baseline" of
the previous screen will create a record in the database,
then display a progress bar, then a final state as seen
in the screenshot.

Image Added


Baselines: We don't suggest the dependencies anymore

As seen in the Step 3 above:

  • Suggestions to add dependencies in baselines can't be accurate anymore, if we want to keep the memory footprint small for Data Center instances,
  • Therefore, we don't suggest dependencies if the baseline is large (>600 requirements) or if it is a refreeze.


That's all. We have tried to keep changes almost seamless in 3.1 compared to the version 3.0, and we have removed the minimum, and we hope that we will not inconvenience your users too much. These changes were required to avoid loading large amounts of requirements in memory, and Data Center administrators will certainly appreciate the change.