Continuous delivery of software-driven innovation on System z
In a traditional IT organization, it is not uncommon to find applications spanning multiple platforms, each built and managed with a different set of processes, tools, and skills. These multitier systems are composed of back-office applications such as packaged apps, data warehouse, mainframe, mid-range applications and front-office web, rich client or mobile applications. The complexity of building, testing and managing the release process of the parts and pieces that make up these applications can be overwhelming even for the most disciplined IT organizations.
A sensible approach is to have an automated and consistent build, test, deploy, and release process through all stages of the Software delivery. This approach ensures that you are building all the parts that are needed and only the parts needed. It ensures that the application remains whole as changes come in and the project moves through the cycle of development, QA, and Production. For example, in the mainframe z/OS environment, organizations are generally building only the changes, the deltas, to the application and deploying them into the environment perhaps 3-4 times a year, whereas a mobile application may be updated weekly. And if the mobile application relies on the services that are provided by the back-office applications such as mainframe, the development, deployment, and release plans of both these systems must be planned and coordinated.
It requires a common set of development and testing tools that teams supporting the distributed and mainframe platforms can use. Furthermore, it requires a Deployment Automation tool that can automate deployments across all the platforms that is utilized in the enterprise. Maintaining separate tools for different teams that are based on their platform is not cost-effective, or in-line with DevOps principles of Collaborative development, Continuous testing, and Continuous Release and Deploy. The consistent development practices can help ensure that teams are using reliable repeatable deployment across the platforms to provide the true business value.
Over the next few weeks, we’ll discuss this collaborative approach for continuous software delivery, and how IBM integrated development and operations tools and processes can help optimize the lifecycle of your applications. Join us to learn about the DevOps architecture.
IBM DevOps solution series: Best practices and tools for continuous delivery of software-driven innovation on System z.
August 7th: “Accelerating the delivery of multiplatform applications” - Mobile, social, big data and cloud technologies are driving the demand for new, faster and more frequent approaches to software delivery across all platforms, middleware and devices. The goal is to push out significantly more features in each release and get more releases out the door, while ensuring compliance and quality. You often find problems – or gaps– with Software delivery that must be mitigated under these increasing demands. Hayden Lindsey and Mike Perera will discuss how the IBM DevOps solutions address culture, process and tools integration across the software delivery lifecycle.
August 14th: “Continuous business planning to get cost out and agility in” - Can you respond quickly to business needs and customer demands without incurring excess cost? Rick Slade and Richard Szulewski will discuss how you can maximize your current investments and reduce maintenance of your application portfolio.
September 4th: “Collaborative development to spark innovation and integration among teams” – Mobile, social, big data and analytics demand a development process that is fast and affordable and cannot exist in disjoint silos. Regardless of your deployment platform, teams need to integrate and collaborate. Tim Hahn and Danny Mace will discuss the benefits of unified development environments and middleware so you can keep the focus on high quality and innovative code. Follow @hanhtj
September 11th: “Continuous testing to save costs and improve application quality” - Automating manual, repetitive tasks, like build, regression and integration testing can help teams move more quickly and meet customer needs while staying on time and budget. Join Rosalind Radcliffe and Marty Shelton to discuss service virtualization techniques like automating testing and debugging. Follow @rosalindrad