![Close [x]](http://dw1.s81c.com/i/c.gif){kind=small}
Wrap up
In this tutorial you've seen how you can manage application changes by centralizing the collection of all change requests into Rational ClearQuest, to assess all changes in a consistent format and evaluate which changes your team has resources to implement. The integration between Rational ClearQuest and Rational RequisitePro protects requirements from unaccepted changes, provides visibility into the origin of requirement changes and allows you to mechanically update your requirements specification with the latest changes.
Rational ClearQuest in this case is merely a funnel and sorting tool, collecting the requests and making them ready for assessment. IBM Rational RequisitePro is still the driving force behind the development progress, since it holds the definition of requirements for the project. IBM Rational ClearQuest and the integration available are merely a way of further enhancing and refining the requirements as the development of the application progresses with the long term goal to deliver software that stays inline with the ever evolving stakeholder needs.
As you look forward to Part 4, you'll be concentrate on managing and tracking the changes themselves, rather than the requests that might have been triggered. These changes are recorded in IBM Rational ClearCase, which integrates with the other tools by providing a method for tracing changes in code, requirements, requests and other entities during the life of the project. In Part 5, you'll look at the role of testing packages in the development of an application.
Table of contents
Local resources
Tags
Use the slider bar to see more or fewer tags.
Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere).
My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).
Popular tutorial tags |
My tutorial tagsSkip to tags list
Popular tutorial tags |
My tutorial tags
