< Previous | Next >

Lesson 2.1: Create associations with folders and files

In this lesson, you will create associations between requirements and a project folder and a file.

The Resource linkable domain in the IBM® Software Delivery Platform includes domain elements that are common to all applications in the Eclipse SDK; these common elements include projects, folders, and files. In this lesson you will create a folder named Secure Payment that a developer could use in a project to group all design elements related to secure payment processes for the application users. You also create a file within the folder named Customer Authentication that a developer could use to make notes related to secure identification and authentication of application users. By associating the Customer Authentication file with the Customer ID glossary requirement in Rational® RequisitePro®, you ensure that the development team will begin to use consistent terminology as the team works on customer security design.

Notice that requirements in Rational RequisitePro are listed in the Requirement Explorer view beginning with a tag and followed by the requirement name. The tag, which includes a textual abbreviation of the requirement type and a number, is a unique identifier within the requirements project; for example, FEAT1 represents the first feature requirement that was created in the project. Requirements can be rearranged and renumbered in Rational RequisitePro, but each tag remains unique within the project.

To create associations with folders and files:

  1. In the Project Explorer view, right-click My Tutorial Project and click New > Folder.
  2. In the New Folder window, type the folder name Secure Payment and click Finish. The new folder is displayed in the project.
  3. Right-click the Secure Payment folder and click New > File.
  4. In the New File window, type the file name Customer Authentication and click Finish. The new file is displayed in the folder.
  5. In the Requirement Explorer view, expand the Features and Vision folder and expand the Web Shop System folder.
  6. Drag the requirement FEAT1 Secure payment method from the Requirement Explorer view to the Secure Payment folder in the Project Explorer view. An association is created between the requirement and the folder.
  7. In the Requirement Explorer view, expand the Glossary folder.
  8. Drag the glossary requirement TERM4 Customer ID from the Requirement Explorer view to the Customer Authentication file in the Project Explorer view. An association is created between the requirement and the file. The file is marked with a horizontal arrow that indicates a direct link to a proxy requirement, as described in the next lesson. The requirement is marked with a diagonal arrow that indicates an indirect link with traceability to the proxy requirement.
< Previous | Next >

Feedback