The lesson shows you how to change a requirement in DOORS®. The Rational® Rhapsody® Gateway
allows you to navigate to the original DOORS requirement,
make the change in DOORS,
and update the Gateway and Rhapsody with
the new information.
Requirement changes often occur and these changes are
made directly to the DOORS requirements.
By virtue of the traceability links that have been set up between
the model elements and the requirements, you can see the model elements
(in the case of the provided example, the use cases) that need to
change as the result of a requirement change. The impact of a requirement
change is analyzed and viewed easily in the Rhapsody Gateway.
- Start Rhapsody and
load the same elevator project you have been using in this tutorial
by opening the elevator.rpy file. Right click elevator
and select Rhapsody Gateway
to open the Gateway Management view.
- Double-click HL_REQ 2 in the left
column under Document 1 Doors XML, enter your DOORS login, and clickOK to
open DOORS.

- Edit the requirement text for HL_REQ 2 in
the Selection Text box, for example, by adding
the word down after or.
Save the changes to the DOORS requirement.
- Reopen the Rational Rhapsody Gateway window and
select Document1 Doors XML in the left column
of the Management View.
- Right click Document1 Doors XML to
open a dialog, and select Reload for DOORS to run on the reload. Confirm
the orange box on HL_REQ 2 appears indicating
a change has occurred.
- Select the Coverage Analysis view
tab, and click HL_REQ 2 in the middle Selection column.
Check the text from the Selection Text box
below and confirm that the requirement down is added
to the text
- Return to the Management View and click the UML
Model Rhapsody at the top of the left column. Confirm
that it says it contains references to the new requirement.
- With the UML Model Rhapsody still
highlighted in the left column of the Gateway Management View, select from the menu bar.
- The Add High level requirements dialog
opens. Highlight elevator in the bottom box, and click OK.
- Another Add High Level Requirements dialog
appears that says that there is one modified requirement. Click OK.
- When prompted to reload the UML Model select Yes.
Note the orange symbol indicating the UML Model has
changed, and the orange symbol next to the main uses Use
Case model.
- Return to the open Rhapsody window
and double-click on HL_REQ 2 in the main uses Use
Case diagram. View the requirement text in the dialog
in the Specification section, and check that down was
added to the text.
The change to a requirement was made in both Rhapsody and Gateway. Now, you are ready
to export Rational Rhapsody model elements to
Doors, view those elements in DOORS.