Rational® RequisitePro® Release Notes

Version 2003.06.00

Copyright © 2003 Rational Software Corporation. All Rights Reserved.

This documentation (the “Work”) is protected under the copyright laws of the United States and/or other jurisdictions, as well as various international treaties. Any reproduction or distribution of the Work is expressly prohibited without the prior written consent of Rational Software Corporation.

Legal Information

Scope

This document provides information about the 2003.06.00 release of Rational RequisitePro.

These release notes provide information critical to installing and using Rational RequisitePro, including hardware and software requirements, compatibility, and known issues with this release.

Contents

What's New in This Release

Enhanced Rational XDE Integration

Simplified Configuration for the RequisitePro and Rational ClearQuest Integration

Oracle and SQL Server Setup Documentation Installed by Default

Simplified Configuration of Rational RequisiteWeb

Document Authoring in RequisiteWeb

RequisiteWeb Traceability Matrix

Enhanced Project Templates

Enhanced Learning Projects

Product Documentation

Hardware/Software Information

Client Requirements

Server Requirements

RequisiteWeb

Installation, Upgrading, and Licensing

Installation Information

Installation Issues

Upgrading from Previous Versions of RequisitePro

Compatibility Issues

With Rational Tools

With Third-Party Products

With International Systems

Restrictions and Guidelines on Using RequisitePro

Microsoft Word Issues

Windows NT Fonts

Configuring E-mail

Offline Authoring

Numerical Attributes

Views and Queries

Requirement Metrics

Known Issues and Change Requests

Opening Sample Projects for the First Time

Creating Projects

Saving Documents

Assigning Parent Requirements in Documents

Importing Requirements

Renumbering Requirements

External Projects

RqCallback.dll

Let's Go RequisitePro

Contacting Rational Customer Support

 

What's New in This Release

Enhanced Rational XDE Integration

The Rational RequisitePro-XDE Integration lets you combine the use-case modeling and application design capabilities of XDE with requirements management capabilities in RequisitePro.

You can define your use cases by integrating Unified Modeling Language (UML) diagrams in XDE and Microsoft Word documents in RequisitePro. You can assign attributes and traceability to your use cases in order to manage your use cases in the context of the requirements. In addition, you can trace your requirements in RequisitePro to your design in XDE in order to better understand the impact of requirement change on your design.

The use-case modeling capabilities of this integration are similar to those of Integrated Use Case Management, which integrates RequisitePro and Rational Rose. You can migrate use-case associations in a Rose model when you upgrade the model to an XDE model.

To use this integration, you must install both RequisitePro and XDE on your system.

Simplified Configuration for the RequisitePro and Rational ClearQuest Integration

Configuring the integration between RequisitePro and ClearQuest has never been easier. A wizard guides you through the setup enabling you to complete your configuration in minutes. You can also use the wizard to test and repair existing integrations. The integration lets you associate enhancement requests, defects, and other ClearQuest records with RequisitePro requirements.

The wizard replaces the ASCQISetup.bat and ASCQISetup.exe files used to configure the integration in earlier versions of Rational Software. If you have an existing integration, you can continue to use ASCQISetup.bat and ASCQISetup.exe to modify the integration, or you can use the RequisitePro-ClearQuest Integration Wizard to make changes.

Oracle and SQL Server Setup Documentation Installed by Default

When you install RequisitePro, the following files are automatically installed in the <install drive>\Rational\RequisitePro\help directory:

• Configuring an Oracle database (oraclesetup.html)
• Configuring a SQL Server database (sqlsetup.html)

Simplified Configuration of Rational RequisiteWeb

Configuring your Web server for RequisiteWeb is quick and easy, requiring just five steps: Install the application, specify your username, configure SSL(optional), reboot the machine, and add your projects to the project list.

You can customize the RequisiteWeb Login Page and footer to accommodate your company's needs.

Document Authoring in RequisiteWeb

In RequisiteWeb, you can now create, modify, and delete documents. When you create a document, RequisiteWeb references the new document in the project database. You can take a document offline and modify its content in Microsoft Word, just as you can with RequisitePro.

RequisiteWeb Traceability Matrix

The Traceability Matrix provides an additional way to manage traceability, complementing the Attribute Matrix and Traceability Tree views that are already available in RequisiteWeb. The Traceability Matrix view presents the relationships between requirements of the same or different types. Use this matrix to view indirect relationships and suspect relationships. You can filter and sort the requirements that are displayed.

Enhanced Project Templates

The project templates available in RequisitePro contain updated structure and requirement attributes to help you be more productive in a shorter amount of time.

Enhanced Learning Projects

The sample projects included with RequisitePro have been revised, and the examples included with the projects help you learn an approach to writing use cases.

Product Documentation

RequisitePro setup creates a Start menu program group for RequisitePro with the following items: Let's Go RequisitePro, Online Help, Release Notes, Rational Extensibility Interface Help, Technical Support, and configuration reference documents for RequisiteWeb, Oracle, and SQL Server databases. To start RequisitePro, click Start > Programs > Rational Software > Rational RequisitePro.

Let's Go RequisitePro opens when RequisitePro is first launched. Use Let's Go RequisitePro to access the RequisitePro Tutorial, Quick Tour, these release notes, Help, project administration tips, the Rational Unified Process, Rational Developer Network and other Web resources. Let's Go RequisitePro can also be opened from the RequisitePro Help menu.

In addition to RequisitePro Help, see the manual Rational RequisitePro User's Guide (available on the Rational Solutions for Windows Online Documentation CD and the Rational Software documentation Web site: http://www.Rational.com/documentation/).

Hardware/Software Information

This section provides basic information on the platforms supported and the hardware and software requirements for running RequisitePro.

Client Requirements

Hardware Requirements

Processor: 500 MHz or greater.

Memory: 128 MB or greater.
Note: We recommend 256 MB for RequisitePro project administrators who use Unified Change Management (UCM) to create baselines of RequisitePro projects.

Disk Space: 200 MB.

Monitor:

• 800 X 600 X 256-color video resolution, or greater.
• High Color or True Color is recommended.

Mouse/pointing device: Microsoft Mouse or compatible pointing device.

Software Requirements

Operating Systems:

• Microsoft Windows 2000 Professional SP-2, SP-3.
• Microsoft Windows NT 4.0 Workstation SP-6a + SRP. (If you are using RequisitePro with Rational XDE, see the XDE release notes for supported XDE platforms and see Using XDE with RequisitePro below.)
• Microsoft Windows XP Professional SP-1.

Recommendations for Using Microsoft Office with the Above Operating Systems:

• With Windows NT 4.0, use Office 2000.
• With Windows 2000, use Office 2000 or Office XP.
• With Windows XP Professional, use Office XP.

Word Processor:

• Microsoft Word 2000 SR-2, SR-3.
• Microsoft Word 2002, SP-1, SP-2.
• See recommendations for Microsoft Office above.

Let's Go RequisitePro Document Viewing: Adobe Acrobat Reader 4.x or higher.

Requirement Metrics Reporting:

• Microsoft Excel 2000 SR-2, SR-3.
• Microsoft Excel 2002, SP-1, SP-2.

Microsoft Project Integration:

• Microsoft Project 2000 SP-1
• Microsoft Project 2002

LAN Support: Microsoft networks. (Novell networks are not supported.)

Oracle Client: Versions 8.1.7, 9i R2.

Automated License Key Requests: Network connection required for automated license requests.

Other Rational Products:

• Rational ClearCase and ClearCase LT, version 2003.06.00
• Rational TestManager, version 2003.06.00
• Rational Rose, version 2003.06.00
• Rational XDE, version 2003
• Rational SoDA for Word, version 2003.06.00
• Rational ClearQuest, version 2003.06.00
• Rational ProjectConsole, version 2003.06.00
• Rational Unified Process, version 2003.06.00

To verify which product versions you have installed on your system, click Start > Programs > Rational Software > Rational Software Installed Product Information.

Server Requirements

Enterprise Database Server Requirements

• Microsoft SQL Server: versions 7.0 SP-4; 2000, SP-2, SP-3.
• Oracle Server: versions 8.1.7, 9i R2.
• Memory: 128 MB minimum. For projects with approximately 50,000 requirements, 256 MB is recommended.

Note: Memory requirements will vary depending on the number of concurrent users, the amount of data being requested, and the size of the database.
RequisitePro does not require the installation of the Oracle Java Runtime components.
• Disk Space: 200 MB recommended for a database or schema.

Remote Access Support

• Citrix MetaFrame 1.8.
• Citrix MetaFrame XP.
• Windows Terminal Services for Windows 2000 Advanced Server, SP2, SP3.

RequisiteWeb

For information about RequisiteWeb, including system requirements, installation and configuration, and known issues, see the Rational RequisiteWeb Installation and Configuration document (RequisiteWebInstall.html).

Note: The production release of Microsoft Windows 2003 was not available for final testing at the time this document was finalized. To obtain the latest information on Windows 2003 support, go to http://www.ibm.com/software/rational/.

Installation, Upgrading, and Licensing

Installation Information

For full installation instructions, see the manual Rational Software Desktop Products Installation Guide. For information about upgrading Rational Suite or integrations with other Rational products, see the manual Rational Suite Upgrade Guide and the Rational Suite Release Notes.

Both installation guides are available on the Rational Solutions for Windows Online Documentation CD and the Rational Software documentation Web site: http://www.Rational.com/documentation/.

Installation Issues

Rational Installer Incompatible with Windows "Change Journal" Feature

Rational has determined that under certain circumstances file system corruption can result from installing Rational Version 2003 products on Windows 2000 to an NTFS partition that has the windows "Change Journal" (log) enabled on it. Rational is actively working with Microsoft to better understand and identify a fix for the problem.

Before installing any Rational Version 2003 product on a computer running Windows 2000, please read Rational Solution 182435434 at http://solutions.rational.com/solutions/display.jsp?solutionId=182435434 for the latest information. Alternatively, you can search the Rational Solutions Knowledge Base at http://solutions.rational.com/solutions for the text "Change Journal". (RATLC00688306)

Other Installation Issues

• Prior to installing RequisitePro version 2003.06.00, you must uninstall all previous versions of RequisitePro.
• This product cannot be installed on a system with Rational products that are earlier than this 2003.06.00 version. For more information on how this relates to the Rational RequisitePro-XDE Integration, see Using XDE with RequisitePro.
• The Rational installation program may incorrectly report disk space requirements. If you have 200MB of free space on your machine, you can choose to continue the installation and ignore a disk space error message.
• When installing RequisitePro on a double-byte system, use the default directory path. When installing RequisitePro to a network location that other members of your team use to install RequisitePro, do not use pathnames that contain multi-byte characters. (RATLC00236978, RATLC00440239)
• The Rational Site Preparation Tool is not supported on Windows 9X class systems. (RATLC00443343)
• The Rational installer does not check to see whether the destination install directory is a valid Windows directory. If a bad directory name is entered (for example, one with bad characters), the installation may complete, but the installed product will probably not work correctly. (RATLC00236727)
• If a member of the RequisitePro administrators group installs RequisitePro, users who are not members of the administrators group may not be able to open RequisitePro. To solve this problem, the administrator must open RequisitePro after installing.
  If a member of the RequisitePro administrators group installs RequisitePro, users who are not members of the administrators group may only be able to open the sample projects read-only. To solve this problem, you can copy the sample projects to a location where you have the appropriate permissions and add the projects in their new location to your project list. (RATLC00058682)
• If you have previously installed RequisitePro version 2003.06.00 and are installing it again in a different location, the old paths to sample projects are retained in your project list. You must remove those sample projects and add the newly installed sample projects to your project list. (RATLC00057228)

Upgrading from Previous Versions of RequisitePro

Upgrading RequisitePro Across Your Company

RequisitePro version 2002.05.20 and version 2003.06.00 are compatible. For other versions of RequisitePro note the following:

• There are limitations when using RequisitePro version 2002.05.00 with versions 2002.05.20 or 2003.06.00.
• If your team accesses a shared RequisitePro project or enterprise database from multiple RequisitePro clients and RequisiteWeb, you must upgrade all your RequisitePro and RequisiteWeb installations to the same product version number.

Upgrading from Version 2002.05 and Earlier

• When you install RequisitePro version 2003.06.00, incorrect sample projects may appear in your project list. Remove the old projects titled Learning Project, Learning-Business, and the QuarterByte Savings Bank Example Project. Make sure the new sample projects, Learning Project - Use Cases and Learning Project - Traditional are added to your project list. (RATLC00057228)
• If you use the Rational ClearQuest integration with RequisitePro, see the Rational Suite Upgrade Guide for additional steps you must perform before you uninstall earlier versions of Rational Software. (RATLC00058077)

Upgrading from Version 2001A

When upgrading older RequisitePro projects that do not contain packages, RequisitePro organizes requirement artifacts in the following default package structure:

• Requirements Document. A package is created for each requirements document, including all requirements that are located within that document.
• Requirement Type. A package is created for each requirement type, including all requirements of that type that are not located in documents. If a requirement type does not include any requirements or only includes requirements that are located in documents, a package is not created for that requirement type.
• View Type. A package is created for each view type (Attribute Matrix, Traceability Matrix, Traceability Tree). Each view package contains all views of that type in the project.

You can create and delete packages in order to organize your project artifacts in a way that meets your team's needs. For example, you can group documents, requirements, and views in packages by feature, component, or team. Move artifacts between packages by dragging and dropping them or changing the Package setting in the artifact's Properties dialog box.

Upgrading Projects from Versions Earlier than RequisitePro 4.0

If a project is in a version of RequisitePro earlier than version 4.0, you must first upgrade the project to RequisitePro 4.0 before using the Database Upgrade Wizard. Contact Customer Support for information.

Upgrading Projects that are Associated with a Rational Repository

If a RequisitePro project is associated with a Rational repository (rather than the more current structure of a Rational project, which can be created in Version 2001A or later), upgrading the project may cause data loss and corruption of the Rational repository that you use with other Rational products. To protect your Rational repository, first upgrade your software and datastores to Version 2001A, then upgrade the software and datastores to the current version. For more information, see “Upgrading from Earlier Versions of Rational
Suite” in the 2001A version of Installing Rational Suite (see http://www.Rational.com/documentation/). (RATLC00015819)

Upgrading SQL Server

If you have a RequisitePro database in SQL Server, and your SQL Server software has been upgraded to version 7.0 or 2000 from a previous version, then you must run the following stored procedure in SQL Server to set the database compatibility level to 70 for SQL Server 7.0 or 80 for SQL Server 2000:

sp_dbcmptlevel [database name], 70 (or 80)

For example:

sp_dbcmptlevel RequisitePro, 70

The above procedure is required to prevent SQL Server Syntax Errors in RequisitePro.

For more information, see the Configuring SQL Server for RequisitePro document (SQLSetup.html).

Upgrading to a Microsoft Access 2000 database

Microsoft Access 2000 is the default database format for RequisitePro version 2000.02.10 and later. If you have a project that was created in an earlier release of RequisitePro, the project database is in Microsoft Access 97 format. If you want to view a RequisitePro project from a previous release in Microsoft Access 2000 or 2002, you must upgrade the project database to Microsoft Access 2000.

Rational has provided a utility to convert Microsoft Access-based RequisitePro projects from Access 97 format to Access 2000 format. The utility "RqAcc2KConv.exe" can be invoked by either dragging and dropping the RequisitePro project file (.rqs) onto the executable, or running the utility from the command line and specifying the entire path to the RequisitePro project file (.rqs) file. As part of the conversion process, the utility creates a backup copy of your database with the .tac extension instead of the .mdb extension. The backup copy can be removed when you are satisfied that the conversion was successful. The utility also repairs and compacts the database.

Compatibility Issues

With Rational Tools

ClearCase
ClearCaseLT
ClearQuest
Rational Administrator
XDE
Rose
Rational E-Mail Reader (mailreader.exe)

Using ClearCase UCM with RequisitePro

• If you are using full ClearCase, we recommend that you use dynamic views for faster performance.
• We do not recommend using UCM with RequisitePro projects that use Microsoft Access. (RATLC00057435)
• A project created from a baseline does not maintain the cross-project traceability links, discussions information, and associations with Rational ClearQuest and Rational Rose from the original baselined project. (RATLC00058743)
• When you open a RequisitePro document in a project that was created from a baseline, you are notified that the document was modified outside of RequisitePro. You can accept this message and then save the document. (RATLC00058744)
• The UCM-RequisitePro integration does not work with a full ClearCase client and server that are configured as case sensitive or configured as case insensitive/not case preserving. The setting case insensitive/case preserving works properly. (RATLC00016087, RATLC00057970)
• If you use Unified Change Management (UCM) with Rational Suite under these conditions:
  • You use Rational ClearQuest to manage UCM activities, and
  • You place a RequisitePro project under configuration control
  then make sure that you do not set the UCM policy, "Check Assignment Before Work On". (The default is for the policy not to be set.)
  When you set the policy, you cannot work on an activity unless you are the owner of that activity. In the current implementation of UCM for RequisitePro, an entire team of workers share the same activity. Therefore, if the policy is set, only one person, not the entire team, can work in a RequisitePro project.
  If the policy is set by mistake, the error message "Source control could not set activity" appears. To work around this error, in the Rational Administrator, connect to a Rational project, right-click the UCM project, and click Properties; on the ClearQuest tab, unset the policy. (RATLC00044075, RATLC0006066, RATLC00045844)

Using ClearCase LT with RequisitePro

To improve performance, consider the recommendations below when you create a baseline of a RequisitePro project with ClearCase LT.

• Run the Check in All from the machine with the snapshot view storage location. Depending on your network configuration, this machine may also be the ClearCase LT server, or it could be a separate file server.
• Keep the size of individual RequisitePro project documents below 1 MB.

Using ClearQuest with RequisitePro

For information about upgrading Rational Suite or the RequisitePro-ClearQuest integration, see the manual Rational Suite Installation Guide and the Rational Suite Release Notes. For information about configuring the integration, see the manual Rational Suite Administrator's Guide. (Both manuals are available in an electronic version on the Rational Solutions for Windows Online Documentation CD and on the Rational Software documentation Web site: http://www.Rational.com/documentation/.)

• If the Administrator username and password are different for ClearQuest and RequisitePro, you may not be able to set up the integration. (RATLC00056478)
• When implementing the ClearQuest-RequisitePro integration in a ClearQuest MultiSite environment, each user must connect to only one master schema repository. If the alias is modified to point to another site (or mastership is owned by another site), the ClearQuest-RequisitePro integration will not work properly. (RATLC00015464)
• Use Universal Naming Convention (UNC) paths when setting up the integration in Rational Administrator, the RequisitePro-ClearQuest Integration Wizard, or the ASCQISetup.bat file. Using mapped drive letters yields inconsistent results. (RATLC00058533)
• Data code pages and character set compatibility with ClearQuest:
  You may see an error message about data code pages if your RequisitePro project is integrated with ClearQuest. The error message appears when you enter data into a tool and the characters you use are incompatible with the set of characters that a ClearQuest database accepts.
  For example, say that you are working in a RequisitePro project that is integrated with a ClearQuest database, and the ClearQuest database accepts characters in English only. If you use English to enter RequisitePro data, the error message does not appear. However, the error message does appear if you use another character set, such as Japanese or Chinese.
  If you see this error message, consult your ClearQuest administrator or systems administrator to resolve the character set incompatibility.
• Even if your administrator has configured the correct code page, you may receive an unspecific error message stating that the ClearQuest-RequisitePro association cannot be saved. This may happen if you type characters that are not in the code page or if you install RequisitePro on a directory with characters that don't match the code page. (RATLC00443827)
• The RequisitePro-ClearQuest Integration Wizard may not appear in the task bar or the running application list. (RATLC00057833)
• Using the ClearQuest-RequisitePro integration when you have selected multiple records in ClearQuest will cause errors. Use the ClearQuest-RequisitePro integration with one ClearQuest record at a time. (RATLC00014777)
• To successfully use the same Microsoft Project schedule with both RequisitePro and ClearQuest, do not select 'Text4, 'Text5' or 'Text6' for 'Assign Custom Fields' in the Rational ClearQuest Project Tracker. (RATLC00016402)
• The ASCQISetup.bat fails if there are multiple connections to ClearQuest repositories. (RATLC00058048)

Using Rational Administrator with RequisitePro

If you have installed RequisitePro as a stand-alone product, the Tools > Rational Administrator command in RequisitePro is not available. However, Rational Administrator is installed with RequisitePro and is available from the Start Menu Rational Software group. (RATLC00058650)

Using XDE with RequisitePro

Platform Issues

Supported platforms for RequisitePro may not be the same as supported platforms for XDE. See the Rational XDE release notes for supported platforms for Rational XDE. (RATLC00057826)

Installation Issues

If you are using a version of XDE that is older than 2003, the Rational RequisitePro-XDE Integration does not work with RequisitePro version 2003.06.00.

XDE Start Preference

You can use the Options dialog box (click Tools > Options) to select the Rational XDE edition on your system that you want to open when you use the XDE integration commands in RequisitePro. You can use more than one edition of XDE with the integration, but only one can be designated to open automatically from RequisitePro when no edition of XDE is open on your system. Only users with operating system-level administrator rights can change the Start Preference for the change to take effect. (RATLC00058758)

ODBC Error

You may receive an ODBC error when creating traceability from an element in XDE to Rational RequisitePro. The error appears after clicking OK on the Requirements Properties dialog box. After you accept the ODBC error message, the RequisitePro explorer is unavailable and does not respond. You must close RequisitePro using the Windows Task Manager. The association for the XDE model element is not created. This happens only during the first association of an element. (RATLC00058433)

Navigational Issues

• For best results, do not start other XDE or RequisitePro operations while the integration operation is in progress (RATLC00057103)
• You cannot open an associated use-case document in XDE by right-clicking or double-clicking the document's generic Windows file icon in the Model Explorer. You can open the associated document by right-clicking the use case itself in a diagram or in the Model Explorer and clicking RequisitePro > Document > Open. (RATLC00017013, RATLC00017014, RATLC00017090, RATLC00056225)
• When associating a requirement to a use case, XDE does not navigate to the selected model automatically. Select the model in the Model Explorer to open it. (RATLC00017218)

Menu Issues

• If XDE stops responding, an instance of devenv.exe is still active. This prevents the RequisitePro integration menus from appearing in XDE. To fix this problem after XDE stops responding, do one of the following: reboot your machine, or open the Task Manager and remove devenv.exe instances. (RATLC00056756)
• Invalid context menu options may appear in the RequisitePro shortcut menu in XDE. The menus may need to be refreshed. Click another model element and return to the original selection to refresh the menus. (RATLC00017320, RATLC00057104)

Help System Requirements

The navigation capabilities of the Rational RequisitePro-XDE Integration Help system require that your browser support Java applets. If the left hand pane is blank or displays an error message, your Microsoft virtual machine may be damaged (Microsoft Knowledge Base Article - 305674), you may be trying to run a Java applet across a firewall, or you may have another compatibility problem. Contact the designated support site for your browser to resolve these kinds of issues.

Undo and Redo Functionality

If you are using the Rational RequisitePro-XDE Integration, the XDE Redo command does not apply to disassociation and cut actions. The XDE Undo commands and ClearCase Undo Check Out commands do apply to association and paste actions. (RATLC00056556)

Offline Documents with Different Versions of XDE

If you use RequisitePro version 2002.05.00 to change the name of a requirement and then take the document containing that requirement offline, changes made to the requirement name in the database using RequisitePro version 2002.05.00 while the document was offline are discarded when you bring it back online using RequisitePro version 2003.06.00. To avoid this situation, take one of the following measures:

• Use RequisitePro version 2003.06.00 for any documents with requirements associated to XDE version 2003.06.00 model elements. Use RequisitePro version 2002.05.20 for any documents associated to XDE version 2002.05.20 model elements.
• Save documents in RequisitePro version 2003.06.00 prior to taking them offline.

(RATLC00056189)

Unsaved XDE Models

Save all XDE for Visual Studio .NET models before you associate model elements with RequisitePro. (RATLC00058453)

Rational Administrator Projects and XDE

You cannot use Rational Administrator to integrate XDE models with RequisitePro projects. After you convert your Rose models to XDE models and migrate their RequisitePro associations to the new XDE models, any references to those Rose models in a Rational Administrator project become obsolete. We recommend that you remove any references to Rose models in Rational Administrator projects if the Rose models have been migrated to XDE models. (RATLC00017161)

Converting Rose Models to XDE Models

You cannot migrate an existing integration with a RequisitePro project from Rose to XDE by using the File > Import command. This command converts the Rose model to an XDE model but does not migrate any associations to RequisitePro. To migrate associations, follow the instructions in the topic "Migrating RequisitePro associations from a Rose model to XDE model" in the Rational RequisitePro-XDE Integration Help, which can be accessed by clicking Tools > Rational RequisitePro in Rose or XDE. (RATLC00016923)

Using Rose with RequisitePro (Integrated Use Case Management)

• Using more than one instance of Rose: To avoid possible errors, use the RequisitePro integration with a single instance of Rose open. (RATLC00058187)
• Remote Server: If you get the "remote server machine does not exist" error message while you are creating a requirement from Rose, you can ignore the message. The requirement is still created. To avoid other error messages, close and reopen Rose. (RATLC00021744)
• Rose RealTime: The Rose RealTime-RequisitePro integration does not support the association of a Rose RealTime package with a RequisitePro project. The use-case and model association is supported. (RATLC00016065)
• Saving Controlled Packages in Rose: This issue involves Rose models that use version control with ClearCase and integrated use cases with RequisitePro. If you have unsaved changes within a controlled package and attempt to check in that package, ClearCase prompts you to save your changes, but RequisitePro does not recognize the save operation. When you subsequently close the Rose model, RequisitePro removes all changes since your last recognized save operation. As a result, the use-case information in Rose and RequisitePro may not be synchronized. To avoid this, be sure to save the controlled package in Rose before checking it in to ClearCase. (RATLC00017953)
• Changing Packages: In Rose, if a use case contains an association to a RequisitePro use-case requirement and you move the use case to a different package in Rose, the association is lost. In this case, you must reestablish the association. Right-click the use case and click RequisitePro > Requirement > Associate. (RATLC0017836)

Rational E-Mail Reader (mailreader.exe)

• If you install RequisitePro as a point product, the complete Rational E-Mail Reader files are not installed because of an install directory change after Rational E-Mail Reader version 2002.05.20. If you attempt to open mailreader.exe, an error message states that expected .dll files are not present. In order to resolve this issue, install Rational ClearQuest 2003.06.00 on your system. Rational ClearQuest 2003.06.00 may be installed separately or as part of a Rational Suite product. No license is required for ClearQuest. (RATLC00694844)
• Each RequisitePro project must have a unique e-mail address associated with each project, and that address should be used only for the Rational E-Mail Reader.
• Removing a project from the Rational E-Mail Reader does not remove the "mail" reference in the RequisitePro .rqs file. The RequisitePro project must be closed when configuring the Rational E-Mail Reader. (RATLC00058245, RATLC00058073)

With Third-Party Products

RequisitePro Conflict with Crystal Reports

After installing Crystal Reports version 8.0, users who are not local administrators may receive the following error message when starting RequisitePro:

"Unable to load the RequisitePro GeneralServices.Files Component.
Class not registered (HRESULT REGDB_E_CLASSNOTREG)"

After this message is displayed, RequisitePro immediately closes. This error is caused by a change to the default security permissions on several registry keys by Crystal Reports. For more information, see Microsoft Article Q266621 in the Microsoft online Knowledge Base. To resolve this problem, reset the registry key permissions that are changed when you install Crystal Reports. A utility that resets the registry key permissions is available from Crystal Decisions:

http://support.crystaldecisions.net/communityCS/FilesAndUpdates/scr8_webregfix.exe.asp

This third-party contact information is subject to change without notice. (RATLC00017845)

With International Systems

RequisitePro has been enhanced for teams that work across time zones. RequisitePro documents now use GMT time stamps to eliminate inconsistencies.

RequisitePro is supported on the following international operating systems: French, German, Japanese, Italian, Swedish, Simplified Chinese, Traditional Chinese, Dutch, Hebrew, and Korean.

Users can enter text and data using their native language and corresponding character set on the following operating systems: French, German, Japanese, Italian, Swedish and Simplified Chinese. Regional date, time, and number conventions, as specified by the user's selection of regional settings on the Windows control panel, are also supported for both input and output.

Users with Hebrew, Korean, Traditional Chinese and Dutch operating systems must enter all input data (such as path names and project data) using U.S. English.

For all international systems listed above, screens, menus, controls, wizards, reports and user documentation are in U.S. English.

Note that internationalization assumes homogeneous language environments; for example, a French operating system using French versions of SQL Server and Microsoft Word.

Internationalization Issues

• When you create RequisitePro schemas or databases on international operating systems, non-ASCII characters are not supported for passwords for SQL-Server- and Oracle-based projects. (RATLC00014648)
• If you create a project on an international system from one of the RequisitePro project templates, you may not be able to move it to another database using the Data Transport Wizard. We recommend that you create the project directly in the targeted database, rather than attempt to move it after it is created. (RATLC00016229)
• When moving RequisitePro projects between databases, all characters in the database must be supported in the code page of the system from which the Data Transport Wizard is run. (RMBU12011)
• In some languages, Excel and other products use a separator other than a comma when saving data as comma-separated value (CSV) files. If your language uses semicolons and you want to import a CSV file created from Excel to RequisitePro, change the semicolon separators to commas so that the requirements to import correctly. (RMBU11775)
• When you run queries and the decimal separator and thousand's separator are different from the default of the language, Visual Basic conversion routines fail. (RMBU11423)
• On German systems, clicking Insert > Picture (or the IncludePicture Microsoft Word field) in a requirement fails. Click Insert > Object (Link field) instead. (RATLC00016076)
• Non-Japanese double-byte characters do not appear properly in a Microsoft Word document after an export of requirements from an Attribute Matrix. To correct the problem, open the Word document, select all text, and select a new font. (RMBU13808)
• Using the Microsoft Word highlight style option for importing requirements does not work for double-byte systems. (RATLC00016298)
• On Korean and simplified Chinese systems, requirements in documents may be concatenated after cut, paste, and Rebuild Tags operations. This applies to all projects created on systems other than Korean and simplified Chinese, including the sample projects. (RMBU15540)
• Because of a limitation with the Rational E-Mail Reader (mailreader.exe), the only double-byte language system that is supported for participation e-mail (inbound and outbound) is Japanese. (RATLC00058289)

Restrictions and Guidelines on Using RequisitePro

Microsoft Word Issues

Text Boxes and Stories in Word

• Avoid creating requirements inside text boxes. RequisitePro cannot access them properly.
• If you are using the story capability in Word, do not use bookmarks (including requirements) outside of the main story. (RATLC00439909)

Special Characters in Word

Do not create requirements from text that contains the Wingdings font or other special characters at the beginning of the text string. (RATLC00016311)

Macros and Macro Security

• RequisitePro does not support Word customized macros. (RMBU10108)
• If you are using Word 2000 or 2002 and choose to clear the Trust all installed add-ins and templates check box on the Security dialog box (click Tools > Macro > Security to open), you must click Enable at the Microsoft Word message box each time you open Microsoft Word. (RMBU11361)

Protecting Word Documents

Do not use a password when protecting RequisitePro Word documents with the Microsoft Word Tools > Protect Document command. (RATLC00016802)

Refreshing Requirements

RequisitePro contains a Refresh Requirements command (available when you click RequisitePro > Document) that lets you reset the style and color of all requirement text in a document in case you inadvertently change it. However, if you change the color of any requirement text using Word 2000 or 2002, the color cannot be reset using the Refresh Requirements command. To refresh requirement text color, save the document and then select the Refresh Requirements command. (RMBU5359)

Nontextual Requirements

You cannot edit the requirement text outside the document (even when the extended editing feature is enabled) if you include the following in the text of a requirement located in a document:

• OLE objects
• Fields (for example, author, title, subject)
• Pictures (both inline and floating)
• Tables
• Annotations (comments, footnotes, bookmarks, hyperlinks)
• Subdocuments
• Lists containing more than a single item (including bulleted and numbered headings or other styles, both sequential and outline)

Windows NT Fonts

If characters in RequisitePro are replaced with a vertical bar, Windows NT users should change the Windows default font to something other than MS Sans Serif (Tahoma is recommended). (RATLC00057929)

Configuring E-Mail

• Performance of e-mail notification using the MAPI protocol is inconsistent on similarly configured Windows 2000 and Windows XP machines running Office 2000 and XP. E-mail notification works on some systems but not others. Error messages are generated when attempting to send e-mail notification messages. RequisitePro uses Microsoft Outlook as the default e-mail system. To avoid the problems, install the Microsoft Outlook Collaboration Data Objects feature. For more information, see Rational Solution #22376. (RATLC00058562)
• For issues related to the Rational E-mail Reader (mailreader.exe) see the Rational E-Mail Reader (mailreader.exe) section.

Offline Authoring

• If you experience problems with the RequisitePro menus when using offline documents, clean all temp files and delete normal.dot.
• In Word 2000 and 2002, you may need to adjust your macro security levels to use the Create and Delete commands (available when you click RequisitePro > Requirement) in offline authoring. By default, Word 2000 is set at the highest level for macro security. This setting prevents the enabling of the RequisitePro offline authoring macros. Reset the macro security in Word 2000 to medium on the Security dialog box, which is available by clicking Tools > Macro > Security.
• For additional information, see Using Offline Documents with Different Versions of XDE.

Numerical Attributes

RequisitePro does not support a digit-grouping symbol of any kind (for example, a thousand separator, such as the comma in 2,350). You cannot enter attributes with this symbol. RequisitePro does not display numbers with this character. (RMBU6858)

Views and Queries

If a saved view includes a query with a user-defined date field parameter, the date is stored with the saved view in the date format that is set in your Control Panel/Regional Settings/Short Date Style. If you attempt to open a saved view on a PC that uses a different date format (such as dd/mm/yyyy), a run-time error occurs. (RATLC00014609)

Requirement Metrics

The Parent Change filter cannot always detect when a requirement is changed from a root requirement to a child requirement, and vice versa. (RMBU8472)

Known Issues and Change Requests

The following is a list of known issues in this release of RequisitePro. For information about issues related to Rational Suite or integrations with other Rational Products, see the Rational Suite Release Notes.

Opening Sample Projects for the First Time

The first time you open any of the documents in the sample projects (learning projects), you receive a Changed Document message. Click Yes in the message, and the document opens. (RATLC00058991)

Creating Projects

• Do not include extra spaces in front of the project name when creating a project. If spaces are included at the beginning of a project name, RequisitePro cannot find the project to open it. (RATLC00016425)
• Avoid using periods in RequisitePro project names. (RATLC00018417)

Saving Documents

If you change focus while a document is being saved, requirements may retain pending tags in the document. Use the Rebuild Tags command, and the requirement tags are displayed properly in the document. (RATLC00016406)

Assigning Parent Requirements in Documents

To avoid problems when assigning parent requirements, save the document first. If you assign a child requirement to a parent requirement that has not been saved in a document, an error message appears and you must select the parent again. To avoid further problems, select the parent requirement from the Parent list in the Requirement Properties dialog box; do not select the choose parent option. (RATLC00016426)

Importing Requirements

• If you cancel the Import Wizard on the Commit screen, you can only close RequisitePro through the Windows Task Manager (CTRL-ALT-DELETE). (RATLC00020644, RATLC00016213)
• When importing a document, if the first word of the document is the keyword used for identifying imported requirements, this first occurrence does not appear as a requirement in RequisitePro. (RATLC00018111)
• When importing a document, if you attempt to create a requirement using text that contains a Microsoft Word MACROBUTTON field, a run-time error occurs in RequisitePro. (RATLC00017620)

Renumbering Requirements

When renumbering requirements in a RequisitePro project, if the first requirement is located in a document and if you choose to start the renumbering by an order of magnitude less than the current numbering (for example, 60 rather than 6000), the first requirement does not get renumbered. To fix this condition, renumber the requirements again using a new starting number, cut and paste the starting requirement from the document into the database and then back into the document, or manually edit the requirement tag in the document. (RATLC00017529)

External Projects

• You may receive "Out of Memory" error messages when using requirements in external projects. You can reduce the possibility of memory errors by doing the following: connect to external projects only when you need to use them, filter views to display only the external requirements that you need, and close views that contain external requirements when you are not using them. (RATLC00056798)
• When removing an external project, views that include requirement types from the external project are no longer valid and should also be deleted. All references to those external requirement types are broken in views, even if you add the external project again. (RATLC00058041)
• Using the Save As command for a view that uses an external requirement type inappropriately converts the external requirement type to the first requirement type of the opened project. (RATLC00057989)

RqCallback.dll

A new library, RqCallback.dll, can be used when extending Rational RequisitePro through the IReqProGUIApp type library. This .dll encapsulates the callback parameter required by many of the IReqProGUIApp methods, and allows the client to listen to events raised by RequisitePro. This .dll is not described in RequisitePro Extensibility Interface Help. (RATLC00058527)

Let's Go RequisitePro

If you open Let's Go RequisitePro from the Start menu and then close it, in all subsequent sessions of Let's Go (when launched from the Start menu) the link to the RequisitePro release notes fails. However, Let's Go appears when RequisitePro opens, and it is also available from the RequisitePro Help menu. In both these contexts, the link to the release notes is successful. The link fails only when Let's Go is launched from the Start menu. (RATLC00058281)

Contacting Customer Support

See the following Web site: http://www.rational.com/support/.

If you have questions about installing, using, or maintaining this product, contact Rational Customer Support as follows:

When you contact Rational Customer Support, please be prepared to supply the following information:

• Your name, company name, telephone number, and e-mail address
• Your operating system, version number, and any service packs or patches you have applied
• Product name and release number
• Your case ID number (if you are following up on a previously reported problem)

RequisitePro User Community

Requirements management discussions are available on the Rational Developer Network. Go to http://www.rational.net to participate in the discussions.