IPD-standalone software projects are IPD requirement management methods for independent software development. They manage large-scale software development with high quality and efficiency through structured processes and powerful cross-project collaboration capabilities, including raw requirements, system features, R&D requirements, tasks, and bugs, among which tasks and bugs are activities generated and problems found during requirement implementation, respectively.
Table 1 lists the important operations for IPD-standalone software projects.
Table 1 Operation description for IPD standalone software projects
Function |
Description |
Related Operation |
Raw Requirements (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. |
- Creating RRs
- Processing RRs
|
Feature Tree (FT) |
The feature tree contains the functions of 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 sub-requirements in this hierarchy: SF > IR > US.
|
|
R&D Requirements (IR/US) |
There are two work item types under R&D requirements:
- Initial requirement (IR)
IRs are requirements re-described in accurate language, complete background, and standard format from the perspective of customers/markets.
- User Stories
User stories are brief description of functions that are valuable to users or customers, which comply with the INVEST principles. User stories are decoupled and can be delivered independently, which is the basis of agile sprint delivery.
|
- Creating R&D Requirements
- Breaking Down R&D Requirements
- Processing R&D Requirements
|
Task |
Tasks are activities generated to achieve a certain goal. |
|
Bug |
Bugs are problems found in the project. |
- |
