System Requirements & Functions

is aBacklog Item Type
is refined fromStakeholder Needs
is formated byLightweight Business Case (LBC), NABC, Stakeholder Story, Use Case
definesFeature/Application, System Increment
is constrainted byQuality Attributes & Constraints (QA&C)

Systems are described at the top level by System Requirements and Functions (features). Requirements only describe abilities or properties in the “problem area”, so they are still independent of concrete system solutions. The solution space is already limited by the Quality Attributes & Constraints .

Interfaces to neighboring systems in the environment and their properties are also specified here. For this a sogn. Context diagram created and used.

Functional System Requirements of the stakeholders are often written in the form of User Stories * and later specified using Use Cases“. Alternatively Behavior Driven Development can be used to specify and test the system’s behavior.

*) P4 introduces the term “Stakeholder Stories” in this context, since they are suitable for the specification of requirements of all stakeholders, not just the user.

**) Non-functional requirements (NFRs) are are called Quality Attributes and are not written directly into the System Backlog in P4 (see Quality Attributes & Constraints )


Further suitable links:

System Requirements on Wikipedia

Events Roles Groups Artifacts
Cluster Planning

Cluster Sync

Cluster Backlog Refinement

Cluster Review


Cluster Product Owner

Cluster System Engineer


Portfolio Owner

Portfolio Architect

Team Product Owner Group

Team System Engineer Group


Cluster Product Owner Group

Cluster System Engineer Group

Inspectable Results

Team DoD


Usable Knowledge & System Increment

Cluster DoD


Systems & Applications

System Platforms & Variants

Organisation DoD