Administrating Req Pro


Published on

This presentation guides you around the project properties and security windows of Rational RequisitePro. It also shows how to create a new ReqPro project.

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Administrating Req Pro

  1. 1. Administering RequisitePro Project Management Discipline June 7, 2009
  2. 2. Precursor <ul><li>In order to understand the material in this course, you should have equivalent knowledge of the following courses: </li></ul><ul><ul><li>Introduction to RequisitePro. </li></ul></ul>
  3. 3. Overview <ul><li>The purpose of this presentation is to demonstrate: </li></ul><ul><ul><li>how to manage ReqPro projects, </li></ul></ul><ul><ul><li>how to manage ReqPro documents, </li></ul></ul><ul><ul><li>how to manage ReqPro requirements and their attributes, </li></ul></ul><ul><ul><li>how to manage ReqPro project security, </li></ul></ul><ul><ul><li>how to link ReqPro projects. </li></ul></ul><ul><li>At the end there are exercises to test what you have learnt. </li></ul>
  4. 4. Creating A Project <ul><li>Execute the File->New->Project command. </li></ul><ul><li>Select the project template that you wish to use for your project. </li></ul><ul><li>Complete the project properties and click ‘Ok’. </li></ul>
  5. 5. Creating A Project Template <ul><li>With the ‘Create Project’ window displayed, select ‘Make New Template’. </li></ul>
  6. 6. Select An Existing Project <ul><li>Project templates are created from an existing ReqPro project. </li></ul><ul><li>The existing project will have had its requirements, documents and security configured. </li></ul><ul><li>A template may optionally contain the data from an existing project – this is the easiest way to make a copy of an existing project. </li></ul>
  7. 7. <ul><li>A unique name for the template. </li></ul><ul><li>Where your ReqPro project templates currently reside. </li></ul><ul><li>An optional text file describing the purpose of the template. </li></ul><ul><li>A windows type icon for display in the operating system. </li></ul>Setting Template Properties
  8. 8. General Project Properties <ul><li>Open a project and execute the ‘File->Project Administration->Properties’ command in order to customize a project. </li></ul><ul><li>The general tab allows some of the properties that were entered when the project was created, to be changed. </li></ul>
  9. 9. Administration History <ul><li>ReqPro records all changes made during the lifetime of a project. </li></ul><ul><li>Click ‘History’ to display all changes that have been made to the project properties. </li></ul><ul><li>Click on a change revision # to display the details about that change. </li></ul>
  10. 10. Maintaining Requirement Types <ul><li>Click on the ‘Requirements Type’ tab to display all of the available requirements for the project. </li></ul><ul><li>Click on a requirement type and click ‘Edit’ to display its properties. </li></ul><ul><li>Click ‘Add’ to create a requirement. </li></ul><ul><li>Click ‘Delete to remove a requirement type (requirements of that type may not exist in the project). </li></ul>
  11. 11. The Requirements Type Window <ul><li>A unique name for the requirement type. </li></ul><ul><li>An optional description for the type. </li></ul><ul><li>Allow this requirement type to be referenced by external projects. </li></ul><ul><li>A unique identifying tag for the requirements. </li></ul><ul><li>Customize how the requirement type appears in a document. </li></ul>
  12. 12. Maintaining Attributes <ul><li>Click on the ‘Attributes’ tab. </li></ul><ul><li>Select the requirement type from the drop-down list. </li></ul><ul><li>Select the attribute name from the attribute list. </li></ul><ul><li>From here you may: </li></ul><ul><ul><li>Add a new attribute, </li></ul></ul><ul><ul><li>Edit the selected attribute, </li></ul></ul><ul><ul><li>Delete the selected attribute, </li></ul></ul><ul><ul><li>Move the attribute up in the list, </li></ul></ul><ul><ul><li>Move the attribute down in the list. </li></ul></ul>
  13. 13. Editing Attribute Values <ul><li>Clicking on the ‘Edit’ command brings up the attribute edit window. </li></ul><ul><li>The attribute ‘Label may be changed. </li></ul><ul><li>The attribute ‘Type’ may not be changed. </li></ul><ul><li>The attribute values, (if applicable) may be edited. </li></ul><ul><li>‘ Hidden From Display’ allows an unused attribute to be retained for future use. </li></ul><ul><li>‘ Change Affects Suspect’, means that this attribute is significant to the traceability of the requirement. </li></ul>
  14. 14. Selecting Document Properties <ul><li>‘ Save Documents in RequisitePtro Format’, prevents the document from being edited outside of ReqPro. </li></ul><ul><li>‘ Enable Extended Editing of Documents’ allows requirements to be edited through tools integrated with ReqPro (always leave box this checked). </li></ul>
  15. 15. Document Templates <ul><li>ReqPro is installed with several default document templates, located in the RequisitePro installation directory ‘outlines’ folder. </li></ul><ul><li>You will want to customize these templates for your own projects. </li></ul><ul><li>Alternatively you may have existing templates that are shared by all users of ReqPro .. the path to these templates is typed into the ‘Document Outlines’ field of the options window that appears when the ‘Tools->Options’ command is executed. </li></ul><ul><li>In order for ReqPro to recognize a file as a template, a ‘.def’ file is needed in the ‘Outlines’ directory containing: </li></ul><ul><ul><li>The name of the document type, </li></ul></ul><ul><ul><li>A description of the document type, </li></ul></ul><ul><ul><li>The name of the document template. </li></ul></ul><ul><li>Each separated by a newline. </li></ul>
  16. 16. Maintaining Documents <ul><li>Click on the ‘Document Types’ tab. </li></ul><ul><li>Select a document to edit and click the ‘Edit’ button. </li></ul><ul><li>Enter: </li></ul><ul><ul><li>a name for the document, </li></ul></ul><ul><ul><li>an optional description of the document, </li></ul></ul><ul><ul><li>a 3 letter file extension for the document, </li></ul></ul><ul><ul><li>the default requirement type (used by ReqPro when importing a document of this type). </li></ul></ul>
  17. 17. Document Templates <ul><li>Select the document type from the list of templates that are made available to ReqPro. </li></ul>
  18. 18. Maintaining Groups <ul><li>Select ‘File->Project Administration->Security’ </li></ul><ul><li>Security is enabled in order for users to be requested a username and password in order to open the project. </li></ul><ul><li>With security enabled, every user is made a member of a group. </li></ul><ul><li>Users are added, deleted, edited or moved between groups. </li></ul><ul><li>Users are never removed from the project, but will be moved to the ‘Deleted Users’ group, when deleted. </li></ul>
  19. 19. Maintaining Users <ul><li>With the user selected, click the ‘Edit’ ‘Users of group’ button. </li></ul><ul><li>A screen pops-up which allows you to change: </li></ul><ul><ul><li>the users name, </li></ul></ul><ul><ul><li>the users password, </li></ul></ul><ul><ul><li>the users email address, </li></ul></ul><ul><ul><li>and if the user is connected to and LDAP server, the user may be selected to login to ReqPro using their network username and paswword. </li></ul></ul>
  20. 20. Setting Group Editing Permissions <ul><li>To restrict a user’s abilities in ReqPro they must be added to a group and that groups access is edited by clicking the group ‘Edit’ button. </li></ul><ul><li>The ‘Group Permissions’ window restricts general access to: </li></ul><ul><ul><li>project administration, </li></ul></ul><ul><ul><li>this window, </li></ul></ul><ul><ul><li>document types that the user may edit, </li></ul></ul><ul><ul><li>requirement types that users may edit. </li></ul></ul>
  21. 21. Setting Group Document Permissions <ul><li>To restrict a group’s access to a document type, select the document name and click ‘Edit Permissions’. </li></ul><ul><li>The ‘Document Type Permissions’ window allows restriction to be set as: </li></ul><ul><ul><li>no access, </li></ul></ul><ul><ul><li>read-only, </li></ul></ul><ul><ul><li>read and update only, </li></ul></ul><ul><ul><li>read, update and create only. </li></ul></ul>
  22. 22. Setting Group Requirement Permissions <ul><li>Select the requirement type that you wish to restrict access to and click the ‘Edit Permissions’ button. </li></ul><ul><li>The requirement type permissions window allows access restriction to be set to: </li></ul><ul><ul><li>requirement type read-only, </li></ul></ul><ul><ul><li>requirement type update, </li></ul></ul><ul><ul><li>requirement type update and delete, </li></ul></ul><ul><ul><li>requirement type traceability read-only, </li></ul></ul><ul><ul><li>requirement type traceability create, </li></ul></ul><ul><ul><li>requirement type traceability mark as suspect, </li></ul></ul><ul><ul><li>requirement type traceability clear suspect. </li></ul></ul>
  23. 23. Setting Group Attribute Permissions <ul><li>ReqPro allows restricted access to the requirement type’s individual attributes. </li></ul><ul><li>Select the requirement type attribute and set whether the group has access to change that attribute. </li></ul>
  24. 24. Setting Attribute Value Permissions <ul><li>If the attribute is an enumerated type, access may be restricted to its individual values. </li></ul><ul><li>Select the attribute value and click on ‘Edit Permissions’. </li></ul><ul><li>Restrict access to read-only for the particular value by unselecting the ‘Update’ box. </li></ul>
  25. 25. Linking Projects <ul><li>In order to trace requirements to another ReqPro project, an administrator needs to set the project location. </li></ul><ul><li>Enter the ‘File->Project Administration->External Projects’, click on the ‘Add’ button and browse to locate the project that is to be linked. </li></ul>
  26. 26. Exercises <ul><li>Create a new ReqPro project from the ‘Use Case’ template and name it ‘Use Case Project’. </li></ul><ul><li>Create a use case document type for the project using the RUP use case template that comes with ReqPro. </li></ul><ul><li>Create a use case requirement type and give it a ‘Status’ attribute taking the following values: </li></ul><ul><ul><li>Proposed, Confirmed, Deployed, Deleted. </li></ul></ul><ul><li>Create groups of users named ‘Project Manager’ and ‘Tester’. </li></ul><ul><li>Set the following restrictions: </li></ul><ul><ul><li>Only project managers may change the use case status to ‘Confirmed, </li></ul></ul><ul><ul><li>Only testers may set the use case status to ‘Deployed’. </li></ul></ul><ul><li>Create a ReqPro project named ‘External Requirements’. </li></ul><ul><li>Create a supplementary requirement type in the ‘External Project’. </li></ul><ul><li>Allow the use cases to be linked to supplementary requirements via traceability. </li></ul>