Working with Projects and Project Packages in Requisite Pro.
When you start RequisitePro, the Open Project dialog box appears, which enables you to select a project to work with or to create a new project. The Existing tab lists all the RequisitePro projects that are accessible to you. You can add or remove projects from your list as you need them.
In the Open Project dialog box, projects are listed according to recent use; the projects you have opened most recently appear at the top of the list. When you select a project and click OK, it appears in the Explorer, following the RequisitePro icon. The plus sign that precedes the name of the project indicates that it contains artifacts; click the plus sign to expand the list and see the hidden objects. Within each project, requirements artifacts are organized in packages. A package is a container that can contain requirements documents, requirements, views, and other packages. You  can place related artifacts in a single package, and this organization makes it easier for you to view them and to manipulate the data. You can configure your packages as necessary to facilitate your work. An artifact cannot appear in more than one package, but you can move it from one package to another. You can create a package within another package. All project packages are shared by all project users.


Adding a RequisitePro Project to Your Project List
Before you can access a RequisitePro project, you must add it to your project list. Projects you create are automatically added to your project list.

1.Click File > Open Project. The Open Project dialog box appears.
2.Click Add. The Add Project dialog box appears.
3. Select the project file you want to add to the list. (Project files have an .rqs
extension.)
4. Click Open. RequisitePro adds the project to your project list, and it appears with the projects listed on the Existing tab. You can now open the project and use its requirements and documents.
Tip: Click the Properties button to view or change the database properties of the selected project.
5. Click OK to save the changes.
Note: To add a project stored on a floppy disk, move or copy the project to a local drive or network drive (using Windows Explorer), and then add it to your project list.

Removing a Project from the Project List
You can remove a RequisitePro project from your project list without deleting the files from your system.
To remove a project from the project list:
1 Click File > Open Project. The Open Project dialog box appears.
2 Select the project you want to remove, and click Remove. RequisitePro removes the project.
3 Click OK to save the changes. Note: You can retrieve a project you removed by clicking the Add button. (Refer to
the preceding section.)

Opening a Project and Project Documents
When you open a RequisitePro project, the project appears in the Explorer. Project artifacts may be hidden from view until you click the plus sign. To open an artifact, you select it in the Explorer; then, either double-click it or right-click and select Open. If you try to open a project that requires updating to the current version of RequisitePro but was created in version 4.0 or later, the Database Upgrade Wizard appears. The wizard guides project administrators through the process of upgrading existing database structure and project data to the current RequisitePro release. For information about the upgrading of projects that are not organized in packages, If a project is in a version of RequisitePro earlier than 4.0, you must first upgrade the project to version 4.0 before using the Database Upgrade Wizard. Contact Technical Support for information.
Note: Do not open a project for which a baseline is being created in Unified Change Management or one that is being added to ClearCase.

To open a project:
1 Click File > Open Project (or click the Project button). The Open Project dialog box appears.
2 Select the project you want to open, and select the Open Project Options you want. If you want to be the only user who has change permissions for the project, select the Exclusive check box. To open the project and its documents in read-only mode, select the Read Only check box. Click OK.
Depending on the security setting for the project, one of two dialog boxes appears:
❑ If security is set on the project, refer to Accessing a Secure Project on page 36.
❑ If no security is set on the project, but your user name has not been identified in the project, the Project Logon dialog box appears.
3 Do one of the following:
❑ Accept the displayed name.
❑ Select a user name from the list.
❑ Type a new user name that will be added to the project.
4 Click OK. The project appears in the Explorer. If the project is already open by another user who has exclusive rights, you are given read-only access.
You can open one or more requirements documents in an open RequisitePro project in one of the following ways:
❑ Double-click one or more documents in the Explorer.
❑ Click Window > Show Word. In Word, click RequisitePro > Document > Open. The Open Document dialog box appears. Select one or more documents and click
OK.
Note: Do not press the ESC key while the document is opening. If you want to view the document but not make modifications to it, you can select it in the
Explorer, right-click, and select Open Read Only.

Closing a Project and Documents
The Close command closes a project and its documents and any open views.
1 Click File > Close Project.
If you made no changes, the Project Close dialog box appears and prompts you to close the project and its documents or keep it open. Click Yes to close the project and its documents.
If you modified but did not save a document, the Document Changed dialog box appears.
2 Do one of the following:
❑ To save the changes to the document, click Yes. If you made changes to a requirement’s text, the Change Description dialog box appears and asks you to
enter the reason for the changes before saving.
❑ To close the project without saving the document changes, click No.
❑ To cancel the close project procedure, click Cancel.
❑ To review document changes, click Review Changes. If you made changes to a requirement’s text, the Change Description dialog box appears and asks you to
enter the reason for the changes.
The Document Changes dialog box appears, listing each modification to the document.
3 Do one of the following:
❑ To save the changes to the document, click Yes.
❑ To close the project without saving the document changes, click No.
❑ To cancel the close project procedure, click Cancel.

Accessing a Secure Project
Project administrators can enable security for a project, requiring users to log on and provide a password. The project administrator sets up security and assigns a user name and password to each member of the team.

Logging on to RequisitePro
To log on and to access a secured RequisitePro project:
1 Click File > Open Project. The Open Project dialog box appears.
2 Select a project in the list to open and click OK. If RequisitePro detects that security is enabled, the Project Logon dialog box appears.
3 Type your name in the Username text box. Usernames cannot exceed 20 characters, and they are not case sensitive.
4 Type your password. Your password is set up by a project administrator.
Passwords are case sensitive; for example, Mycomputer, MYCOMPUTER, and mycomputer are separate passwords.
5 Click OK. You are now ready to use the project.

Modifying Your Password, User Name, or E-mail Address When you are in a project, you can modify your password, user name, or e-mail address. If you are a RequisitePro administrator or a member of a group with project security permissions, you also have the ability to change the password, user name, or
e-mail address for other users. A valid e-mail address is necessary for receiving RequisitePro discussion messages via e-mail.
1 Open a project and log on.
2 Click File > Project Administration > Security. The Project Security dialog box appears.
3 Click the Enable security for this project check box. Select a user group and a user name, and click the Edit button.

The Edit User dialog box appears.
To change your password:
1 Type your password in the Old Password text box that appears in the dialog box. (This step applies only to users who do not have project security permissions.)
2 Type your new password in the New Password text box. Passwords are case sensitive and are limited to 14 alphanumeric characters.
3 Confirm the new password by typing it again in the Verify box.
4 Click OK. Your new password is in place and ready for use. To change your user name (for users with project security permissions):
1 Select your current name in the Username field.
2 Type a new user name. User names are limited to 20 alphanumeric characters and are not case sensitive.
3 Click OK. Your new name is in place and ready for use.

To change your e-mail address:
1 Select your current e-mail address in the E-mail Address field.
2 Type a new e-mail address.
3 Click OK. Your e-mail address is in place and ready for use.
Close the project and project documents Then click File > Exit.

 

Working in Views

Rational RequisitePro views use tables or outline trees to display requirements and their attributes or the traceability relationships between different requirement types. RequisitePro includes powerful query functions for filtering and sorting the requirements and their attributes in views.
A view is an environment for analyzing and printing requirements. You can have multiple views open at one time, and you can scroll to view all requirements and attributes in the table or tree. The number of requirements in the current view appears in the lower right corner of the views window.
You can create three kinds of views:
 An Attribute Matrix view, which displays all requirements and their attributes within a specified type.
 A Traceability Matrix view, which displays the relationships between requirements of two types.
 A Traceability Tree view, which displays the chain of traceability through the project requirements. A Traceability Tree can be set up in one of two directions: traced out of requirements of a specified type or traced into requirements of a specified type.
You can do the following in a view:
 Create and modify the requirement name, requirement text, requirement attributes, and traceability relationships
 Sort and filter view information
 Save a view’s query and display setup
 Save view information to other formats
 Print views

Accessing Functions and Navigating in Views
All views commands are located in the toolbar. To navigate in a view quickly, use the arrow keys, the PAGE UP or PAGE DOWN keys, and the HOME and END keys. Use the right button on the mouse as a shortcut to commands that are specific to requirements and attributes. Move the mouse over the requirements and attribute labels and click the right button to access these shortcut menus. When you select a requirement in a matrix or a tree, the full name and text of the selected requirement are displayed in the text pane at the bottom of the view. (You can resize the text pane by positioning the mouse on the upper border and dragging upward.) When you select a requirement in the Explorer, the requirement name appears in the description window below the Explorer pane.

Viewing Current Data
While a view is open, other users may add, delete, or modify requirements that are displayed in your view. These changes are not automatically reflected in your open view or in the Explorer.
To update the data displayed in the view and in the Explorer for requirements that were modified by other users, click in the view or in the Explorer and then click View > Refresh (or the Refresh the view button). The Refresh command updates the displayed content.

Traceability in a View
The Traceability Matrix and Traceability Tree views display traceability relationships, and the Traced-to or Traced-from attributes appear in the Attribute Matrix. A traceability relationship is displayed as suspect when you make a change to a requirement. For more information about traceability relationships between requirements
 Arrows are used to indicate direct traceability relationships in the Traceability Matrix and Traceability Tree views. If the arrow points from A to B, then the following two statements are true: A is traced to B and B is traced from A.
 In the Traceability Tree and Traceability Matrix views, suspect traceability relationships are marked as lines through the arrows. In an Attribute Matrix,
suspect relationships are denoted by an (s) after the requirement tag in the Traced-to or Traced-from column.

A requirements relationship is indirect if the relationship is derived by traversing the requirements relationships. An arrow outlined by a dotted line, lighter in color than a direct relationship arrow, indicates an indirect traceability relationship in the Traceability Tree and the Traceability Matrix.

Hierarchy in a View
All views display hierarchical relationships, and you can use the Traceability Matrix and Traceability Tree to display hierarchical relationships that are marked suspect.
 You can create hierarchical relationships in a view by using Requirement menu commands or editing the requirement properties in the Hierarchy tab of the
Requirement Properties dialog box.
 When you modify a parent requirement, RequisitePro marks the relationships between the parent and all its immediate children as suspect.
 When you modify a child requirement, the relationship with its parent is not marked as suspect.
 When a child requirement is assigned to a new parent, all hierarchical relationships between the new parent and its immediate children are
automatically marked as suspect. The relationships between the children and their children are not marked as suspect.
 In the Traceability Tree, you can manually mark a hierarchical relationship as suspect or clear a suspect relationship.
You can set the level of child requirements to display in a view or in the Explorer.
1 Click View > Displayed Levels. The Displayed Levels dialog box appears.
2 Set the number of levels to display in the rows. You can either type a number or select all. Each level corresponds to another level of artifacts. (If you select 1, only root artifacts are displayed; if you select 2, one level below the root artifacts are displayed; and if you select all, all levels are displayed.) For a Traceability Matrix, set the number of the levels to display in columns.
3 Click View > Properties > Save as Default to save these levels as the defaults for a view. This command saves the currently selected pane size, window size, displayed levels, and all view properties as default settings.

The Attribute Matrix
The Attribute Matrix is a spreadsheet-like display that lists requirements of a specific requirement type and their attributes. Requirements are arranged in rows, listed by tag number and followed by requirement name (or requirement text, if the requirement has not been assigned a name). Attributes are arranged in columns. The Attribute Matrix displays all requirements, and it is the only view in which database requirements can be created.

Requirements
In an Attribute Matrix, a requirement is displayed in a single row, showing the requirement tag followed by the requirement name (or requirement text if the
requirement has not been assigned a name). When requirement text exceeds the width of the row, the last character is followed by an ellipsis (...), signifying the presence of additional text. An arrow marker at the beginning of a row indicates a selected row. An * and <Click here to create a requirement> marks the beginning of the empty row at the bottom of the matrix, where you can insert a new requirement. A pencil icon at the beginning of a row indicates that the requirement information you are entering has  not yet been saved.

To change the number of lines of requirement name and/or requirement text displayed, click View > Row/Column Sizing, and then select a different value for the row or column size.
Attributes
Attribute labels are listed at the top of each column. Corresponding attribute values are listed beneath the attribute labels. Query information is displayed here as well. Click View > Displayed Attributes to select the attributes you want to display in the view. The Attribute Matrix displays all internal and external traceability relationships in the Traced-to and Traced-from columns; suspect traceability relationships are denoted with an (s) in the relevant column. You can change the size of the attribute columns.


Text Pane
The text pane, located at the bottom of the Attribute Matrix, displays a requirement's tag, name, and text, and it reads “Multiple requirements selected” if you have selected more than one requirement. This field is read-only. Graphics and OLE objects included in requirement text are displayed as small rectangular symbols. For Word-linked files included in the requirement text, the path and time stamp of the linked file are presented. The default size of the text pane is two lines, but you can drag the border to increase the size.

The Traceability Matrix
The Traceability Matrix displays and manipulates the relationships between two requirement types. The requirements can be of the same type or of different types, and they include all internally and externally mapped requirements. Use this view to create, modify, and delete traceability relationships and to view indirect and suspect traceability relationships. If you display a Traceability Matrix of requirements of the same type, it shows hierarchical relationships that are marked as suspect. In this view, a requirement is traced to or traced from another requirement. For example, Requirement B is traced from Requirement A if it was directly or indirectly derived from Requirement A. If Requirement A is the basis of several other requirements, Requirement A is traced to these requirements.

An arrow pointing from one requirement to another indicates that a direct traceability relationship exists between the requirements. A dotted line arrow indicates an indirect relationship. (By default, only direct traceability relationships are displayed in a new Traceability Matrix. To view indirect relationships, click View > Properties > Show Indirect.)
Rows and columns can be resized. The intersection of a row and column is called a cell. To change the number of lines of requirement name and/or requirement text displayed, click View > Row/Column Sizing and then select a different value for the row or column size.
Note: If the requirement has a name assigned, that name appears in the first line of each row or column. Increase the row or column size to view both the name and text.

Cells
 If the cell is blank, no relationship exists.
 If an arrow points upward to a column requirement, the row requirement is traced to the column requirement.
 If an arrow points down toward a row requirement, the row requirement is traced from the column requirement.
 If a dotted line arrow is displayed, an indirect relationship exists.
 If an arrow with a red diagonal line through it is displayed, the traceability relationship is suspect.
 If a triangle with a red diagonal line through it is displayed, the hierarchical relationship is suspect.

Text Panes
The Traceability Matrix displays two text panes at the bottom of the window. These panes let you review the requirements in each area, so you can easily create, modify, and delete traceability relationships. The default size of each pane is set to one line and can be resized. The top text pane displays the name (or text) of the currently selected row requirement, and the bottom pane displays the name (or text) of the currently selected column requirement. These fields are read-only. If the selected requirement has been assigned a name, that name appears in the text pane. Otherwise, the requirement text appears in the text pane. When more than one row or column is selected, the corresponding text pane displays the message “Multiple requirements selected.” Graphics and OLE objects included in requirement text appear as small rectangular symbols. For Word-linked files included in requirement text, the path and time stamp of the linked file are presented.

The Traceability Tree
The Traceability Tree provides a graphical view of relationships to or from (internal and external) requirements of one specific requirement type, including direct,  indirect, and suspect traceability relationships. Although direct and suspect relationships are modified in this view, RequisitePro permits read-only access to indirect relationships. In addition, the Traceability Tree displays hierarchical relationships and shows parent-child relationships that have been marked as suspect.

The tag, name, and attributes of the selected requirement are displayed in the attribute pane.

When creating a Traceability Tree, you can choose one that displays all requirements traced to the requirements on which the tree is based or one that shows all requirements traced from the requirements on which the tree is based.

Tree Pane
The left pane of the Traceability Tree displays all the requirements associated with a requirement type. Root requirements appear at the root level (farthest left) of the tree pane and are preceded by an arrow. Child requirements are indented below their parents and are preceded by a triangle. The text pane below the tree provides the name and text of the selected requirement in the tree; the pane on the right side of the view displays requirement attributes of the highlighted requirement.  To resize the tree pane, click the border between the tree and attribute panes. Press the left button on the mouse and drag it left or right to the size you want. This does not affect the length of the lines set in the Row/Column Sizing dialog box.


If the arrow leading from a root requirement points toward a branch requirement, the branch requirement is traced from the root requirement. (This
appears only in a Traced out of Traceability Tree.) If the arrow leading from a branch requirement points toward a root requirement, the branch requirement is traced to the root requirement. (This appears only in a Traced into Traceability Tree.)
If an arrow with a red diagonal line is displayed, the traceability relationship is suspect. If a triangle with a red diagonal line is displayed, the hierarchical relationship is suspect.

Attribute Pane
The attribute pane, located on the right side of the Traceability Tree, displays the tag, name, and attributes associated with the currently selected requirement. To display the attributes of a particular requirement, click the requirement in the tree pane. This is a read-only text box and cannot be edited. If you have more than one requirement selected, the pane displays the attributes for the first requirement selected.

Text Pane
The text pane, located in the lower section of the Traceability Tree, displays a requirement's name and text. This field is read-only. To display the full name and text of a particular requirement, click the requirement in the tree pane. To adjust the height of the pane, click its upper border and drag the pane to the size you want. Then click View > Properties > Save As Default to save this pane size as the default. The text pane is blank when a requirement is not selected. When more than one requirement is selected, the text pane displays the message “Multiple requirements selected.” Graphics and OLE objects included in requirement text appear as small rectangular symbols. For Word-linked files included in requirement text, the path and time stamp of the linked file are presented.

Working with Views
This section presents the fundamentals of working in a view:
 Creating a view
 Expanding and collapsing a view

Saving a view
 Opening and closing a view
 Saving a copy of a view
 Renaming a view
 Printing a view
 Deleting a view
Creating a View
1 Select the package in which you want the new view to appear and click File > New
> View. The View Properties dialog box appears.

Do the following:
❑ In the Name box, type the name under which you want the view to be listed in the Explorer. Filling in the Description box is optional.
Note: The Package box contains the name of the package you selected in Step 1.
Click the Browse button if you want to change that selection.
❑ Select the View Type.
❑ Select a Row Requirement Type. (If you are creating a Traceability Matrix, you must also select a Column Requirement Type.) Note that user-defined
requirement types are also displayed.

Select the Private check box if you want to be the only user who can open the
view.
Note: The View Type, Requirement Type, Author, Date, and Time text boxes are read-only and cannot be modified.
3 Click OK. The view opens and appears in the Explorer in the package you selected in Step 1, listed alphabetically by name.
4 Click File > Save View to save the view in the project database. Expanding and Collapsing a View You can expand and collapse hierarchical relationships in all views and in the Explorer and traceability relationships in the Traceability Tree. An expanded view shows the root requirement and all its sub-level requirements. Collapse the view to show only the root-level requirements. The Expand All command expands all relationships in a view. When you select this
command in a Traceability Tree, a requirement that has a traceability relationship with a root requirement appears as a branch of the root requirement. This command also expands all parent requirements, displaying all children, in all views.

The Collapse All command collapses all relationships in a view. When you select this command in a Traceability Tree, a requirement that has a traceability relationship with a root requirement is no longer displayed. This command also collapses all parent requirements, hiding all children, in all views.
You can expand the parent requirement by clicking the plus sign next to the parent requirement, selecting the parent, and clicking SHIFT +, or selecting the parent and clicking View > Expand. You can collapse the parent requirement by clicking the minus sign next to the parent requirement, selecting the parent and clicking the minus (-) key, or selecting the parent and clicking View > Collapse. Use the Expand All command to expand all hierarchical or trace tree relationships in the view; use the Collapse All command to collapse all hierarchical or trace tree relationships in the view.

Saving a View
When you save a view, the layout of the view and the query criteria are also saved. The data within the view is not saved as part of the view; it is part of the database. Thus, when you open a saved view, the display shows the current information in a saved view format.
Note: The saved view is not a snapshot of requirement information for a particular date. To save the results of a query, you must print the view.

If you want to save a view and you have more than one view open, make sure that the view you want to save is active. To make an open view active, click the title bar.
To save a view:
1 Open the view that you want to save.
2 Click File > Save View (or the Save the current view button).

Opening and Closing a View
When you open a saved view, RequisitePro displays the view according to the specified layout and re-applies the query criteria to the current project database. The display therefore shows the current information in a saved view format.
To open a view, select the view in the Explorer and double-click it; to close a view, click the X in the upper right corner of the screen (the one below the top-level X in the title bar).

Saving a Copy of a View
If you have already saved a view, you can save another copy of it with a new name. This is useful if you want to change one aspect of the view, such as query criteria, and retain both versions for later use.
1 Open a view.
2 Click File > Save View As.
3 In the View Properties dialog box, you can do the following for the new copy of the
view:
❑ Modify the Name. (You must change the name if you are saving the view in the same package as the original view.)
❑ Browse to a new Package.
❑ Select the Private check box if you do not want to share the view. (Only the author or a member of the Administrators group can modify shared views.)
❑ Modify the Query.
4 Click OK.

Renaming a View
The name of a view is displayed in the title of the view window and is used as the view name when the view is printed. Renaming the view is useful for printing purposes; you can give a view a longer, descriptive name before you print it, so that the new name appears on the printed page. The new name is  saved in the database when you save the view again.
1 In the Explorer, select the view you want to rename and click File > Properties. The View Properties dialog box appears.
2 Type a new name for the view in the Name box and click OK.
3 Click File > Save View to save the renamed view to the database.
Note: The view is alphabetized in the Explorer by the new name after you click View > Refresh.

Printing a View
You can print any active view, and you can choose to print the entire matrix or selected items.
To print an open view:
1 You can print the entire view, or you can print selected requirements or relationships. To print selections, do one of the following:
❑ In an Attribute Matrix, click a requirement.
❑ In a Traceability Matrix, click a cell that contains an arrow. (Both the source and the destination requirements are selected.)
❑ In a Traceability Tree, click the requirements you want to print. (Use a multiple select action to select multiple requirements or relationships.)
2 Click File > Print. The Print dialog box appears.
3 If you are printing selected requirements or relationships, click Selection.
4 Make any other necessary changes and then print.
Note: Use the Print button on the toolbar to print directly to the default printer. The entire view is printed using the default printer selections.
You can also export a view to a comma separated value (CSV) file and use another application, such as Excel, to open the file and arrange the data for printing. You can specify the header and footer information to be printed with the view. In an open view, click File > Page Setup. In the Page Setup dialog box, select the information you want to appear, and then click Print.
Deleting a View
A personal view can be deleted only by the person who created it. A project-wide view can be deleted by the person who created it or by a member of the
Administrators Group.
1 In the Explorer, select the view you want to delete.
2 Click Edit > Delete.

Customizing Views
You can customize the look and content of every view you create. You can:
 Adjust the size of rows and columns.
 Filter and sort data according to query criteria, so that only requirements that match the query criteria are displayed.
 Select specific view properties to display, such as buttons, requirement name and text, lines, images, root images, and trace to and trace from buttons.
 Save a defined view for future use. Saving a view saves its query criteria and layout, but not the requirement data.
Adjusting Row Height
Adjusting row height affects all rows in the view.
1 Click View > Row/Column Sizing. The Row/Column Sizing dialog box appears.
2.Type the number of lines to display for each requirement. The maximum number of lines depends on a monitor’s display resolution.
3 Click OK. The view is modified according to your specifications. Shortcut: Click and hold the mouse on any border in the requirement area, and
then drag the row up or down to the size you want. If the row height is already set at one line, RequisitePro will not let you drag the row up to less than one line. The Traceability Tree does not have a shortcut.
Adjusting Column Width
1 Click View > Row/Column Sizing.
The Row/Column Sizing dialog box appears, as shown above.
2 Type the number of pixels (in the Attribute Matrix) or lines (in the Traceability Matrix) to display for each requirement or attribute. Parameters for column widths in different views follow.
❑ Attribute Matrix: To set a different width for each column, drag the column to the desired width. To set an equal width for all columns, use the Row/Column
Sizing dialog box. The maximum screen height is based on your screen’s resolution.
❑ Traceability Matrix: RequisitePro determines the maximum width on the basis of screen resolution.
❑ Traceability Tree: The column width is represented by the amount of indentation for each branch. RequisitePro dynamically changes the maximum number of
pixels allowed in these columns according to the width of the requirement pane and the size of the view. Any change to the column width affects all of the
columns in this view.
3 Click OK to commit these changes.
Shortcut: Click and hold the mouse on any border in the attribute label area or the requirement area (the gray area at the top of each column) in an Attribute or Traceability Matrix. Drag the width left or right to the size you want. The Traceability Tree does not have a shortcut.

Resizing and Arranging Views
Use the menu commands or the buttons on the toolbar to define the size and arrange the order of a view.
Creating Cascaded Views In a cascaded views arrangement, views are stacked on top of each other, each view slightly below and to the right of the preceding view. If many views are open, RequisitePro may overlap the first cascade of views with a second cascade until all open views are arranged.
Click Window > Cascade. RequisitePro cascades the views.

Creating Tiled Views
A tiled view arranges open views next to each other without overlap, and the views are uniform in size. To tile the views, click Window > Tile. RequisitePro presents a tiled view, as shown in the following screen shot.

Arranging Icons
Icons for all minimized views can be arranged from left to right, beginning at the bottom left corner of the view. To arrange the minimized views, click Window >
Arrange Icons.
Displaying View Properties
Use the Properties command to display properties associated with an active view. Each view displays distinct properties. These properties affect how the view appears and not the information contained therein.
Click View > Properties. Eight menu commands are listed; however, some are not available, depending on the type of view that is active. (For example, the option Show Trace to is not available when an Attribute Matrix is active.) If they are checked off on the menu, they appear in the active view.
 Save as Default saves the current view settings as the default settings for a new view.
 Reset Default resets the view properties to the saved default settings.

Show Name displays the requirement name. You can define the number of lines displayed using the View > Row/Column Sizing command.
 Show Text displays the requirement text. You can define the number of lines displayed using the View > Row/Column Sizing command.
 Show Trace To or Show Trace From displays arrows in the direction of either trace to or trace from relationships, depending on your selection. (These options are not available when an Attribute Matrix is active.)
 Show Indirect displays both direct and indirect traceability relationships. (This option is only available when a Traceability Matrix is active.)
 Show Expand Indicators displays a + in the cell if the child requirements of a collapsed requirement contains traceability relationships. (This option is only available when a Traceability Matrix is active.)

Saving View Properties as Default
The Save As Default command saves a view layout and any properties displayed as the default when opening views of that type. This command is available for all view types. To save a view and its displayed properties as the default for views of that type, click View > Properties > Save As Default. RequisitePro saves the view, layout, and properties for views of that type. Note: Use the Reset Default command to reset any view properties that have been
changed back to the saved default settings.