New End-to-End Project Deployment Process in Solution Manager 7.1 and 7.2
- by Michael Demuth, Chief Support Architect, SAP SE
- November 9, 2016
Learn about developments done with multiple large corporations for the IT Requirement-to-Deploy process in SAP Solution Manager 7.1 and 7.2. Follow the management of the IT Service Management (ITSM) and Application Lifecycle Management (ALM) spaces from requirement management, to design, build, test, and deployment in an integrated fashion.
Reading this article, you will learn about:
- The scope of the Requirement-to-Deploy application
- The end-to-end Requirement-to-Deploy process delivered with Solution Manager 7.1, Support Package 14, and Solution Manager 7.2, Support Package 3, starting in November 2016
- The implementation techniques that overlap with standard Change Request Management (ChaRM) or the IT Portfolio and Project Management (ITPPM) standard
- Requirement-to-Deploy customization
- The Requirement-to-Deploy process that inherits some smaller applications, such as deployment automation or automatic retrofit. The latter are also part of the Focused Build for SAP Solution Manager solution.
- The main customization of the Requirement-to-Deploy processes such as requirement management, change management, project management, test management, release management, and deployment management
- The user interface (UI) technology usage for SAPUI5, WebUI, and Web Dynpro (if user interfaces are modified you need to know these three technologies)
- The difference between the standard request for change (RfC) and the maintenance cycle of ChaRM, compared with work packages, work items, and release cycles of Requirement-to-Deploy
- The use of process modeling, solution documentation, and the tools used in Solution Manager 7.1 and 7.2
- How testing is integrated into the Requirement-to-Deploy process, and how test-defect and defect-correction transactions are enhanced compared with ChaRM
- How release management and the deployment automation are integrated. Note that deployment automation can also be used for standard ChaRM.
The Requirement-to-Deploy focus solution is free of charge for SAP customers with a premium support contract. All other customers can acquire it on a rental basis. It can be downloaded from the SAP Portal and is delivered as an add-on with the technical name ST-OST. Requirement-to-Deploy is also known as the Focused Build for SAP Solution Manager solution.
The allover Requirement-to-Deploy process in Solution Manager 7.1 and 7.2 spans from project preparation through a discovery process in business, ending up in creating business requirements prior to handing the project over to the IT department.
I describe the end-to-end Requirement-to-Deploy process as delivered as of the Focused Build for Solution Manager solution within Solution Manager 7.1 and 7.2. The Focused Build solution provides a requirement process that is deeply integrated into a newly delivered release management process. The integration into IT Portfolio and Project Management (ITPPM) projects is the basis of dashboard-driven progress analysis, such as milestones, waves, sprints, and requirement progress.
Different than Change Request Management (ChaRM), the application comes with many functional enhancements, dashboards, and SAPUI5 components. After a process description, the main customization is shown enabling ChaRM users to adjust the Focused Build solution to their company’s needs. The table at the end of the article shows the main functional differences between ChaRM and the Focused Build solution.
I cover functionality available in the Solution Manager 7.1 Focused Solution Support Package 14, and also provide details about the Solution Manager 7.2 Focused Solution Support Package 3, which is to be delivered as of November 2016. Since Solution Manager 7.1 runs out of maintenance at the end of 2017, the screenprints in this article are exclusively based on 7.2.
Would you like to see this full item?