Requirement Model

First, let's look at the work objects in this requirement model: RR, SF, IR, SR, and AR.

**Table 1** Work objects of IPD-system device projects
Work Object	Description
Raw requirement (RR)	An original problem or demand described from the perspective of internal and external customers. Customer requirements are a type of RRs. This type of requirements must be analyzed and reviewed by the Requirement Management Team (RMT) and Requirement Analysis Team (RAT).
System feature (SF)	A major capability of a version that supports problems (PBs). In principle, a system feature is a set of key selling points (highlights) of a product package. Each feature is an E2E solution that meets customers' specific business requirements. Some features can be sold independently via license control.
Initial requirement (IR)	A requirement re-described accurately (with a complete background and standard format) from the perspective of internal and external customers and markets. IRs can be produced: By breaking down RRs or SFs. From product plans.
System requirement (SR)	A functional or non-functional requirement described from the R&D perspective. This type of requirements is visible to the outside and testable. Functional requirements are scenario-specific, while non-functional requirements are about system costs, global quality attributes (mainly DFX), and technical limitations.
Allocated requirement (AR)	A functional or non-functional requirement that an SR is broken down into for subsystems/modules to deliver, based on the division of responsibilities of basic-level organizations.