Rational RequisitePro
Version 2000.02.10

Section 2: Getting Started with RequisitePro

Section 3: Known Issues and Incompatibilities

Section 4: Contact Information

Section 1: What's New in RequisitePro

Requirement Authoring via the Web

Rational continues to make requirements even more accessible by providing requirements authoring via the Web. RequisiteWeb is no longer a separate product, but is included as a component of RequisitePro. With RequisiteWeb, you can now modify the text of all requirements and create, modify, delete and re-parent requirements that are not located in documents - all through the Web. All changes are automatically tracked, just as they are from the Windows client. Requirement authoring via the Web allows better support of distributed teams and multiple-platform environments.

In-View Editing

Directly within an Attribute Matrix view, you can now edit and create requirements. Simply click on a selected requirement in the view to start editing the requirement text in place. Create new requirements directly in the view without having to go through a dialog box.

Extended Editing

Extended Editing of documents allows you to change requirement text outside a document: from a view, from RequisiteWeb, from the RequisitePro Extensibility Interface, or from integrated tools. You can now update requirement text without having to open the document. This allows multiple people to simultaneously edit requirements within a single document. All changes are still tracked in the database.

Security Enhancements

Traceability: You can now set security specifically on traceability relationships, giving you better control over who on the project can modify traceability. Permissions on traceability are set by requirement type. There are four traceability permissions: Create, Delete, Mark Suspect, and Clear Suspect. Users must have the appropriate permission on requirements on both ends of the relationship to perform the selected action.

Requirement Text: You can now set security on requirement text. For example, you can select user groups that can modify other requirement attributes but not requirement text.

Group Permissions Default: When you add a new security group in an existing RequisitePro project, the group has all security permissions by default. You can remove permissions using the Edit Permissions buttons in the Group Permissions dialog box.

New RequisitePro Extensibility Interface Features

The following documented features have been added to the RequisitePro Extensibility Interface:

In addition, new values have been added for the following constants:

• enumPermissions
• enumPermissionTypes
• enumRequirementDeleteFlags
• enumRequirementFlags

For the Project, Requirement, and Requirements objects, the Delete method has been replaced by the DeleteRequirementHierarchy method.

Additional documentation has been added to the online help regarding accessing the RequisitePro GUI Type Library using the GetObject.

Improved Integrated Use Case Management

The integrated management of use cases between Rational Rose and Rational RequisitePro has been improved in this release allowing users to start or work in either environment -- according to your process.

Integrated Use Case Management allows Rational Rose and RequisitePro users to consistently and seamlessly manage all use case artifacts: specification documents, attributes, traceability, and diagrams from either the Rose or RequisitePro environment. Previously, you could create and associate requirement documents and properties with use cases from within Rose. This integration has been improved to allow you to create and update use cases items in Rose from their associated requirements and use case specifications in RequisitePro.

Improved Rational ClearQuest/RequisitePro Integration

Understanding the details and context of an enhancement request that is associated with a requirement is now just a click away. Previously, you could associate and create requirements from an enhancement request in ClearQuest. Now, from RequisitePro, you can associate enhancement requests with requirements and navigate directly to the enhancement request record in ClearQuest.

For information on configuring this integration, refer to Chapter 4 of Configuring Rational Suite, available on the Rational Documentation CD.

Internationalization

RequisitePro is internationalized to support international operating systems and applications. In addition to French, German and Japanese, RequisitePro now supports:

• Italian, Swedish, and Simplified Chinese
  Users are able to enter text and data using their native language and corresponding character set on Italian, Swedish, and Simplified Chinese operating systems. Regional date, time, and number conventions, as specified by user's selection of regional settings on the Windows control panel, are also supported for both input and output.
• Traditional Chinese and Dutch
  RequisitePro 2000 is capable of installation and use on Traditional Chinese and Dutch operating systems, and it has been tested to assure conformance. Users must enter all input data (such as path names) using U.S. English.

For all international systems listed above, displays, 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.

Miscellaneous Enhancements

• Attributes can now be marked as "Hidden from display" so that they are hidden from general RequisitePro users in the Views Workplace and in the Requirement Properties dialog box.
• Block Create function now saves previous criteria and requirement properties as defaults; allows selection of all sentences or paragraphs by specifying a wildcard.
• RequisiteWeb users can set their user preferences including e-mail, passwords, and display options.

Archiving

RequisitePro teams use a variety of configuration management tools for archiving projects. Because of this, the PVCS Version Manager and Visual SourceSafe commands have been removed from the Project > Archive menu. You can continue to use these and other configuration management tools to archive your projects from within those configuration management environments. First use the RequisitePro Archive command to create an archive or each file; then archive these files using your configuration management tool.

The RequisitePro Archive and Rational ClearCase commands are still included on the Project > Archive menu.

The RequsitePro Archive command now is available for projects with Access, Oracle or SQL Server databases. Using the RequisitePro Archive command copies all project documents into a user-specified archive directory. Database administration online help is available for archiving Oracle- and SQL-Server-based projects.

Archiving RequisitePro projects with ClearCase is now similar to archiving with the RequisitePro Archive command. The many ClearCase-specific dialog boxes have been replaced with a simpler dialog box.

Updated Templates

In this release, the rup_fcnltst.def and rup_fcnltst.dot templates were renamed to fcnltst.def and fcnltst.dot. When you open a project created in a previous version of RequisitePro, select the updated outline "Functional Test Case Specification" in the Document Type dialog box.

Section 2: Getting Started with RequisitePro

Compatible Applications

RequisitePro is compatible with:

• Rational ClearCase, version 4.0
• Rational TestManager, version 2000.02.10
• Rational Rose, version 2000.02.10
• Rational SoDA for Word, version 2000.02.10
• Microsoft Project 98 and 2000
• Microsoft Excel 97 and 2000
• Microsoft Word 97 and Word 2000
• Oracle, version 7.3.4 and 8i
  (Note: Oracle 8i is not certified for use with Windows 2000)
• Microsoft SQL Server 7.0

RequisitePro Folder or Group

RequisitePro setup creates a Start menu program group for RequisitePro with the following items: Let's Go RequisitePro, Online Help, Rational License Key Administrator, Rational RequisitePro, Rational Software Installed Product Information, Rational Synchronizer, Release Notes, and Technical Support.

To start RequisitePro, select the Rational RequisitePro menu item.

Let's Go RequisitePro

Use the Let's Go RequisitePro feature to access getting started online help as well as these release notes, white papers, the Rational Unified Process, and Web resources.

Let's Go RequisitePro appears when RequisitePro is first launched. It can also be launched from the RequisitePro Help menu.

Section 3: Known Issues and Incompatibilities

The following is a list of known issues and incompatibilities with RequisitePro and auxiliary applications.

Upgrade Issues

Shared files and components

During the Rational Software Setup, the Upgrade Compatibility dialog box appears if you have additional, older, Rational products installed on your system. Because Rational tools share files and components, this installation can cause the older Rational products to stop working. You will see no visual clue to indicate that the older products may be compromised.

For each of the additional, older products listed, we strongly recommend that you take one of the following actions:

• Upgrade it: Complete this installation, and then restart the Setup wizard to upgrade the next product. Upgrading a product updates all necessary files, registry entries, startup menu items, and shared components on your system.
• Remove it: Complete this installation, and then use the Control Panel's Add/Remove Programs tool to remove the next product. Removing a product deletes files, registry entries, and startup menu items from your system.

A Web site exists to provide more details about interactions between specific products. To visit the Web site, please see http://www.rational.com/sitewide/support/index.jtmpl. Click Patches and Upgrades, and then click Upgrade Compatibility.

Upgrading from RequisitePro 4.5

If you are upgrading from RequisitePro 4.5 and have not uninstalled 4.5 and removed the RequisitePro 4.5 installation folders, you should remove the reqpro.gid and letsgo.gid files from the \Rational\RequisitePro 4.5\help directory if they are still present. (11427)

Upgrading to a Microsoft Access 2000 database

Microsoft Access 2000 is the default database format for RequisitePro version 2000.02.10. If you have a project that was created in a previous 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, you will need to upgrade the project 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 will create a backup copy of your database with the .tac extension instead of the .mdb extension. The backup copy can be removed once you are satisfied that the conversion was successful. The utility will also repair and compact the database.

Running RequisitePro on Micron Systems

If you experience problems running RequisitePro on Micron systems, contact Rational Technical Support for a technical note relating to the issue. For additional information contact Micron PC Technical Support at: http://support.micronpc.com/contact/support/.

Numerical Attributes

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

Dialog Boxes and Wizards

If a dialog box or wizard in RequisitePro appears to stop responding, a hidden error message may be displayed behind the dialog box. Drag the box to another part of your screen to see if a hidden error message is displayed. Respond to the error message and continue. (11979)

Traceability History

When you mark the "Traceability/Changes logged in history" check box on the Tools > Options dialog box, changes to requirement traceability appear on the revision history list in the requirement properties dialog box. However, traceability changes caused by the MS Project Integration wizard are not logged in the revision history. (6019)

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. The same error occurs if the saved view is part of a project that you are using as a template for creating a new project on a PC that uses another date format. (8328)
• In RequisitePro projects that use a Microsoft Access database, you may experience a 5-to-10-second delay between entry of data and display of the modified data. This is due to defects in Microsoft MDAC components, which RequisitePro uses in querying data in Access databases. For example, if you create or modify a requirement, and then run a query for all requirements of that type, the new or modified requirement may not be displayed until after a delay. (2189)

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. (8472)
• Close Requirement Metrics before you close the RequisitePro project. (7302)
• If your Requirement Metrics report has multiple queries and contains a traceability change query, the results of other queries may not be correct (11894)

RequisitePro Extensibility Interface

The color and style set through the RequisitePro Extensibility Interface are off by one index number. To set the color and style correctly from the extensibility interface, use enum - 1. (11746)

Offline Authoring

• If you experience any difficulties with offline authoring, clean all temp files and delete normal.dot.
• In Word 2000, you may need to adjust your macro security levels to use the Requirements > Create and Delete menu commands in offline authoring. Word 2000 defaults to 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.

Microsoft Word Issues

Text Boxes in Word

Avoid creating requirements inside text boxes. RequisitePro cannot access them properly.

Tables in Word

Avoid creating requirements inside tables. (11967)

Customized Macros

RequisitePro doesn't support Word customized macros. (10108)

Revision Numbers in Word

When saving RequisitePro documents, Microsoft Word records the revision number for all revisions as "2." This revision number is available on the Statistics tab of the document Properties dialog box, which is accessed from the File menu using the Properties command. This revision number does not affect the document revision information in RequisitePro, which is available on the Revision tab of the Document dialog box. This dialog box is accessed from the RequisitePro Document menu using the Properties command. (1826)

Importing Word Documents with Existing Formatting

If you are importing a Word document that uses a template other than Word's normal.dot template or an existing RequisitePro outline, you should set up that template as a RequisitePro outline prior to importing the document. RequisitePro will overwrite any unrecognized formatting with the normal.dot formatting.

If you have customized the formatting within the Word document, you should save the document as a Word template and copy it to the RequisitePro outlines directory. Refer to the Microsoft Word documentation for help in creating Word templates. Refer to the RequisitePro online help topic "Creating outlines" for help in managing RequisitePro outlines.

Hidden Text in Requirements

RequisitePro will not create a requirement if the block of text and/or images highlighted contain hidden text at the beginning or end of the selection. This occurs because RequisitePro uses hidden text at the beginning of a requirement to assign a requirement tag number and at the end of a requirement to store formatting information about the requirement.

Do not type information within the hidden part of a requirement, as the information is formatted as hidden. If the requirement is deleted, the information you typed is deleted as well.

Protect for Revisions

If Protect for Revisions is turned on automatically in RequisitePro documents due to reqistry permissions problems, do the following: Run regedt32, select the HKEY_LOCAL_MACHINE and select Security > Permissions. Assign Full permissions to the Everyone user. (10205)

Word 2000 Issues

• RequisitePro contains a Refresh Requirements command on the Document menu that allows you to 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, the color cannot be reset using the Refresh Requirements command. To refresh requirement text color, close the requirements document and reopen it, and then select the Refresh Requirements command. (5359)
• If you are using Word 2000 and choose to clear the Trust all installed add-ins and templates check box on the Tools > Macro > Security dialog box, you must click Enable at the Microsoft Word message box each time you open the RequisitePro Word Workplace. (11361)
• If you are using Word 2000, copying Word picture objects from an external Word document to a RequisitePro document more than once will cause errors in RequisitePro. A patch is available from the Rational Web site: http://www.rational.com/support/downloadcenter/upgrades/reqpro.jsp.(11762)

Non-Text Requirements

If you include the following in the text of a requirement located in a document, you will not be able to edit the requirement text outside the document (even when the extended editing feature is enabled):

• OLE objects (both embedded and linked)
• Fields (e.g., 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)

Enterprise Database Issues

• By default, when Oracle databases are created on UNIX systems, the Oracle character set installed is incompatible with Microsoft Word's extended characters. This incompatibility prevents proper storage of special characters in RequisitePro requirement text and causes requirements to be marked as "modified" in documents. The required character set is WE8ISO8859P1. For more information, contact Rational Technical Support.
• The Microsoft ODBC driver is not compatible with the Oracle 8.1.5 client. To avoid this problem, install the Oracle 8.0.5 client. Refer to Microsoft Knowledge Base article Q239719. (6050)

Internationalization Issues

• When configuring SQL Server, do not mark the check box "Change the language of SQL Server system messages to..." The use of this check box prevents users from opening the RequisitePro project after its initial creation. (10411)
• The Rational E-Mail Reader doesn't accept project names that use doublebyte characters. Therefore, participation e-mail cannot be enabled for those projects (11773)
• Note that Excel and other products use a separator other than a comma when saving data as comma-separated value (CSV) files. To import a CSV file created from Excel to RequisitePro, you must change the semicolon separators to commas for the requirements to import correctly. (11775)
• When running queries, the decimal separator and thousand's separator are different from the default of the language, Visual Basic conversion routines fail. (11423)
• On Japanese systems, if you are importing requirements from a Microsoft Word document based on a style, the import may fail. (11792)
• If you switch keyboard settings while you are creating requirements, both RequisitePro and Microsoft Word stop responding. (11399)

Let's Go Display

• The graphical heading banners and icons in Let's Go RequisitePro may be distorted when displayed on PCs with the 256 Colors display setting. For clearer graphics, set your display properties to High Color (16 bit) or the True Color (24 or 32 bit) settings. (11573)
• For best results when opening PDF files from Let's Go, make sure you are using Acrobat Reader version 4.0. This version of Acrobat Reader is shipped with RequisitePro. (11837)

Integrated Use Case Management

• If you access the Rose Use Case Specification dialog box from RequisitePro (using the Go to Rose command) and change the use case name, clicking either the Apply and OK buttons in the dialog box will cause Rose to stop responding. To avoid this, access the dialog box from Rose when you want to change the use case name. (10755)
• Currently, you can create a requirement in a RequisitePro document from a Rose use case using Integrated Use Case Management, even if extended editing is not enabled. However, unless extended editing is enabled, you cannot modify the text of the requirement. (11790)

ClearQuest Integration

• If you are upgrading an existing "Studio" schema from ClearQuest version 2.0 to ClearQuest version 2000.02.10, an additional Requirement tab appears on the EnhancementRequest and Defect record forms in ClearQuest. This tab can be removed through ClearQuest Designer. (The tab that should be removed only has a "Requirement" field. The tab that should remain contains both a "Requirement" field and a "Tag" field.) (11912)
• If you are upgrading from a Rational Suite version 1.5, and you have ClearQuest records associated with RequisitePro requirements that have been deleted, you will receive error messages about the ClearQuest requirement proxy while you are running the ASCQIupgrade.exe. Note the record number, click OK and complete the upgrade. Then open the record in ClearQuest, remove the deleted requirement from the Requirement tab. Query on all Requirement records in ClearQuest, open the appropriate Requirement record, and delete it. (12015)
• In order for ASCQISetup.bat to run correctly for Windows 98 systems, do the following: In the MS-DOS window, select the Properties menu command to open the MS-DOS Prompt Properties dialog box. Click the Memory tab. In the Conventional Memory frame, select the highest value for the Initial environment setting. (10657)
• On Windows 9X systems, when you launch the ASCQISetup.bat, two MS-DOS windows open. One may result in a Windows Kernel32.dll error. Click OK and Launch the ASCQISetup.bat file again. (10866)
• If you are using non-English, special characters, when you launch the ASCQISetup.bat file, the special characters are not sent correctly. Instead, launch each command directly from MS-DOS. Copy each command (excluding REM commands) from the ASCQISetup.bat, paste it into the MS-DOS Prompt window and run each command. On Windows 9X systems, you must use environmental variables for commands longer than 127 characters. (11625)
• When using Oracle for your ClearQuest database, both the Administrator and Client machines must have Oracle 7.3.4 drivers installed.
• When enabling the ClearQuest / RequisitePro integration for network access, locate the help file (CQI.hlp) on a shared drive (network) and reference the path to this file in UNC format. (11961, 11942)
• Use the UNC format in all path fields for all applications that are accessed or shared across a network when enabling the ClearQuest/RequisitePro integration. These applications specifically include the Rational Administrator, the RequisitePro project, the ClearQuest databases, and the ASCQISetup.bat. Additionally copy and paste the UNC path from application to application to avoid encountering path case-sensitivity problems. For the path to the RequisitePro .RQS file, use the path that is stored in the .RQS file. (11876)
• After you have changed associations in ClearQuest, or deleted requirements, manually refresh any open views in RequisitePro (click the Refresh button) to make sure updated information appears in the Associate Enhancement Requests dialog box. (10862)
• When creating a new requirement from ClearQuest, do not click the ellipsis button in Create Requirement dialog box. The applications may stop responding. Once the requirement has been created, you can use the ellipsis button. (11070)
• When you are setting a ClearQuest query in the Query field of the Associate Enhancement Requests dialog box, you must choose a query that contains a ClearQuest ID in order for the integration with RequisitePro to work correctly. (10853)
• When you use the ClearQuest Refresh button on a record in ClearQuest, an error message may incorrectly appear, stating that some requirements don't exist. (11913)
• From within ClearQuest, if you remove an association to a requirement, then change the project reference and add another requirement for the new project in the same session, errors will result. Instead, delete the requirement, commit the changes, before changing the project reference and adding a new requirement. (10897)

Section 4: Contact Information

Rational Software Corporation

Corporate Headquarters:

Rational Software Corporation
18880 Homestead Rd.
Cupertino, CA 95014
Toll-free: 1-800-728-1212
Telephone: 408-863-9900
Fax: 408-863-4120
E-mail: ratlinfo@us.ibm.com

Technical Support

Telephone: 1-800-433-5444 or 408-863-5000 (outside the U.S. and Canada)
Fax: 408-863-4300
E-mail: support@rational.com
Web site: http://www.rational.com

Visit our Web site for more information about us!

RequisitePro Users Mailing List