The document outlines a lab module focused on managing requirements through suspect traceability for an automated meter reader (AMR) project. It includes objectives, tasks for selecting suspicion profiles, creating views for specific profiles, changing artifacts, and assessing the impact of those changes. The lab aims to teach the impact assessment of changes on artifacts through the use of a traceability system.

1. Student Workbook Module: Identifying and managing change
Lab 1: Managing requirements by using suspect traceability -module
© Copyright IBM Corp. 2013 1
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Lab 1: Managing requirements by using suspect
traceability -module
Objectives
At the end of this lab you will be able to assess the impact of change by using suspect traceability
Given
► Automated Meter Reader (Water) project (AMR)
Description
► In this lab, you select a suspicion profile and then assess the impact of the changes to an artifact.
Exercise tasks
In this exercise, you complete these tasks:
 Task 1: Select a suspicion profile
 Task 2: Create a view for a specific suspect profile
 Task 3: Change an artifact
 Task 4: Assess the impact of a change

2. Student Workbook Module: Identifying and managing change
Lab 1: Managing requirements by using suspect traceability -module
2 © Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Task 1: Select a suspicion profile
In this task, you select a suspicion profile that watches for changes to specified artifacts and attributes in the project.
Each suspect profile tracks specific changes to link and attribute information.
1. You are in the lab environment All Projects page of the RM application (https://jazz-
server:9443/rm/web). You are logged in as bob with password bob.
2. Navigate to the Automated Meter Reader (Water) project Artifact page.
3. Optional: In the help system, open the “Viewing and clearing suspect traceability” topic and watch a
demonstration by clicking the Show Me link.
4. From the 01 Requirements folder, click AMR Stakeholder Requirements Specification.
5. From the artifact menu options in the upper-right corner of the artifact, click the suspicion profile icon.
NOTE: An administrator created the profile and set it to watch for specific changes. By clicking the icon, you
are indicating that you want to see which artifacts have been affected by changes since the administrator set the
profile.
Figure 1: Select a suspicion profile
6. From the Choose suspicion Profiles for Automated Meter Reader (Water) select Analyst as the suspicion
profile and click OK to close the window. The Analyst suspicion profile watches for changes between artifacts
linked by the link types: Constrains, Decomposition, Link, and Satisfaction.
Task 2: Create a view for a specific suspect profile
In this task, add a column to highlight any suspicious changes, as defined by the selected suspicion profiles. You
create a view so that you can consistently and easily return to the same perspective of the data.
1. From the Views section, click Trace to System Requirement.
2. Add the Suspicion column to the Artifacts page and move the column to be displayed before the artifact ID.
TIP: To add the column, click the Change Column Display Settings icon.
3. Name the view Suspect-Analyst Profile, ensure that it is a personal view, and save it.
4. Either scroll through the module or click the suspicion column to sort, and then look for suspect artifacts.
Depending on previous changes, you might see suspect indicators. If you do not see changes, do not worry.
Figure 2: The suspicion indicator
TIP: If you click a column, the artifacts are sorted in ascending order. If you click again, the artifacts are sorted
in descending order. If you click the column a third time, the sort is removed from the artifacts.
5. Switch the view to Suspect-Analyst Profile.

3. Student Workbook Module: Identifying and managing change
Lab 1: Managing requirements by using suspect traceability -module
© Copyright IBM Corp. 2013 3
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
6. Find the artifact named The handheld device shall allow for the meter reader to
collect and store information from the meter.
a. Verify that this artifact is linked to two system level requirements:
 The handheld device shall provide for the means for the meter reader to manually (AMR System
Requirements Specification)
 The handheld device shall provide for a minimum of 16MB of memory in order to su (AMR System
Requirements Specification)
b. Verify that no suspicious changes exist between the artifacts.
7. Log out of the project.
Task 3: Change an artifact
The analyst profile repost on changes between artifacts that are linked by the Satisfies relationship. A change to the
artifact will cause a suspicion that has to be evaluated and acted upon.
1. Log in to the Automated Meter Reader (Water) project as Sally by typing sally for both the user ID and
password.
2. Go to the Artifacts page of the Automated Meter Reader (Water) project.
3. From the 01 Requirement folder, click AMR System requirements.
4. Find and select the artifact 435, named The handheld device shall provide for the means
for the meter reader to manually enter a meter reading.
5. Open the artifact for editing by either expanding its edit menu and clicking Edit Attributes, or by opening the
artifact and clicking Edit.
a. In the context of the artifact, add the word detail to the end of the artifact’s name so that it is, The
handheld device shall provide for the means for the meter reader to
manually enter a meter reading detail.
b. For the Status attribute, select Accepted.
c. Set the Clarity attribute to Medium.
6. Log out as Sally.
Task 4: Assess the impact of a change
1. Log in to the project as Bob by typing bob for both the user ID and password, and then go to the Artifacts page
of the Automated Meter Reader (Water) project.
2. From the 01 Requirements folder, click AMR Stakeholder Requirements Specification.
3. In the Views section, click Suspect-Analyst Profile.
4. Find the artifact named The handheld device shall allow for the meter reader to
collect and store information from the meter.
5. Verify that the suspicion indicator is displayed. The suspicion is caused by the changes that Sally made. Notice
the different icons used to detail the type of change that caused the suspicion.

4. Student Workbook Module: Identifying and managing change
Lab 1: Managing requirements by using suspect traceability -module
4 © Copyright IBM Corp. 2013
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Figure 3: Suspicion is indicated in a view
6. Hover the cursor over the icon in the suspicion column to identify that the change is caused by one of the linked
artifacts.
Figure 4: Hovering over the suspicion icon to reveal more details.
TIP: Even though suspicion is shown in the module, suspicion is not shown for the base artifact because the link
is scoped at the module level.
7. From the rich hover window, click the artifact that caused the suspicion. The artifact that caused the suspicion
opens in the module that it belongs to.
8. Explore the history of the artifact by clicking the Open History icon.
Figure 5: The Open History icon
9. Click the Audit History tab and determine which change was made to the artifact that caused it to be marked as
suspect. You can see the details of the changes that were made to each version of the artifact.
10. In the right sidebar, in the Links section, open the links explorer and determine which artifacts might be affected
by the change.

5. Student Workbook Module: Identifying and managing change
Lab 1: Managing requirements by using suspect traceability -module
© Copyright IBM Corp. 2013 5
Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
Figure 6: Using the links explorer to assess the impact of the change
11. Close the links explorer and return to the AMR Stakeholder Requirements Specification artifact.
12. Take any actions that are necessary to keep the linked artifacts up to date, and then clear the suspect status:
a. Select the Suspect-Analyst Profile view.
b. Find the artifact named The handheld device shall allow for the meter reader to collect and store
information from the meter.
c. Hover the cursor over the suspicion icon in the Suspicion column and remove the suspicion by selecting
Clear All.
Figure 7: Clearing all suspicions from the Suspicion column