Workflow for using configurations in projects

Understand the workflow for using configurations to work in parallel versions of a product or system, and create hierarchical structures of configurations from IBM® Engineering Lifecycle Management (ELM) applications to represent components of your product or system.

Before you begin

Procedure

  1. A configuration lead completes these steps:
    1. Optional: In each project area, if no baseline exists as a starting point for the team to do their work, creates the baseline from the initial stream. Creating a baseline freezes the set of versioned artifacts at a point in time, so it is clear which versions of artifacts were used when development started.
    2. Create a stream for the team to work in.
  2. In each lifecycle application, team members do their work, which includes these actions:
    1. Select a stream to work in.
    2. RM application: Create a change set to group your changes and new artifacts. Some projects enforce the use of change sets, and might also enforce linking them to approved work items.
      • If your team uses global configurations, the change set is automatically added to your personal stream. This stream is created automatically if it didn't already exist. See workflow for global configurations.
    3. In the Global Configuration Management application, add other configurations that you need from the lifecycle applications, to the personal stream.
    4. Create and update artifacts. For example, update a system requirement, and associate it with a test case.
    5. Compare how your configuration differs from another. For example, you might compare your change set to the baseline it was created from to see how it has changed; or you might compare your change set to the destination stream to see how they differ.
    6. Deliver the changes to the stream.
    7. Accept changes from the parent stream.
  3. Capture the version of resources used at a milestone or at critical points in a release by creating a baseline of a stream. Work can continue on this stream. For new versions or releases, create new streams from a baseline.
  4. Optional: Create reports so that you can view data for a configuration in your Jazz dashboards. For example, you might create a report that shows test plans and test cases for a specific configuration, and then add that report to your dashboard. In this release, reporting on configuration-enabled projects is available with limitations. See Getting started with reporting by using Lifecycle Query Engine data sources on Jazz.net.
  5. Configuration leads or team members with configuration management permissions can create global streams and add local configurations from lifecycle applications to them. Global configurations give you a view of all the artifacts in a product variant. See workflow for global configurations. These team members can also complete these actions:
    • Branch them to create new development streams
    • Extend them to include other configurations.

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