• Like
  • Save
Lab 1: Managing requirements by using suspect traceability -module
Upcoming SlideShare
Loading in...5
×
 

Lab 1: Managing requirements by using suspect traceability -module

on

  • 1,348 views

(Module: Identifying and managing change) ...

(Module: Identifying and managing change)
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

Statistics

Views

Total Views
1,348
Views on SlideShare
1,348
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Lab 1: Managing requirements by using suspect traceability -module Lab 1: Managing requirements by using suspect traceability -module Document Transcript

    • Student Workbook Module: Identifying and managing changeLab 1: Managing requirements by using suspect traceability -module© Copyright IBM Corp. 2013 1Course materials may not be reproduced in whole or in part without the prior written permission of IBM.Lab 1: Managing requirements by using suspecttraceability -moduleObjectivesAt the end of this lab you will be able to assess the impact of change by using suspect traceabilityGiven► 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 tasksIn 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
    • Student Workbook Module: Identifying and managing changeLab 1: Managing requirements by using suspect traceability -module2 © Copyright IBM Corp. 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.Task 1: Select a suspicion profileIn 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 ademonstration 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, youare indicating that you want to see which artifacts have been affected by changes since the administrator set theprofile.Figure 1: Select a suspicion profile6. From the Choose suspicion Profiles for Automated Meter Reader (Water) select Analyst as the suspicionprofile and click OK to close the window. The Analyst suspicion profile watches for changes between artifactslinked by the link types: Constrains, Decomposition, Link, and Satisfaction.Task 2: Create a view for a specific suspect profileIn this task, add a column to highlight any suspicious changes, as defined by the selected suspicion profiles. Youcreate 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 indicatorTIP: If you click a column, the artifacts are sorted in ascending order. If you click again, the artifacts are sortedin 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.
    • Student Workbook Module: Identifying and managing changeLab 1: Managing requirements by using suspect traceability -module© Copyright IBM Corp. 2013 3Course 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 tocollect 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 SystemRequirements Specification) The handheld device shall provide for a minimum of 16MB of memory in order to su (AMR SystemRequirements Specification)b. Verify that no suspicious changes exist between the artifacts.7. Log out of the project.Task 3: Change an artifactThe analyst profile repost on changes between artifacts that are linked by the Satisfies relationship. A change to theartifact 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 andpassword.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 meansfor 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 theartifact 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, Thehandheld device shall provide for the means for the meter reader tomanually 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 change1. Log in to the project as Bob by typing bob for both the user ID and password, and then go to the Artifacts pageof 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 tocollect and store information from the meter.5. Verify that the suspicion indicator is displayed. The suspicion is caused by the changes that Sally made. Noticethe different icons used to detail the type of change that caused the suspicion.
    • Student Workbook Module: Identifying and managing changeLab 1: Managing requirements by using suspect traceability -module4 © Copyright IBM Corp. 2013Course materials may not be reproduced in whole or in part without the prior written permission of IBM.Figure 3: Suspicion is indicated in a view6. Hover the cursor over the icon in the suspicion column to identify that the change is caused by one of the linkedartifacts.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 linkis scoped at the module level.7. From the rich hover window, click the artifact that caused the suspicion. The artifact that caused the suspicionopens 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 icon9. Click the Audit History tab and determine which change was made to the artifact that caused it to be marked assuspect. 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 affectedby the change.
    • Student Workbook Module: Identifying and managing changeLab 1: Managing requirements by using suspect traceability -module© Copyright IBM Corp. 2013 5Course 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 change11. 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 storeinformation from the meter.c. Hover the cursor over the suspicion icon in the Suspicion column and remove the suspicion by selectingClear All.Figure 7: Clearing all suspicions from the Suspicion column