Getting started for requirements management project administrators

If you are a requirements project administrator or requirements analyst lead, these guidelines can help you get started.

Before you begin

Procedure

  1. Create a requirements project. Select a project template to populate the project with predefined artifact types and a project structure. For more information, see Creating requirements projects.
  2. Add users to the project and assign them project roles. For more information, see Adding and modifying users as members of project areas and team areas.
  3. Optional: Assign permissions at the project level or at a team level. For more information, see Permissions for requirements projects.
  4. Optional: To meet specific project needs, customize the artifact types, attributes, data types, and link types. For more information, see Managing project properties in requirements projects and Creating link types for requirements projects.
  5. Create suspicion profiles to track suspect traceability and to enable team members to watch for changes in linked artifacts, which are based on link type, artifact type, and attribute criteria. For more information, see Creating suspicion profiles and Suspect traceability.
    Important: Suspect traceability is not supported in projects in which configuration management is enabled. However, you can now monitor the impact of changes to linked artifacts using link validity in configuration management enabled projects.
  6. Organize the artifacts in the project by modifying the project folder.

What to do next

You can now begin to create and manage requirements.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki