Getting started with creating and managing requirements

If you are a product manager or requirements analyst lead, follow these guidelines to get yourself and your team started with creating and managing requirements.

Before you begin

Administrators must complete the administrative tasks that are associated with creating the Jazz repository and a requirements management project area. Product managers and requirements analysts must review the requirements management process to see an example of the workflow to get started.

Procedure

  1. Use the Artifacts page and other project pages to create, view, and manage project artifacts.
  2. Upload external documents and import comma-separated values (CSV), Microsoft Word, OpenDocument, and Rich Text Format documents to the project, as needed. The documents can include preliminary information such as problem statements, stakeholder needs, and a project management plan. You can extract requirement artifacts from documents as you import them or from documents that are already in the project.
  3. Create requirements. Create high-level requirements to describe the product features. Create detailed requirements to elaborate the feature requirements. You can create requirements as individual artifacts in rich-text documents or in the structured content of a module. You can also run reports.
  4. Create supporting artifacts to help elaborate and give context for the requirements.
  5. Use the Project Dashboard to track recent activities and other project properties. You can also use saved views and filters to manage requirements on the Artifacts page and other project pages.
  6. Create traceability by linking high-level requirements, detailed requirements, and supporting artifacts. You can also trace requirements to other applications across the software development lifecycle to complete these tasks:
    • Implement requirements with development plans and work items
    • Validate requirements with test plans and test cases
    Team members can select traceability profiles, which are created by administrators, to enable suspect traceability tracking to watch for changes in linked artifacts. The tracking is based on link type, artifact type, and attribute criteria.
  7. Create collections or modules to organize requirements into related groups to prepare for requirement reviews and other management activities. You can use collections and modules to link requirements to development plans and test plans.
  8. Initiate requirements reviews. Create review for requirements collections or modules or individual artifacts, and add team members to serve as reviewers and approvers.

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