An Introduction To Rational's New Requirements Composer
March 3, 2009
Rational’s new Requirements Composer
An Introductory Overview
By Mark J. Sandefur
In late 2008 a new entrant emerged in the expanding Requirements Definition tools arena – IBM Rational’s
Requirements Composer. As Rational is correctly recognized as a thought leader in the Application Lifecycle
Management (ALM) space, it is important to see the role this new entry can play, for enterprises.
Rational Requirements Composer, hereafter referred to as RRC, is not a Requirements Management tool. It rather
attempts to exist earlier in the lifecycle, where requirements are first defined. This matches the current trend, whereby
business-side resources can contribute more fully on projects, using various ‘vocabularies’ to collaborate on ideas.
RRC seeks to serve two audiences: Analysts (who author), and Stakeholders (who review). Ultimately, it can thus
serve as a collaborative repository for organizing, creating, refining, and reviewing requirements and their related
materials. This can shorten duration and increase your competitiveness in a demanding market; and also lower costs
through better communication and less rework.
Flexible sources, of Requirement material
A great starting point in trying to grasp RRC’s role is understanding the variety of artifacts that can be leveraged, in it.
These can include:
Rich Text – either create Rich Text (including media such as images) in the editor, or leverage other rich
formats such as Microsoft Office documents.
Figure 1 - Rich Text document example
Multiple Glossaries – Remove ambiguity on business and technology terminology.