IBM Rational Requirements Composer, Version 2.0 Licensing Information

Answer

Abbreviations used in this document
AU = authorized user
FL = floating user

Licenses for Rational Requirements Composer V2.0
In addition to the Rational Requirements Composer client licenses, a Rational Requirements Composer server license is required. The server license activation kit makes the built-in 60-day trial permanent and includes entitlements for 3 author AU.

• Server license (activation kit)
• Author license (AU and FL)
• Review license (AU and FL)

Licensing differences between Rational Requirements Composer V1.0 and V2.0

• FL is now available for both author and reviewer licenses.
• You can now customize roles and their permissions so that you can control who creates reviews and project snapshots.
• The new product capabilities can be governed by these licenses and role customizations.

Notes about capabilities, clients, and license types
The following table displays maximum capabilities. Specific role assignments can limit user access to various capabilities (For example, an author on one project might only have reviewer privileges on another).

Project administration capabilities are available to authors who have project administrative rights.

Collaborative ALM actions require the appropriate license and project permission for the action that is being performed. For example, to create a work item in Rational Team Concert™ from within Rational Requirements Composer, the user must be defined in the RTC server, have a RTC contributor license assigned, and have an appropriate role assigned in the relevant RTC project area. For more information see the Collaborative ALM scenarios.

Rational Requirements Composer includes the Jazz Team Server. Administrative tasks for the Jazz Team Server, such as configuring the server or adding users to the server, do not require a Rational Requirements Composer license.


Rational Requirements Composer 2.0 Client License Capabilities

Tasks	Rich Client		Web Client
	Author License	Reviewer License	Author License	Reviewer License	No license required
Authoring
Create artifacts Upload files to repository Initiate reviews Create collections Create project snapshots	Y Y Y Y Y
Create shared queries Create tags	Y Y
Create private tags	Y	Y
Use the embedded Rational Publishing Engine to create reports from templates that ship with Rational Requirements Composer V2.0	Y
Create links to work items, test plans, and test cases in Rational Team Concert & Rational Quality Manager (Collaborative ALM)	Y	Y
Use Collaborative ALM integration capabilities View rich hover information Include Rational Team Concert/Rational Quality Manager viewlets in dashboard	Y	Y	Y	Y
Viewing and Reviewing
artifacts (as read-only) artifact history collections comments	Y	Y	Y	Y
Add comments Participate in a review Approve or disapprove artifacts in a review	Y	Y	Y	Y
Export artifact or set of artifacts to Microsoft® Word	Y	Y
Customize personal Web dashboards			Y	Y
Rational Requirements Composer Project Administration
Add users to project	Y
Configure integration with Rational DOORS® and Rational RequisitePro®®	Y
Rational Requirements Composer Server Administration
Create users and configure server, database and LDAP					Y
Configure integration with Rational Team Concert & Rational Quality Manager					Y

Who should be assigned Rational Requirements Composer author licenses?
Author licenses are for anyone who writes or edits documents; or adds artifacts to the repository.
This includes analysts, project managers, and anyone else who interacts with client stakeholders to define, elicit, validate, analyze, and report on requirements. In some organizations, developers or architects may fill the role of analysts (partly or completely).
Licenses are also needed by project delivery team members who will be composing and editing documents (team leads, project manager, user experience team, etc.).

Who should be assigned Rational Requirements Composer reviewer licenses?
Anyone who needs to view, comment, and participate in review & approval cycles. This includes the following people:

• Client stakeholders
• Project delivery team stakeholders. These can include architects, developers, test developers, testers.
• Managers who want to monitor projects, but do not author or edit them.

Anyone without a Rational Requirements Composer author license who is using the Collaborative ALM scenario to pull information from Rational Requirements Composer (for example, when using Rational Requirements Composer viewlets in Rational Team Concert and Rational Quality Manager dashboards, or creating artifacts and links across requirements and work items).

When do I need licenses for Rational Publishing Engine?
The runtime of the Rational Publishing Engine is built into Rational Requirements Composer V2.0. Rational Requirements Composer users who generate reports by using its reporting wizard and included templates do not require Rational Publishing Engine licenses.

It is possible to customize the included templates for your organization, or create new templates and use them in Rational Requirements Composer. In the following cases:

• The people authoring new custom templates or modifying the included templates needs Rational Publishing Engine to be installed on their workstations; they also need the Rational Publishing Engine licenses.
• Rational Requirements Composer users who generate reports from custom templates will require Rational Publishing Engine licenses, but do not have to have Rational Publishing Engine installed. The first time a Rational Requirements Composer user attempts to generate a report from a custom template, a prompt will ask for Rational Publishing Engine license details (typically, the user would enter your license server details).
• Custom templates can be added to a Rational Requirements Composer server and made available through its reporting wizard if they follow the pattern of the included templates.

For more information on integration scenarios and their status see Rational Requirements Composer integrations on jazz.net.