Eric J. Ostrander's
ClearCase / ClearQuest pages.
RequisitePro, how do I ...
Attributes   |   Databases   |   Discussions   |   Documents   |   Integrations   |   Misc   |   Packages   |   Projects   |   Requirements   |   Security   |   Views/Queries   |   Web
NOTE: The following notes are for my edification only. Any examples given should be verified in the online documentation or with Rational Tech Support before being attempted. Currently RequisitePro Client is only available on Windows. To access ReqPro via UNIX, use the RequisitePro web interface (ReqWeb).
Attributes
List attributes.
Create an attribute.
Set an attribute's value.
Customize attribute values.
Assign requirement, attribute, traceability and/or document permissions.
Databases
Nothing yet.
Discussions
Discussions. (general)
Create a discussion.
Set up email notification for a discussion.
Locate a discussion in a project.
Delete a discussion.
Documents
General.
List document types.
Create a document.
Save a document outside ReqPro.
Open a document.
Move a document.
Create a document type.
Assign requirement, attribute, traceability and/or document permissions.
View and/or print document history.
Delete a documnet.
Integrations
Integrate ReqPro w/ ClearQuest.
Misc
Customize menus.
Packages
Create a package.
Move a package.
Rename a package.
Delete a package.
Projects
Create a project.
Open an existing project.
Archive or baseline a project.
Designate a project prefix.
Add an existing project to the ReqPro project list.
Remove a project from the ReqPro project list.
Create a project template.
Designate an alternate location for project template storage.
Remove a project template.
Print a project summary.
View and/or print project history.
Rename a project template.
Add an existing project template to the list.
Rename a project.
Requirements
Create a requirement.
Create multiple requirements.
Edit a requirement.
Create traceability between requirements.
Delete traceability between requirements.
Clear suspect traceability.
Create a hierarchical (parent/child) relationship.
Delete a hierarchical (parent/child) relationship.
Establish cross-project traceabililty.
Find all instances of a certain requirement type.
Move a requirement.
Enable/disable requirement text editing outside a document.
Designate an existing requirement type as external.
Create a requirement type.
Modify a requirement type.
Delete a requirement type.
Assign requirement, attribute, traceability and/or document permissions.
Renumber requirements.
Rebuild requirement tags in a document.
Hide requirement tags in a document.
View and/or print requirement history.
Export requirements.
Import requirements.
Security
Enable security.
Assign requirement, attribute, traceability and/or document permissions.
Groups.
Set the default logon.
Views/Queries
Create a view.
Rename a view.
Delete a view.
Modify a view.
ReqWeb
Nothing yet.
List attributes.
In ReqPro, double-click on a view, such as "All Features". A matrix will appear with the attributes for each requirement listed to the right.

Back to the Table of Contents.
Create an attribute.
Attributes can be either list-type or entry-type. Attributes allow you to objectify the decision-making process. The values you assign to each attribute help to organize, analyze, and prioritize the requirements in your project. You can add, edit, or remove requirement attributes at any time during your project. The following data types are supported:
* List (single value): A set of values from which a single value can be selected (up to 20 characters); for example, high, medium, or low.
While attributes are a property of a requirement type, attributes are created and modified in the project's Properties sheet. All requirements of a given requirement type carry the same set of attributes. In the project's Properties sheet, under the Attributes tab, click Add.

Back to the Table of Contents.
Set an attribute's value.
The value of an attribute can be reset any time after creation. Open an attributes matrix and double-click on the intersection of the requirement and the appropriate attribute. A pull-down list will appear. See Customize attribute values.
To set multiple attribute values simultaneously, use <shift>-click to select a range of requirements or <ctrl>-click to select several individual requirements. Multiple values can only be set in one attribute column at a time.

Back to the Table of Contents.
Customize attribute values.

Back to the Table of Contents.
Nothing yet.

Back to the Table of Contents.
Discussions (general).
A ReqPro feature that lets you address comments, issues, and questions to a group of discussion participants. Discussions can refer to one or more specific requirements or the project in general. Discussions can be initiated at any time.
In the discussion dialog (Explorer only), high priority discussions have a red exclamation point next to them, and closed discussions have a black X next to them.

Back to the Table of Contents.
Create a discussion.
In the Explorer, go to Tools->Discussions. Click on the Create button. On the General tab, the Subject defines the discussion and the text will be the first comment in the discussion. On the Attributes tab, you can set the discussion priority and status. On the Participants tab, you can add discussion members and optionally restrict the discussion to members only. If a user has email notification enabled, they will automatically get an email about the new discussion. On the Requirements tab, select one or more requirements to be discussed. If no requirement is listed, it's assumed that the discussion is about the project in general.
Even if you limit the discussion to participants only, anyone can read the discussion.

Back to the Table of Contents.
Set up email notification for a discussion.
Any user participating in a discussion via email must have an email address entered in ReqpPro (see File->Project Administration->Security).
In Tools->E-mail Setup, select the appropriate protocol. Each user must complete this if they want to send and rcv email notifications for discussions.
You can also use Rational's email reader. The email is rational-home\common\mailreader.exe on Windows.

Back to the Table of Contents.
Locate a discussion in a project.
If viewing a particular requirement in the Explorer, right-click on the requirement and choose Discussions. In a document, right-click on the requirement, select Requirement Properties, and go to the Discussions tab.
To see all discussions in a project, in the Explorer go to Tools->Discussions. You can click on the Filter button at the top left to isolate discussions based on your own criteria. To sort the discussions, simply click on the header of the column on which you want to base the sort.
In the Explorer, if a requirement has an associated discussion, there will be a little, red triangle on the right side of that requirement's name.

Back to the Table of Contents.
Delete a discussion.
In the Explorer, open the discussion dialog box: Tools->Discussions. Select the discussion to be deleted and click Delete. The discussion must be in the Closed state and can only be deleted by the Author or an Administrator.

Back to the Table of Contents.
General.
In the ReqPro online help, be sure to see "Tips for using Word in RequisitePro".
When working with large documents, ask Rational Tech Support for Technote #2383.

Back to the Table of Contents.
List document types.
In the ReqPro Client, right-click on a project and select Properties. Select the Document Types tab.

Back to the Table of Contents.
Create a document.
In the ReqPro Client only, highlight the package in which you'd like to create the document, such as Use Cases. Select File->New->Document. In the resulting dialog, fill in relevant information. The ReqPro document will be placed in the project's directory on the file system.
You can do a Save As to save a document outside the ReqPro database so that it will be readable by MS Word. Or, you can go to the project's Properties, under the Documents tab, and deselect the "Save documents in RequisitePro format".
The document name must be unique within the project.

Back to the Table of Contents.
Save a document outside of ReqPro.
Documents created inside ReqPro are created inside the associated database. To save the document so that it can be read independent of ReqPro, open the docuemnt within ReqPro. Inside the document, select RequisitePro->Document->Save As.

Back to the Table of Contents.
Open a document.
In ReqPro, if a document appears under a package, simply double-click on it and it'll open. Also, if a requirement is associated with a document, double-clicking on the requirement will open the document as well. However, that feature needs to be enabled. If you are unable to open a document by double-clicking on a requirement in that document, go to Tools->Options and ensure "Double-click to go to source" is selected in the Views section.

Back to the Table of Contents.
Move a document.
In the Explorer, simply drag and drop the document to anywhere else in the package hierarchy.

Back to the Table of Contents.
Create a document type.
In ReqPro, document types do not govern what sort of information is contained within a given document. They merely catagorize documents into manageable groups.
In ReqPro, enter the Properties sheet of the project. Under the Document Types tab, select Add. The File Extension doesn't need to be three characters. If you leave the Outline as <none>, it will use the MicroSoft normal.dot format.

Back to the Table of Contents.
View and/or print document history.
Enter the document's Properties sheet. In ReqPro, right-click on the document and select Properties. Inside the document, select RequisitePro->Document->Properties. In the Properties sheet, go to the Revision tab and click on History. You must have a printer already set up for the Print button to be active. There is no way to print to a file.

Back to the Table of Contents.
Delete a document.
Open the project in ReqPro. Right-click on the document and select Delete. All requirements associated with the document will be deleted from the project as well.

Back to the Table of Contents.
Integrate ReqPro w/ ClearQuest.
For details, see the Rational Suite Administrator's Guide. It comes bundled as an Adobe Acrobat file with the Suite's cdroms.
Any CQ record type to be integrated must have the latest Repository and RequisitePro packages installed. A ReqPro project can only be integrated with one CQ database at a time. A CQ database can have many ReqPro projects integrated with it.
To enable the integration, you must edit the ASCQISetup.bat file, located in ratl-home\common. Once the variables are set, there should be one ASCQISetup.exe line for CQ record type being integrated. REM-out any lines that are not applicable, such as if you don't have an EnhancementRequest record type.
The file only needs to be edited and run once, unless one of the values changes. Run the bat file once for each ReqPro Project/CQ integration. Save a copy of each integration instance. Note that if a particular ReqPro project doesn't have security enabled, the Super User logon variable must be set to the project's default logon; namely "admin" unless it was changed.

Back to the Table of Contents.
Customize menus.
The Tools->Add-ins command allows you to add your own customized commands to menus in ReqPro. These menu commands can be used to start external applications, such as Notepad, directly from ReqPro. In addition, you can configure a command to open an individual file with the application of your choice. You can add commands to any of the following ReqPro menus: File, Edit, View, Requirement, Traceability, Tools, and Help. You can add either a project-wide menu command for use by all members of the project team or a command that appears only when ReqPro is open on your PC. The Add-ins command prompts you to specify an external menu file that defines your customized menu commands.

Create a menu file.

However, before you can add custom commands to a menu, you must create a custom menu file in which those commands are defined. The following is the syntax for that file: 
Menu <RequisitePro menu name>
{
	Separator
	Option <menu item>
	{
		Exec <command line>
		Status <status text>
	}
	Menu <submenu name>
	{
		Option <menu item>
		{
			Exec <command line>
			Status <status text>
		}
		Option <menu item>
		{
			Exec <command line>
			Status <status text>
		}
	}
}
Menu: The ReqPro menu under which the command will appear.
Separator: A horizontal bar that appears in the menu to separate entries.
Option: The name of your command as you want it to appear in the menu.
Exec: The path to the executable.
Status: A simple cmd explanation that appears at the bottom of ReqPro when the mouse is placed over the menu item.
You can have up to 5 levels of submenus. All names and items must be in double quotes if more than one word is used. Place an ampersand (&) before a character so that the keyboard can be used to jump to that menu item. You can have all your custom menu commands in one file independent of where they appear in the ReqPro menus.

Add the custom command.

In the ReqPro Explorer, select Tools->Add-ins. Once inside, click the Add button. Type in a name for the custom menu. This name is only used for the Add-ins list. The actual menu command names are listed inside the custom command file. Browse to where you created the custom menu file. Leave the Active button checked. The custom menu can be Local (just you), or Project (everyone). Click OK and the custom menu file's entries will appear in the ReqPro menu(s).

Back to the Table of Contents.
Create a package.
Highlight the name of the project in the Explorer. Select File->New->Package. The package can be placed anywhere in the package hierarchy of the project. The package name must be unique in the parent where it is placed.

Back to the Table of Contents.
Move a package.
In the Explorer, simply drag and drop the package to its new location. The package name must be unique in the parent where it is placed.

Back to the Table of Contents.
Rename a package.
Open the project in ReqPro. Access the package's Properties sheet. Simply type in a new name for the package.

Back to the Table of Contents.
Delete a package.
The package folder must be empty before it can be removed. Either drag the contents to another package or delete them.

Back to the Table of Contents.
Create a project.
Any open project will need to be closed first. In ReqPro (client only), select File->New->Project. Select a template icon, such as Use-Case Template and click OK. Give the project a useful name, a location for the project data, and a database type.
When creating a project from a baseline, the newly created project does not maintain the cross-project traceability links, discussions information, and associations with Rational ClearQuest and Rational Rose from the original baselined project.
When you create a new project, ReqPro performs some of the following operations.
The project appears in the Explorer and is added to your project list in the Open Project dialog box. If the project is based on the Use-Case or Composite Template, ReqPro creates an Attribute Matrix Views package that also appears in the Explorer, listed under the project. The requirement types and document types you created in the project become available for your use.

Back to the Table of Contents.
Open an existing project.
In the ReqPro Client, select File->Open Project. Projects are listed according to recent use.

Back to the Table of Contents.
Archive or baseline a project.
The major difference between ReqPro archives and baselines is in the purpose and person who performs the operation. Archiving is done for data protection, and is usually performed by IT (who may have no knowledge of ReqPro). Baselining is done for project tracking purposes and is usually done by the project administrator, who typically is familiar with the project and perhaps CC UCM. That is, a release of a project's software should include in the baseline all the software to run the system, the requirements that are applicable to that release, documentation to run the system, and any test artifacts that are needed to test that particular version of the system. Even though the artifacts are baselined in CC, they are still controlled and modified in ReqPro. But, instead of users accessing the .rqs (project) file from just any share, they will actually be accessing ReqPro (probably unknown to them) from a ClearCase view. Yes, this implies that all users that modify artifacts of the ReqPro project are using the same CC view.
When you archive projects that use an Access database, ReqPro includes all project files, documents, and database content in the archive. When you archive projects that use an enterprise database, RequisitePro includes only project files and requirements documents in the archive. You must use your database utilities to archive the enterprise database. That is, requirements that only live in the enterprise db are only archived if a DBA archives them. Projects that participate in cross-project traceability should be archived or backed up at the same point in time to maintain consistent traceability links between them.
By contrast, when a ReqPro project is baselined, no DBA involved is needed, even if an enterprise db is employed. The requirements in the db are streamed to XML files that are placed under source control in CC. The ability to baseline a project was introduced in ReqPro 2001.

Archive
In the Explorer, open the project to be archived and select File->Project Administration->Archive->(RequisitePro Archive or Rational ClearCase). RequisitePro Archive creates a copy on the file system. Rational ClearCase creates a new version under source control in a ClearCase VOB, even if identical. Placing files in ClearCase does not baseline (create a label on) them.
Before archiving to ClearCase for the first time, under Tools->Options, enter the ClearCase View path to a VOB location where the projects should be archived: something like "M:\default_view\archive_vob\reqpro_projects".

Baseline
To create a ClearCase UCM baseline of a ReqPro project, the project must be associated with a UCM-enabled Rational project in Rational Administrator (RA). The baseline is created through the RA and not through ReqPro. Everybody must be out of that project whenever it's baselined.
Note that when a project is initially baselined in UCM, all the files associated with the project are left checkedout. Users will continue to edit the project in the normal ReqPro way, but instead of accessing the files from a share, they access them from within a CC view. The project isn't baselined again. To update the baseline in CC, use the check-in-all command from within the RA. That is, the baseline is only done once and a check-in-all is performed every time after.
To get an initial baseline you must create a ClearCase UCM project and view, create a RA project, and then create ReqPro project from within the RA. The RA project file that gets created (.rsp) is just a configuration file that doesn't have to be under source control. ReqPro projects can also be created from a UCM baseline of an older, existing project.
The baseline (label) itself is not created from ReqPro, but from within ClearCase the standard way after creating a new version of the project there. See "Create a baseline".

WARNING! You must create the ReqPro project within CC from the start. If you don't and then baseline it, the process will actually move the files from disk to CC. After that, ReqPro won't be able to find the project files anymore.

NOTE: You may want to choose to have the project save documents with the Word .doc extension instead of the ReqPro specific extensions (.vis, .ucs, etc) that it defaults to. This will give greater flexibility with the files while they under source control, such as diffing and merging. However, if the file is saved with the generic .doc extension, it can be modified outside of ReqPro, which is a problem.

Back to the Table of Contents.
Designate a project prefix.
Project prefixes are required if you want to take advantage of cross-project traceability. To destinquish between UC123 in project and UC123 in another project, the "external" project to which you connect must have a project prefix. External is defined as the project to which another project will connect to get requirements. Prefixes must be in all upper-case with a max of 8 characters. For example, if the project is called "Learning Project", you might designated the prefix as "LEARNING".
In ReqPro, with the external project open, right-click on the project to enter its Properties dialog. On the general tab, simply type in the Prefix.

Back to the Table of Contents.
Add an existing project to the ReqPro project list.
If you bring a project (.rqs and related docs) from another location, you can simply add the project to the ReqPro project list. Open ReqPro and select File->Open Project. When the dialog appears, click on Add. If the project is on a removable device, such as a floppy disk, move it to a permanent location on the local hard drive first, as that is where ReqPro will expect to find it from then on.

Back to the Table of Contents.
Remove a project from the ReqPro project list.
You can remove a project from the list of projects in ReqPro without deleting the files on disk. In ReqPro, select File->Open Project, highlight the project to be remove and click Remove.

Back to the Table of Contents.
Create a project template.
A project template defines what views, documents etc are present as a default when create a new project of that type. You can create a custom project template by selecting File->New->Project. In the dialog, double-click on the Make New Template icon. In the ensuing wizard, you cannot dynamically enter a template storage location. However, you can designate an alternate location for project template storage. The tempalte must be based on an existing ReqPro project. Place that name in the RequisitePro Project field. You can optionally "Include project data" in the new template as well. It will use the actual requirements and document of the other project as they existed when the project template was created. If project security is enabled for that project, you must have project structure permissions to base a template off of that data.
You can optionally include a Documentation File, such as a ReqPro project plan that describes the creation and use ReqPro projects at your site.
You can optionally change the icon associated with the project template. Simply set the path the alternate .ico file in the Icon->File: field. If you swap out the icon after the creation of the template, be sure to use the exact same name as the original .ico file.
The properties set above cannot be changed after the creation of the template. However, you can remove the template from the list and use the same data to create a template with slightly different properties, such as storage location.

Back to the Table of Contents.
Designate an alternate location for project template storage.
If you create custom project templates, you can store them in a central, network accessible location. In ReqPro, go to Tools->Options. Fill in the path to the custom project templates directory in the Project Templates field. Unforatunately, you can only have one custom path. It will show up in addition to the default template location when creating a new project template.

Back to the Table of Contents.
Remove a project template.
To make it so that a project template no longer shows up in the list of available templates when creating a new project, simple move the actual project template folder (or rename it). The project creation wizard will only show project template folders that it can dynamically find.

Back to the Table of Contents.
Print a project summary.
You can print a summary of the project structure in report form. The requirement types, document types, and document details are printed.
Open the project in ReqPro. Select File->Project Administration->Print Summary. Unfortunately, there is no way to send the summary to a file. You must have a printer set up.

Back to the Table of Contents.
View and/or print project history.
With the project open in ReqPro, select File->Properties. Go to the revision tab and click History. You must have a printer already set up for the Pring button to be active. You can't print to a file.

Back to the Table of Contents.
Rename a project template.
There is no easy way to rename a project template. You need to go to the disk location where it's stored and rename the template folder. You must also rename any files that reside inside the template folder to be the same name.

Back to the Table of Contents.
Add an existing project template to the list.
If you bring a project template in from somewhere else, you simply need to place the entire project template folder into one of the registered template storage locations. The default is ratl-home\RequisitePro\templates. You can also designate an alternate location for project template storage.
If the project template folder is renamed in the process, be sure to rename all files contained in the folder to have the same name.

Back to the Table of Contents.
Rename a project.
To rename a project, open it up in ReqPro and access its Properties sheet. On the General tab, simply give the project a new name. The project's name will be changed on disk as well.

Back to the Table of Contents.
Create a requirement.
ReqPro Client only. All requirements are stored in the database. The requirement can be created as part of a document or directly in the db.
In a document:
Open the document from within ReqPro. Highlight the text to be turned into a requirement, right-click on the text and select New Requirement. In the resulting dialog, choose the requirement type and give it a name. ReqPro automatically assigns the requirement ID when the document is saved.
Directly in the database:
In the ReqPro client, right-click on the package in which the new requirement will live and select New->Requirement. Or, invoke a view, such as "All Features", and at the bottom of the list of requirements, select "Click here to create a requirement". Upon creation, the new requirement is automatically committed to the database.
NOTE: Unfortunately, ReqPro doesn't check to see if an existing requirement already has the same Name. That is, it's possible to create duplicate requirements. It's up to the user to detect duplication.

Back to the Table of Contents.
Create multiple requirements.
Multiple requirements can only be created from within a document. With the document open, highlight all the text to be turned into requirements. You can even highlight inbetween sentences that you may not want to be turned into requirements. During the wizard's execution, it will only look for sentences containing certain keywords and then will prompt for confirmation on each one.
Select RequisitePro->Requirements->New Wizard. When the dialog box appears, type in any keywords and Add them to the keywords list. Click the Create button and it will step through each sentence that is highlighted.

Back to the Table of Contents.
Edit a requirement.
Requirements can be edited in a document or just in the database. If a requirement that is included in a document is edited in the database, the changes will be visible in the document the next time it is opened. Whether or not a particular requirement is part of a document or not can be determined by looking at the "Location" column under the attributes matrix.
Edit in a document:
Edit outside a document:

Back to the Table of Contents.
Create traceability between requirements.
In the database:
In ReqPro, open the project whose requirements are to be connected. Requirements can trace between projects too. In a package, double-click on a traceability matrix, such as "Use Cases Traced to Features". In an empty cell that is the intersection between requirementst to be connected, right-click and select "Trace To" or "Trace From" depending.
You can trace several requirements at once by using a combination of the <shift> key and mouse click.
In a document:
Place the cursor somewhere on the requirement's text. Select RequisitePro->Requirements->Properties. Click the Add button to trace from or to another requirement.

Back to the Table of Contents.
Delete traceability between requirements.
In the database:
In ReqPro, open the project whose requirements are to be disconnected. In a package, double-click on a traceability matrix, such as "Use Cases Traced to Features". Right-click on the cell whose traceability is to be removed and select "Delete Trace". Alternatively, select Edit->Set Value and choose "Delete Trace" from the pull-down menu.
To clear the traceability on several requirements simultaneously, use the <shift>-click or <ctrl>-click to highlight them.
In a document:
Place the cursor somewhere on the requirement's text. Select RequisitePro->Requirements->Properties. Select the trace to be removed and click the Remove button.

Back to the Table of Contents.
Clear suspect traceability.
In a traceability matrix, simply right-click on a cell and select "Clear Suspect". By default, anyone can clear suspect traceability. Security can set up to control this action.

Back to the Table of Contents.
Create a hierarchical (parent/child) relationship.
The hierarchy must be set up from the child to the parent. That is, when setting up the relationship, do it from the child's properties dialog. A child can only have one parent, but a parent can have more than one child. If a requirement is associated with a document, its hierachical relationships can only be created and modified within the document.
Right-click on an existing requirement (in a document or in ReqPro) and select Requirement Properties. Under the Hierarchy tab, in the pull-down list, select <choose parent>.

Back to the Table of Contents.
Delete a hierarchical (parent/child) relationship.
If a requirement is associated with a document, its hierachical relationships can only be created and modified within the document. Within a document, right-click on the requirement and select Requirement Properties. Under the Hierarchy tab, choose <none> for the Parent.

Back to the Table of Contents.
Establish cross-project traceability.
You can only connect to projects that contains at least one requirement type that is designated as external. See Designate a type as external. Also, the external project must have a designated project prefix. See Designate a project prefix.
Go to File->Project Administration->External Projects. You can dynamically disconnect and connect the "external" projects.
The Logon Project dialog box appears if the external project is secured and your username and password are different than those used to log on to the current projet, the current project is not secured, but the external project is. If neither project is secured, you are not required to log in.
In the External Projects dialog, click Add. It will prompt for a .rqs (ReqPro Project) file that resides out on disk somewhere. in the External Project References list, select the project. Click Connect. Click OK to save the changes.
Once cross-project traceability is enabled, you can establish traceability to external requirements. Go to a Traceability Matrix. Enter the Properties dialog for a requirement and click Add. You should see the external requirement type(s) listed in the "Requirements of Type:" pull-down.

Back to the Table of Contents.
Find all instances of a certain requirement type.
If you attempt to remove a type that is still being used by requirements, you get an error stating so. If you create a matrix that shows all the requirements of that type, you can highlight them all and select Edit->Delete. Unfortunately, it will complain that it can't remove them from documents. You will have to go to each document and remove them one at a time.

Back to the Table of Contents.
Move a requirement.
In the Explorer, simply drag and drop the requirement to anywhere else in the package hierarchy.

Back to the Table of Contents.
Enable/disable requirement text editing outside a document.
If a requirement lives in a document, you may have a policy that allows or disallows the editing of the requirement's text outside the context of the document.
In the Explorer, enter the project's Properties sheet. The switch is under the Documents tab.

Back to the Table of Contents.
Designate an existing requirement type as external.
The requirement type must already exist. You must have "project structure" permission to designate a type as external.
Open the Properties dialog for the project whose requirement type is to be externalized and go to the Requirement Types tab. Select the type to be externalized and click on Edit. Simply check the box called "Allow External Traceability". You must have designated a project prefix. See Designate a project prefix.

Back to the Table of Contents.
Create a requirement type.
A requirement type is a template for your requirements. Requirement types are used to classify similar requirements so they can be efficiently managed. When you define a requirement type, you define a common set of attributes, display style, and tag numbering. A typical grouping scenario is to group high level features (such as marketing requirements) into one requirement type, more detailed requirements (such as software specs) into another type, and business requirements into yet another type. You must have "project structure" permissions to create requirement types.
In the Explorer, double-click on the project to bring up its Properties dialog. Click on the Add button and fill in the required fields. It will automaticaly pick a color that isn't already being used by another requirement type. The field called "Requirement Must Contain" designates a word or phrase that must be present in the text being turned into a requirement of this type. The Name can be up to 64 characters and the Description can be up to 255 characters. You can designate the "Initial Requirement #", but that number cannot be changed after the first requirement of this type is created.

Back to the Table of Contents.
Modify a requirement type.
In the Explorer, double-click on the project to bring up its Properties dialog. Click on the Edit button. The "Initial Requirement #" cannot be changed after the first requirement of this type is created.

Back to the Table of Contents.
Delete a requirement type.
You cannot delete a requirement type that has requirements of that type in the database.
Double-click on the project to enter its Properties sheet. Go to the Requirement Types tab, select the type to be deleted and click on Delete.

Back to the Table of Contents.
Renumber requirements.
You can renumber all requirements of a specified type in requirement documents and the database. The renumbering feature is useful for eliminating "holes" in a numbering scheme, which can result when you delete requirements. To renumber requirements, you must open the project in exclusive mode. In addition, if security is enabled, you must have project structure permission to renumber requirements. To renumber requirements in documents, all documents that contain requirements of that type must be open.
Open File->Project Administration->Renumber Requirements. Click "Renumber Requirements of this type". To change the order of renumbering for requirements located in documents or the database, select a document name or Database in the Order of Processing list, and then click Move Up and Move Down. The requirements in the first item listed (the database or a document) are renumbered first, followed sequentially by the requirements in the second item, and so on. A document appears in the Order of Processing list only if it contains requirements of the selected type.

Back to the Table of Contents.
Rebuild requirement tags in a document.
The information used to identify and locate requirements in a document may become corrupted. You can use the Rebuild Tags command to rebuild a requirement tag that is partially or completely deleted or corrupted. You must have update permissions to use this command. You cannot rebuild tags if a document is open in read-only mode.
Inside the document, go to RequisitePro->Document->Rebuild Tags. The affected tags are rebuilt, and a list of rebuilt requirement tags is displayed. This command does not restore deleted or corrupted requirement information, such as text, graphics, or OLE objects.

Back to the Table of Contents.
Hide requirement tags in a document.
For readability, you may want to hide the requirement tags associated with each requirement in a document. While in the document, go to RequisitePro->Document->Properties. Under the general tab, uncheck the "Show Tags" box.

Back to the Table of Contents.
View and/or print requirement history.
In ReqPro, right-click on a requirement and go to its Properties sheet. Inside a document, highlight the requirement and go to RequisitePro->Requirement->Properties. Go to the Revision tab and click on History. You must already have printer set up for the Print button to be active. There is no way to print to a file.

Back to the Table of Contents.
Export requirements.
You can export requirements from a view to a .csv file or Word document.

To .csv:
You export a view as an ASCII file (csv format). Depending on the view, each requirement is exported with the requirement tag, followed by the requirement text, requirement name, and requirement attributes.
Note that setting view properties for requirement text and name affects what is exported. If the requirement text and name are not displayed in the view, they are not exported. If you have refreshed the view, only the filtered requirements are exported. Hierarchical requirements are exported with their full hierarchical tag number. This number is used to denote the hierarchical relationships and is used on subsequent imports to reconstruct the hierarchy.
To export, open the view you want to export. Select File->Export->Export to CSV. Type a file name for the exported view (use the .csv extension), and click Save.

To a Word doc:
When you export requirements in Word format, Rational RequisitePro creates a new Microsoft Word document showing the expanded levels in a view. You can export Attribute Matrix and Traceability Tree views. Note that setting view properties for requirement text and name affects what is exported. If the requirement text and name are not displayed in the view, they are not exported. If you have queried the view, only the filtered requirements are exported.

Back to the Table of Contents.
Import requirements.
You can import requirements into ReqPro from Word docss or from a .csv format. The Import Wizard, which automates the import process, appears when you select the Import command on the Project menu. You can cancel the import at any time during the process.
For each import you perform, RequisitePro creates an import log, which is a written record of the import process. The import log records such events as: Requirement type matching, Conflict handling, Attribute mappings, Success or failure of search criteria, etc... RequisitePro saves the import log in the directory where the project is stored. The import log is named import#.log, where # is a number representing sequential order of creation.
Before you begin importing a document or a .csv file into a ReqPro project, you must have a project created. The project must include at least one requirement type and one document type.
Important notes: Imported requirements are renumbered during the import. If an input file has more than one requirement type listed, they are all converted to the same requirement type designated during the import. To start the import, in ReqPro go to File->Import.

From a .csv:
A .csv (comma-separated-value) file is a data file consisting of fields and records, stored as text, in which the fields are separated from each other by commas. If the data in a field contains a comma, the field is further surrounded with quotation marks. Using a comma-delimited file format allows data to be shared between database systems that use different formats.
The .csv file must contain a header in RequisitePro format; namely:

<Tag>,"Requirement text", "Name", <Attribute 1>,<Attribute 2>,<Attribute 3>

The requirement type specified in the <Tag> field determines the default requirement type that is assigned during the import process. You can change this requirement type assignment in the Import wizard. All attributes that are included in the .csv file must exist in the corresponding ReqPro requirement type. If attributes do not match, the default values for the requirement type are inserted during the import process. All list-type attribute values in the .csv file must exactly match the predefined list-type attribute values in the ReqPro requirement type definition. Multiple-value list attributes appear in a .csv file in quotes, separated by commas (for example, "Chris, Jan, Sue"). If the .csv file contains null values (blank spaces) for any list-type requirement attributes, those attributes are assigned the default value as defined in the project's Properties. To retain a null value, remove the default setting before importing the .csv file. You can reassign the default value after the import process is complete.

From a Word doc:
You can use the Import Wizard to import requirements from a Word doc into a ReqPro document. The document from which you are importing must be in Word format. If your document was created in an application other than Word, refer to the Microsoft Word documentation for instructions on saving the file in Word format. Turn off Word’s spelling, grammar, and background repagination options (in the Options dialog box) before you import a Word document.

Back to the Table of Contents.
Enable security.
Initially, security is not enabled for any project. Once security is enabled for a project, the user logging in gets prompted every time before opening the project. Without project security, there is no audit trail of who made what changes.
In the Explorer, right-click on the project and select Security. You must be logged in the "Administrators" group to initialize security. To allow a specific group to manage project structure and/or project security, select the group and click Edit underneath the group list.

Back to the Table of Contents.
Assign requirement, attribute, traceability and/or document permissions.
In the Explorer, go to File->Project Administration->Security. Select the group to be given type security. Cannot assign special security to the Administrators group, as they already have global write access. Underneath the selected group, click Edit. By default, all new groups have read/write access to all data. There is no way to remove user read access to attributes and traceability.

Requirement and document types:

Attributes:

Traceability: