
Requirements management in SAP Cloud ALM deals with the entities requirement, user story, and feature.
Details about the figure:
- Requirement
- Describes required functionality from business point of view.
- Functionality can be implemented over multiple sprints.
- User Story
- Describes a smaller part of required functionality that can be completed in a few days or less.
- Requirements are broken down into user stories to plan step-by-step implementation.
- Optional task: Functionality to be realized by one dev member daily.
- Feature
- Represents functionality that delivers business value to a target system and is sized to be delivered in a single sprint.
- Functionality that is represented by a feature must be deployed to a target system together.

Description of the requirements driven process:
- Requirement created from solution process → approval process → refined in multiple user stories (and optional in tasks).
- Feature created from requirement with manually assigned user stories.
- Created test cases can be assigned to the requirement and/or to user stories.
- Feature creates/assigns transports.
Other possibilities to work with SAP Cloud ALM (can be discussed):
- Requirement without refinement in user stories → approval process → feature created from requirement (creates/assigns transports) → test cases assigned to requirement.
- User stories created without requirement (no approval process) → feature created without requirement → feature creates/assigns user stories and creates/assigns transports → test cases created and assigned to user stories.