Workflow for variants and baselines in GCM and ELM applications

As a configuration lead or team lead, you should understand the workflow in the Global Configuration Management (GCM) application and IBM® Engineering Lifecycle Management (ELM) applications to create a global configuration variant and to create a baseline to capture a milestone.

Stream and baseline automation now completes some of the work that was formerly manual.

Configuration leads must have the following permissions:
  • In the contributing ELM applications, permission to create streams and baselines.
  • In the GCM application, either permission to create streams from streams or create streams from baselines. By default, configuration leads have these permissions.

In this scenario, a configuration lead needs to create a UK variant global configuration, starting from a global configuration baseline. The configuration lead follows the scenario through to the creation of a milestone baseline, working with the team leads of the Requirements Management (RM) and Quality Management (QM) applications.

The configuration lead completes most of the work for global configurations. In this scenario, a configuration lead, John, completes all of the work, except for the parts that are completed by the team leads for other ELM applications.

Create a variant and a baseline

  1. The configuration lead, John, creates a global configuration variant from a baseline.

    John starts with the latest release of a nested global configuration, Meter Reader Mobile US 3.0 GA.

    Figure 1. Global configuration baseline

    Image shows nested global configuration baseline

    John creates a stream for the variant and calls the new stream Meter Reader Mobile UK 3.0.

    Figure 2. Create stream for UK variant

    Image shows Create Stream dialog box with UK variant changes

    Initially, the new UK variant stream has the same non-modifiable baselines as the baseline that it was created from.

    Figure 3. New UK variant stream

    Image shows new variant UK stream

    For the UK variant, John will change requirements and test cases, so the RM and QM configurations must be modifiable streams. (John can use the AM (formerly DM) baseline as is.) The RM and QM configurations are from other tools. Either John can create the variant streams automatically from GCM, or he can talk to the RM and QM team leads about creating the variant streams in their tools. Use one of the following processes.
    • John creates the variant streams automatically, so the streams are in the global configuration hierarchy. John must communicate with the RM and QM team leads when the stream variants are ready for their teams to use. Skip to step 3.
    • The RM and QM team leads create the variant streams. They must tell John when the streams are available so that he can replace the baselines with the variant streams in the global configuration. Proceed to step 2.
  2. John replaces the RM and QM baselines with streams.

    John uses the Replace context menu (right-click) from the Meter Reader (RM) Mobile US 3.0 GA baseline, and picks the new RM stream UK variant that the team lead told him about, Meter Reader (RM) Mobile UK 3.0.

    Figure 4. Replace a baseline with a stream

    Image shows replacing a baseline with a stream

    John completes the same step for the new QM stream UK variant, and then the global configuration looks like the following image.

    Figure 5. Replace a baseline with a stream

    Image shows the global configuration UK variant

    John notifies the team leads that the global configuration variant is ready for their teams to use. The team leads tell their teams to set their configuration context to the global configuration variant, as shown in the following image. The local configuration is set automatically to use the new stream variant for the specific ELM application.

    Figure 6. Working in the correct global configuration context. The RM configuration context is set automatically.

    Image shows the correct global configuration context in RM

  3. Teams change the variant in their ELM applications.

    After the work of defining the necessary variant streams is done, teams can use the streams as they update and modify requirements and test cases. The teams make the necessary changes for the UK variant, and then deliver their changes to their local configurations. They are ready for the first milestone of the schedule, M1, so it is time to baseline the global configuration.

  4. John creates the M1 baseline.

    John can create a baseline or a baseline staging stream, depending on his team's process.

    Create a baseline: The M1 milestone occurs on a specific date and all teams that contribute configurations must be finished with changes to their streams by that date. John creates the baseline hierarchy from the root by selecting Create Baseline, as shown in the following image. Baselines are automatically created for the stream variants contributed by ELM applications.

    Figure 7. Create a baseline

    Image shows how to create a baseline

    John has created the baseline. Proceed to step 8.

    Create a baseline staging stream: The M1 milestone does not occur on a specific date. John creates a baseline staging stream. Proceed to step 5.

  5. The configuration lead stages a baseline.

    John wants to capture the state of the stream for the M1 milestone. He initiates the process by creating a baseline staging stream that is called Meter Reader Mobile UK 3.0 M1, which is an uncommitted baseline that will be committed after John replaces the RM and QM streams with baselines.

    Figure 8. Create a baseline staging stream

    Image shows how to create a baseline staging stream

    If John tries to commit Meter Reader Mobile UK 3.0 M1 now, the operation fails because the global configuration still contains (modifiable) streams.

    The RM team lead determines that the requirements work for M1 is complete, and then creates a baseline that is called Meter Reader (RM) Mobile UK 3.0 M1. The QM team lead also creates a baseline of the QM local configuration. John communicates with the RM and QM team leads to find out when he can replace the stream variants with baselines as they become available.

  6. The configuration lead replaces the RM and QM streams with baselines.

    Figure 9. Replace a stream with a baseline

    Image shows replacing a stream with a baseline

    John also replaces the QM stream with a baseline, and then the tree view looks like the following image.

    Figure 10. Global configuration for M1 milestone

    Image shows M1 milestone global configuration

  7. The configuration lead commits the baseline.

    Now all the configurations are non-modifiable baselines, so John can commit Meter Reader Mobile UK 3.0 M1.

    Figure 11. Commit the M1 milestone baseline

    Image shows how to commit the baseline

    The first milestone of the UK variant global configuration is complete.

  8. John can now compare the UK variant with the original US configuration, which shows the differing configurations.

    Figure 12. Compare US and UK global configuration baselines

    Image shows comparison of US and UK global configuration baselines

    To gather more details about the changes, John might open the RM or QM configuration and compare it to a different version.

Learn more

To learn more about global configuration advanced topics, see the following resources:

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki