...
Example with the Baseline blueprint:
Step 1. The baseline summary page (Fresh page with the RY Baseline macro) | |
Step 2. After the first click The record is created in the database. The number of expected requirements is fixed. The query is fixed. | |
Step 2 bis. Need to change the query? If you change the query on the page, the record of If you need to update it, click "Recount" on the | then click Recount. |
Step 3. Freeze When clicking "Freeze requirements", | |
Step 4. Final The two lines are a single component, it is not possible |
Example with the baseline wizard:
Step 1. Search In the search, click Make baseline. |
Step 2. Choose the name A title for the baseline will be automatically suggested. | |
Step 3. Check the dependencies This step suggests the dependencies which are Feature removal: We don't display this step when Feature removal: There used to be an "Add" button | |
Step 4. Choose options In the past, the user could choose to freeze now or later; Now, we have 2 options to choose. | |
Step 5. The progress bar Like in the other situations, the "Create baseline" of |
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.