 I guess most of you who own smartphones here and a lot of new application development. It's app economy now, a lot of application development happens via the mobile, and we want to say how application development done via the mobile or for the mobile is still relevant, and how the mainframe is the platform of choice. Mobile is the computing device that most of us use now. We're talking about application development in this whole space from the mobile to the mainframe, and how it's helping DevOps in the app economy. So I want to talk about the importance of system Z, like some of you may already know, is the mainframe platform stands for zero downtime, and how is it still relevant in this age. Then we want to talk about specifically development of applications that are diverse and heterogeneous environment, that spans across multiple platforms, multiple technologies, and how all of that still use the mainframe. We are from the mainframe group within the CA Technologies Division out at Hyderabad. So we want to say how is it still relevant for all of you. Then we want to talk about the linkage between DevOps and the mainframe, and we want to go through instance of an end-to-end automation of the whole life cycle. This is both the process and the application life cycle, and how are we able to automate it from an end-to-end perspective for both application development and application delivery, both aspects. Then finally, we want to show how all of these are orchestrated across the whole life cycle, using the tools that we want to show as an instance, that we want to showcase today, and we end with a quick video demo, which will elaborate these concepts for you very clearly, and we'll leave it out for Q&A. Thank you. So just a quick view of system Z app economy. So we believe it's still the most strategic and the reliable platform. Like I don't know if you know this, but on an average, an American knowingly, unknowingly, spends are actually 15 percent of the transactions are 15 times in a day. Any transaction that he does, actually hits the platform, which is the mainframe knowingly, unknowingly. That's a huge number. So that's why we believe it's going to be strategic. There has been a lot of investment on the mainframe aspect. We want to retain those investments, or we see our customers retaining those investments, and trying to use that as a strategy or a strategic way to have new application development done anywhere, through web, through the mobile, any other app, but still the system of record is system Z. So that's what I want to say. We have application developed to execute mobile to mainframe architectures and managed as a whole, which basically gives you visibility from an end-to-end perspective for a dev and operation persons not siloed. 33 percent of our organization applications are accessible on the mobile devices, and 35 percent of current mainframe applications are even accessible via the Cloud. So this is this big push towards the new technologies and still retaining investments on the mainframe. So it's a picture of a guy who seems to be very worried as to what's going to happen to all my investments that I've done on the mainframe, and how can I make this as a technology enabler as an engine for growth? That's a concern. So like I said, development per se on the mainframe for the mainframe is we have seen and a lot of surveys point to it. We're actually seen also that they are actually legacy and they are declining. But what we are trying to say here is development leveraging the mainframe. It can happen anywhere like on your mobile device or on a distributed platform. All of that go back into the mainframe, and that is new and that's the use case we want to go through today and that's growing. So it's a powerful way to leverage the infrastructure that you have and look for growth. So very interesting statistics, still five billion lines of new cobalt code is being added to the life systems every year. So it's highly relevant. More than 90 percent of adults who own cell phones, 50 percent of smartphones, what it means is they're using that to spend time on retail sites via the mobile devices, which eventually like I said, on an average 15 transactions go back into the mainframe. So what we want to say is in this way, in a way the old and new are kind of converging and your mobile device is the primary computing device and your system Z is the primary platform of choice. Feel free to ask questions anytime. Just quick note on DevOps and mainframe. We really don't want to talk about what DevOps is about. But what we want to say is the important thing about these three aspects, communication, collaboration, and integration, which is also a key aspect of how you do your agile development or agile methodology, integration in your teams. So kind of emphasis that, and we want to say how is that related to the mainframe. So it basically needs a very tight coordination between your development team, your system programmers, and the operations team, and we have an in-house tool called Endeavour. That is an environment that helps both the development and the operations teams to work together and deliver code and deliver tests and deploy them faster. So what we want to say is application development is not for the mainframe. We talked about it. So the development for the mainframe on the mainframe is obviously legacy and declining. But if you're not agile and if you're not going with agility, if you're not releasing quicker, faster time to market, you obviously die. So I'll pause here. I'll have Sirajal take over a little bit more about what we want to say from a DevOps perspective and then a few more things on the complete lifecycle automation. Thank you. Thank you. So before I proceed, basically from here onwards, what I would like to extend upon what Ravindra has been saying, the challenges of DevOps and the agile development. These two things DevOps and agile development are not separate things. I mean, they are both complementary to each other. Whenever we talk of DevOps practices, agile development and agility is inbuilt practices within the DevOps practices. And how to address those challenges of DevOps, the traditional challenges that DevOps tries to address, how we address those challenges with the help of the application development tools, application development lifecycle tools that we have. So before we proceed until this time, do any of you have any questions? Then we proceed. So this diagrammatic representation is a kind of solution and integrated solution where if you see on the left-hand side, we have couple of product solutions like FileMaster and InterTest. These are testing tools on the main frame side. And on the right-hand side, again, CA-Gen and Plex, these are development languages tools. And on the base, you have CA-Endaver and CA-Harvest. So these are software change management tools and applications. So here, there is a convergence, as Ravindra mentioned earlier. So here, there is a convergence of the main frame and distributed platforms, which enables your application developers to work on both the platforms for faster application development and delivery. Yeah, just to add, what we want to say is, we have things that we want to maintain and keep investments growing there. But we are also looking to modernize there and using cloud and front-end mobile devices and with new logic, new UI, all that is getting done. And eventually, it all goes back and maintained in the main frame and keeping the whole lifecycle fully automated. And hopefully, it helps us go faster in delivering products. Because of its relevance importance, so it is still, as Ravindra earlier mentioned, I mean, 70 to 75% of the transactions that is happening in this world today, as of today, is still happening on the main frame. It is zero downtime and it is one of the most reliable platforms are still there. It is costly in terms of, but overall, if you take cost comparison, it is still cost-effective. Migrating out of it is a long process. We are not saying it's not feasible or possible, but just that people, the big banks, like FedEx, the Social Security Administration, whatever, you look at the top 500, the top 1,000 MNCs, Fortune 500 companies, most of them have main frames. They're looking to leverage what they've invested in and trying to see how can they go and take on new technologies and keep that investment and actually also move forward. They're doing both. But right now, like what Serajil was saying, 70 to 75% of all the transactions have been on the main frame. So the challenge that I have seen is in terms of the integration in the state. So now, although there's a tip for on-cloud, there's something from Air Movie is also there, which is in the middle of it. But then the challenge always is there in terms of integrating things which are posted on cloud, how to integrate back to your main frame or the SSC. So in this presentation, would you be covering? Yes, this is what our story is progressing towards. We are actually giving you a proposed solution, which actually integrates all of this and makes you go faster, both from the application delivery and application operational personnel. So these are a typical sum of the DevOps solutions, not the whole application development life cycle solutions that we have. For example, I mean, if you take the DevOps stages, developers are committing codes, then it is going through continuous integration server until it goes to production followed by operations. So at each and every stage, you have individual point products and solutions that are helping each of the stages. For example, for continuous validation and automation testing, you have, see a Lisa automation suite. For continuous monitoring, you have application performance management and then you have for continuous delivery, you have release automation solutions. But until this stage, you have these solutions working in silos for that particular stages. These are still not integrated. So this representation, this graphical representation is where we are progressing towards. So here we have different tools for different stages of application development life cycle. Just for the understanding, if you divide the whole DevOps cycle between application development and delivery, the upper part you see, it starts from ideation and it closes the feedback loop. It closes the loop at the feedback. So right from requirements to develop to build and then you do delivery and deployment and then monitor. At each stages, you have individual tools, not only in-house products, but other third party products it integrates with. Yeah, these are the third party ones. These are already CA provided solutions. So we can choose anything you want. And the interesting part of the story that we want to introduce here is all these tools and solutions can be monitored and controlled and integrated and orchestrated through a single user interface that we have a solution called application life cycle conductor. And that is what the product that we are going to demo in a couple of minutes, how it works. Yeah, I got it, I got it. So I think that gives just a quick overview given the short 20 minutes time. If you have more questions, we are more than happy to happy. More than happy to answer them. So you can talk about ALC itself. Yeah, so ALC is basically, this is what at different stages of your application development life cycle, the different tools and solutions that you use, you can monitor and basically orchestrate all these individual products and solutions through this ALC. It is kind of control center. Yeah, I got it. Yeah. So these are some of the life cycle processes that can be enabled by ALC. Okay, so this is pretty much it. I think we will move to actually the demo, quick demo. Before I start, this is a recorded video demonstration of this tool called application life cycle conductor. So there is already an application, a mobile application. So this is a hotel application. So the change or the modification here, whatever is required is, suppose there is a menu called facilities, we want to change it to comments. So this is the requirement, so this is our course. All right, we're gonna quickly do a use case where we take a mobile application which you're looking at on the screen right here that's backed by a mainframe web service and we're gonna make a few changes to it with different CA technologies helping out along the way. So we're gonna start off with the product manager who is going to use CA's newly acquired application life cycle conductor to add a new work item which he's got on the backlog to an ongoing sprint. So here we're looking at him expanding the record navigator. He goes over to the backlog, selects the manage comments work item and adds it to the sprint. Okay, so he's gonna go and save. And when he does that, you can see that it comes off the backlog automatically and becomes part of the sprint. From here, he's gonna assign the work item to a developer. So he's completed the final, the application gets updated. This will be orchestrated through this tool on. User story and send them to the test management solution and that could be used by the different teams to begin authoring test cases. So in addition, what happens is ALC binds the user stories to the test cases and the test management solution so that the progress of the tests can come back. So he's gonna update the task to completed and you can see it moves to the completed column on the task board. And then he's going to add the necessary details for. So here what we can leave this tool is again. From here, from this tool itself, you can create test management and your individual test tasks. And then the task test plan, your test task is completed in QC. And the completion status is getting updated here. So this is a kind of an agile tooling as well, close concept as well, how we implemented it. So overall lifecycle management across all stages, right? So yeah, so across each tool that we make a change and see the great test integration. So you can see that there is that we're going to, the acting as dashboards. So once again in ALC now, basically the sprints done, you can see the product manager looking at the user stories in the sprint. You can see on the right hand side, they've all been accepted. So the next part of our process is in our, in our sample workflow is to create a change order. And if you look in the bottom right corner, you can see, I don't know if you caught it, but the product manager actually pushed the sprint into a change order in Service Desk. And in fact, Service Desk has a web-based plugin that allows us to show what's going on in ALC right from within Service Desk. So the Service Desk analysts can use that button on the change order that was generated previously to launch the ALC. So this is the service tool that is integrated ALC with. So ALC, not only these tools that are pre-integrated. The related entity, in this case, the sprint. A pre-integrated, but it also has a unique connector technology that other third-party products can be integrated with this other agile tools that you use. I think with this, time is up. Any closing comments that you would like? I just leave for questions, yeah. Sure. For automated testing. So we have a release automation tools, like Lisa. Yeah. Right? Yeah. We would have unit test frameworks, which are automated, right? Right. Yeah. We, I think we talked yesterday a bit about it, like extending G test for the mainframe. So we have started on that journey, right? And now looking to see what are those unit tests that can be automated. We started doing that, that's all. So you're just saying, did we have integration? Yes, yes. We have an integration to the build systems that are on the mainframe, which we call Endeavour. And then we have SCM systems that are, that we call Harvest, that are for the distributed work that we do. So both of these, we have written plugins from this tool, which can go and talk to them. Yeah? Okay. It's not only sprints, but the whole life cycle. Life cycle, actually. Of, you are developing a new product, or developing a new application, or modifying an existing application. So the sprints are, of course, your underlying activity as you, you know, you follow your agile practices. Of course. Right. Metrics in terms of reports and other stuffs you see, the whole, I mean, all kinds of reports that you can, I mean, at least the basics, for example, the burn down and all other stuffs you want to see, the defect charts and all those stuff, it is already there. You can get metrics from defect tools that you normally would like to get, from the project management tools that you normally would like to get. And all of these come in a single pane of glass, or single pane of view, right? So you're able to actually integrate all of these diverse tools across the whole life cycle of, of, from, let's say, a mainframe developer, a distributed developer, everybody working, and then you're able to link all of them, integrate them, and get, get a quick view of what's happening across your whole organization, or across your whole development teams, so. You should be. Yes, yes, yeah. Yeah. Yeah, we have actually those plugins, maybe. I don't know, it's there. I just wanted to show that, but yeah. I will give you a whole list of, you know, the connectors available, for example, for the defect management. If you are using Jira, that can be plugged in here, all the kind of reports that you can get from Jira can be displayed here, something like that. So what we want to say, conclude, is that app development on the mobile as a primary computing device is going to be very active, right? And we still, and then the investments and the relevance of the mainframe platform is also so much relevant. So we are saying this is the mainframe, the mobile to mainframe business will keep growing, right? So that's the message we want to say, and we have provided a solution here, a potential solution, and it's basically about agility, going across all of your silos or across all of your applications, across different teams, and being able to integrate, monitor, and see progress across the whole setup. It's about agility, thank you. Thank you very much, everyone. Thank you.