Help Center/ CodeArts Req/ User Guide/ Managing IPD-Standalone Software Project Requirements/ Requirement Management Process
Updated on 2026-10-26 GMT+08:00
View PDF
Share

Requirement Management Process

IPD-standalone software projects are designed for large-scale software development scenarios based on structured processes and powerful cross-project collaboration. They help you manage development with efficiency and quality, covering raw requirements (RRs), system features (SFs), R&D requirements, tasks, and bugs. During requirement implementation, tasks are the activities generated, and bugs are the problems found.

Figure 1 IPD-standalone software projects

Table 1 lists the important operations for IPD-standalone software projects.

Table 1 Operation description for IPD-standalone software projects

Function

Description

Billing

Raw requirement (RR)

RRs are raw problems or requirements described from the perspective of customers. Customer requirements are a type of RRs, which need to be analyzed and reviewed by the RMT/RAT. For details about how to create and manage RRs, see Creating and Managing RRs.

You need to upgrade the package to the professional or higher edition. For details about the billing change, see Impact on Billing After Specification Change.

Feature tree (FT)

FTs contain feature sets and SFs.

  • Feature set: aggregates and manages SFs. Multi-level relationships can be established for the feature set, and the feature tree version snapshot and snapshot comparison functions are provided.
  • SF: feature that brings benefits. SFs can have different types of child work items in this hierarchy: SF > IR > US.

System feature (SF)
SFs are major capabilities of offering requirements or services to support problems (PBs).
  • Offering requirements: a group of complete, consistent, and series of formal requirements planned by product managers/planning representatives.

    In principle, SFs are a set of key selling points (highlights) of an offering. Each SF is an E2E solution that meets customers' specific business value requirements. Some SFs can be sold separately via license control.

  • PBs: challenges and opportunities faced by customers (customer strategies and pain points), that is, key problems solved by a product or service for customers. Resolving key problems can bring core value to customers.

For details about how to create system features, see Creating System Features.

R&D requirement (IR/US)

There are two work item types under R&D requirements:

  • Initial requirement (IR)

    IRs are re-described accurately, with complete background, in standard format, and from the perspective of customers/markets.

  • User story (US)

    User stories are brief descriptions of functions that are valuable to users or customers, which comply with the Independent, Negotiable, Valuable, Estimable, Small, and Testable (INVEST) principles. USs are decoupled and can be delivered independently, which is the basis of agile sprint delivery.

For details about how to create and manage R&D requirements, see Creating and Managing R&D Requirements.

Task

Tasks are activities with a certain goal. For details about how to create and manage tasks, see Creating and Managing Tasks.

Bug

Bugs are problems found in a project. For details about how to create and manage bugs, see Creating and Managing Bugs.
Parent Topic: Managing IPD-Standalone Software Project Requirements