You have learned the basics needed to manages requirements
with Rhapsody® Gateway
and DOORS®, traceability, coverage,
and impact analysis across a project lifecycle. The system requirements
are brought into Rhapsody as
SysML artifacts. Now that you have completed the course, you know
how to import, analyze, and trace DOORS requirements
in the Rhapsody Gateway.
You can also export Rhapsody model
elements to DOORS, and try
it now on your own.
Lessons learned
If you have completed
all of the lessons, you should now be able to successfully apply a
simple to complex pattern and perform the following tasks:
- Bring requirements into Rhapsody Gateway
from DOORS
- Link requirements to model elements in Gateway
- Analyze the requirements and coverage of the requirements in the Rhapsody model
- View how traceability occurs when a requirement changes in DOORS
- Upload Rhapsody model
elements to DOORS
- Change a model element in Rhapsody and
export the modification to DOORS
Additional resources
If you want to learn
more about the topics covered in this tutorial, consider the following
sources:
- "Integrating Rational® Rhapsody and Rational DOORS"
topic in Rational Rhapsody online Help
- White papers from the developerWorks® Web
site