The following diagram presents an example of the requirements definition process. Click on any box for more information. Each section of the diagram is explained in more detail below.
The business analyst sets up a project in Rational® Requirements Composer by completing these tasks:
The business analyst collects input regarding the business problem by completing these tasks:
The business analyst creates a series of documents and other artifacts to express the current system and the proposed solution. Artifact types can include:
The business analyst creates requirements from text and other elements in the artifacts by completing these tasks:
The business analyst invites other team members to review the assessment documentation and any supporting artifacts by completing the following tasks:
To manage requirements, the business analyst adds the requirements to Rational RequisitePro® or Rational DOORS®. The analyst can also import requirements from Rational RequisitePro.
See Managing requirements with Rational RequisitePro and Managing artifacts with Rational DOORS.
After requirements are defined, you can use Collaborative Application Lifecycle Management (C/ALM) integrations to link requirements to development work items and test artifacts in other products based on Jazz technology. See Collaborative Application Lifecycle Management (C/ALM).
Requirements Management practice links on IBM developerWorks