Tool Mentor:
 Setting Up Rational RequisitePro for a Project
Purpose
This tool mentor describes how to set up Rational RequisitePro® for a project.  
Related Rational Unified Process (RUP) information:  
  Activity: Set Up Tools. 
Overview
You create a new project in RequisitePro using a project template. All of the
project templates that are included with RequisitePro (except the Blank
template) include predefined document types, requirement types, and attributes
that are used by the project you create. You can use the Use-Case Template to
create a project; with this template, you can use all the features of the RUP. In your new project, you can immediately begin
creating new requirements documents in the Microsoft® Word or individual
requirements in views. Refer to the introductory topics at the top
of the Let's Go RequisitePro help application for more information on getting
started in your RequisitePro project. 
If you have licensed a Rational Suite or other Rational products, you can
integrate your RequisitePro project with your work in those products.
 
  - For information on integrating RequisitePro with Rational Rose®, refer to
    Tool Mentor: Managing
    Use Cases with Rational Rose and Rational RequisitePro.
  
 - For information on adding a RequisitePro project to a Rational project,
    refer to the Rational Suite Administrator's Guide on the Rational
    Solutions for Windows Online Documentation CD. You must add a RequisitePro
    project to a Rational project if you want to integrate RequisitePro with
    Rational ClearQuest®.
  
 - For information on setting up the integration between RequisitePro and
    ClearQuest, refer to the Rational Suite Administrator's Guide on the
    Rational Solutions for Windows Online Documentation CD. For step-by-step
    instructions on associating ClearQuest records with RequisitePro
    requirements, refer to Tool Mentor:
    Managing
    Stakeholder Requests Using Rational ClearQuest and Rational RequisitePro.
 
 
About the RequisitePro Use-Case Project Template
The Use-Case Template provides the following RequisitePro requirements types,
which map to the most important traceability items as defined in Concepts:
Traceability. The template also provides additional requirement types
that are commonly used on projects. 
  
  
    
      
        | RUP
          Traceability Item | 
        
          RequisitePro Requirement Type | 
       
      
        | User/Stakeholder
          Needs (from Vision) | 
        STRQ:
          Stakeholder Request requirement type.  A Need is identified by
          marking it with a priority. ("High" priority indicates a
          "need".) | 
       
      
        | Product
          Feature (from Vision) | 
        FEAT:
          Feature requirement type | 
       
      
        | Supplementary
          Requirement (from Supplementary
          Specifications)  | 
        SUPL:
          Supplementary requirement type | 
       
      
        |  Use
          Case | 
        UC:
          Use-Case requirement type | 
       
      
        | Use
          Case Section (sections of a detailed use
          case) | 
        UC:
          Use-Case requirement typeas child requirements of a parent use case
          (see Hierarchical relationships overview in the
          RequisitePro online Help). | 
       
      
        | Design
          Element (from the design
          model) | 
        Managed
          in Rose. See Integrated Use-Case Management in
          the RequisitePro online Help. | 
       
    
   
  
 
You have the option of introducing a separate requirement type for the Use
Case Section rather than using hierarchical use-case requirements.  This is
useful if you want your project's Use Case Sections to have different
attributes, access privileges, or traceability rules (for example, to ensure
that Test Cases are traced to Use Case Sections and not to Use Cases). 
Tool Steps
To set up RequisitePro for a project, follow these steps: 
  - Create a project in
    RequisitePro
 
  - Set up project security
 
 
  - Click File > New > Project.
    The Create Project dialog box appears.
  
 - Click the Use-Case Template icon, and click Create. The
    RequisitePro Project Properties dialog box appears.
  
 - Type a name for the project. The Directory text box shows the
    directory in which
    the project files will be stored. Either accept the default directory or
    click the Browse button to navigate to another directory.
  
 - From the Database drop-down list box, click the appropriate database to
    use with the project. If you choose Oracle or SQL Server, click Properties;
    complete the appropriate information in the Database Properties dialog box;
    and click OK.
  
 - Type a description for the new project, and click OK to close the
    dialog box.
  
 - At the prompt asking you whether you want RequisitePro to create a new project directory, click Yes.
    RequisitePro creates the new project.
  
 - Click Close to close the Create Project dialog box. Your new
    project includes predefined document types, requirement types, and
    attributes. You can review or modify these by selecting File
    > Properties and clicking the corresponding tabs.
 
 
Because RequisitePro allows multiple users to access the same project
documents and database simultaneously, project security is crucial. You can
enable or disable security in a project, depending on the needs of the group.
With security enabled, users belong to groups, and RequisitePro administrators
assign group-specific permissions. The permissions determine the amount or kind
of access users have to projects. 
All RequisitePro users can create a new project. When you create a new
project, you are considered the project administrator and are automatically
placed in the Administrators group. After you create the project, you (and other
project administrators) can define other users and groups. 
If security is not enabled, any user can open the RequisitePro project. When
you first open an unsecured project, RequisitePro allows you to log on as the
user name in the Default Project Logon field in the Options dialog box
(click Tools > Options), as your Windows logon name, or as a user name of your choice. The user
name is added to the project Administrators group list. 
 
Any project administrator can enable security, modify User and Administrator
lists, and assign passwords for other users. If security is enabled, the Project
Logon dialog box appears each time a user opens the project. 
To set project security in RequisitePro: 
  - Click File > Project > Security.
    The Project Security dialog box appears.
  
 - Select the Enable security for this project check box.
    Three default groups are added to the Groups list: Deleted Users,
    Administrators, and Users.
  
 - Click OK.
 
 
To add a user group: 
  - In the Project Security dialog box, click the Add button
    below the Groups list. The Group Permissions dialog box appears.
  
 - Type a name for the group.
  
 - Select the group project permissions.
  
 - Edit the document and requirement type permissions.
  
 - Click OK.
 
 
To add a user to a group: 
  - In the Project Security dialog box Groups list, select the group that you
    want to contain the user.
  
 - Click the Add button adjacent to the Users of Group list.
    The Add User dialog box appears.
  
 - Type a user name, new password, and verification password.
 
    Note: The New Password and Verify fields are encrypted,
    displaying a symbol for each of the 14 maximum characters. Remember: user
    names and passwords are case-sensitive.
   - If the user has an e-mail address, type it in. This e-mail address is
    necessary for participating in RequisitePro discussions via e-mail.
  
 - Click OK. The Project Security dialog box reappears. The
    user is added to the group list.
  
 - Click OK.
 
 
For More Information
  Refer to the
topic Setting project security (Index: project commands > security)
in the RequisitePro online Help.
 
 
 
Copyright 
© 1987 - 2001 Rational Software Corporation
 
 |  | 
 
 
    
 |