Cloud Application Lifecycle Management: create feature from requirement
In this Blog post we will describe, how it is possible to create Feature, connected to a Requirement and which phases it will have in it´s lifecycle then. The steps are described for the CALM solution, connected with SAP S/4HANA Cloud 3SL landscape.
To start the process we need “Requirements” app. There we need to select correct Project and click Create -> Requirement:
Enter requirement Title and Description:
Below you can assign test-cases to the requirement:
You can add external references:
Assign necessary attributes and save:
Once the requirement is created, it can be approved:
Once the requirement is ready, we can move to feature´ creation:
For the feature we need to enter following information:
Then Save and Close.
Once you are done with the feature creation, it is bounded to the requirement:
It is possible to have several features for the requirement.
Now let´s click on the created feature. This will lead us to the feature screen:
We can assign there transport(s) to the feature:
The possibility to assign several transports to the one feature is provided, in order to follow dependencies, which feature could have with other functions/customizing items. The feature itself will be located in one transport request.
Once the feature is ready, we can Start Implementation:
Afterwards we get possibility to Deploy feature in Test system:
Once the deployment is started, we need to wait, until feature is deployed in Test system:
Currently it is necessary to update deployment status manually:
Once the deployment to Test tenant is done, we need to Approve the feature for the deployment in Prod tenant:
Now we can deploy it to Prod tenant:
Update the status and check, if the feature has been deployed:
As the last step we Confirm Deployment:
If we go back to the “Requirements” app we will see “Deployed” status for the feature there as well:
In future releases of CALM, deployment orchestration-related functions will be extended further, what enables usage of CALM actively not only from organisational, but from orchestration perspective as well.