Change Management

Notice the banner at the top of the Artifacts tab.

The message informs users that the module is under change management. Later in the demonstration script, a new change set will be created. For now, learn about the audit and traceability capabilities of ELM.

  1. Click the Open History menu item under the hamburger menu icon.

Birds-eye view

  1. Click the Audit History tab.

  1. Click the Expand All link.

  1. Notice the full audit trail.

From this view, auditors can view who changed what, when the change was made, and in which change set.

  1. Click the Close History button.

  1. Click the 3. Satisfied By link in the Views panel.

  1. Notice the columns can show traceability.

Here, traceability is seen in the Satisfied By column. Rows with data in the Satisfied By column provide links to the downstream system requirements that satisfy these higher-level requirements. Notice that several rows have no information in the Satisfied By column. These empty fields illustrate gaps in the requirements providing a gap analysis traceability view.

  1. Hover the mouse over the 4968 link in the ID column (don't click the link).

Notice the additional details about the requirement that are visible by simply hovering over the item in the table.

  1. Click the first question icon icon in the Satisfied By columns.

Don't see the question icon

If the question icon doesn't appear, try clicking the refresh button for the widget at the top right.

Notice the options available to set the link validity for the requirement.

Traditionally, traceability is maintained in separate documents such as spreadsheets. This is a manual process, prone to error, very costly to maintain, and usually outdated as soon as the author clicks “save”. Here traceability is added, maintained, and tracked directly in the IBM solution and can easily be reported on.

To learn more about link validity go here.

For Act 3, remain on the current browser page and learn about ELM's design input capabilities.