Modern Enterprise Software Delivery System Architecture
Overview: In the second episode of our podcast series, Building a Better Software Delivery Platform, VP of Product Engineering David Rizzo joined DevOps Solution Architect Rick Slade to discuss the architecture of a software delivery system and explain how Compuware has integrated new tools, processes and automation into its delivery system.
In the second chapter of Compuware’s “Building a Better Software Development Platform” podcast series, DevOps Solution Architect Rick Slade focused on the architecture of a modern software delivery system. This conversation gave real-world examples of how organizations can approach the modernization of their software delivery system and what that process looks like in practice.
Rick gave a short overview of the Software Delivery System (SDS) and the role Agile practices can play in improving that system. He then named three critical components of the SDS: automation, integration, and measurement. Automation plays a huge role in saving time and increasing the quality of software delivery. Automated activities need to fit into the software delivery lifecycle seamlessly, as do all of the various technologies needed. The ability of these tools to integrate into the SDS and work well together is key to the success of the system. And continuous measurement of the tools and processes involved are vital to ensuring the efficiency and effectiveness of your SDS.
Special guest David Rizzo, Compuware Vice President of Product Engineering, joined Rick to discuss the processes, tools, and organization involved in transitioning Compuware’s SDS from traditional waterfall development to an Agile model, built to meet customer needs as efficiently as possible. David touched on the tools involved, like ISPW and BitBucket for source change management and zAdviser for continuous measurement, as well as the importance of automation.
Overall, David explained how
Compuware treats its SDS like a product, with a product owner, planning meetings, and tracking through JIRA. Compuware is able to deliver code changes in almost real time thanks to a 24-hour continuous integration cycle where developer modifications are applied daily, then built, tested and deployed nightly, thanks to automated processes.
David stressed that building a new SDS, incorporating new tools, and automating processes is a continuing exercise. He likened Compuware’s experience to changing a car’s wheels as it drove down the road, stressing the need for planning and taking changes one step at a time, with an eye toward continuous improvement.
For more in-depth information on how Compuware has built its SDS, listen to Chapter Two: Modern Enterprise Software Delivery System Architecture. You can find all of the episodes in the series, as well as recordings of the Office Hour with Rick Slade Q&A session at www.compuware.com/goodcoding.
Be sure to check out the next episode in the series, Chapter Three: Managing Software Delivery Platform Evolution, in which Rick discusses how to plan a new SDS, execute that plan, and effectively manage a modern delivery
Latest posts by Matthew DeLaere (see all)
- Modern Enterprise Software Delivery System Architecture - May 18, 2020
- Key Characteristics of a Modern Software Delivery System - May 11, 2020
- Planning Your Migration to COBOL V6 - April 23, 2020