Name: Modernizing ACUCOBOL®: Instant Analysis & Development with GenAI
Uploaded: 2026-03-31T15:31:14.117Z
Duration: 1 h 9 min 32 s
Description: Modernizing ACUCOBOL®: Instant Analysis & Development with GenAI

Transcript for "Modernizing ACUCOBOL®: Instant Analysis & Development with GenAI": Hello. Hello, everyone. Welcome to today's session about modernizing AcuCobal instant analysis and development with GenAI. Can you hear me okay? Can you see the screen okay? Let's, sync in the chat, please. Let me know if you if everything is working. K. Thank you, Richard. Thanks, everyone. Let's wait for another minute until everyone joins, and then we can start today's webinar. We can continue our little tradition and share in the chat where are you joining from. Personally, I'm in Lithuania, Europe. Very happy to be here today and share our updates. Okay. I see South Africa. Sounds amazing. Bangkok, Huntersburg. A lot of people from South Africa. Heard great great things about Cape Town. My one of the dream destination. Germany, West Virginia, Munich, UK. Happy to see people from all over the world joining joining us today. Okay. I think we'll start with housekeeping, and we'll still have some people to join us and go over some details to make the session as comfortable for you as possible. So my name is Sarah. I'm product marketing manager here at Rocket responsible for Rocket Acquable products. And to make this session as comfortable for you as possible, there are some things I want to cover first. First of all, we will be recording today's session, and we will share it on the forum later. We will also send it through email, so make sure to check your inbox tomorrow. We would like this session to be as as interactive as possible, so please use q and a tab. It's right next to the chat, to ask, questions to our speakers. Today, we're not gonna have live q and a, and we're gonna answer all the questions on the forum in upcoming days. So I will share the link to the forum a little bit later, but this is something we are trying to make the content a little bit longer, and then we can focus on answering the questions so you have them in written form, and you can reuse them, share them with the team, and get the most out of the answers. Last but not least, there's gonna be a short post event survey at the end. So please share your feedback with us. This is how you help us to make the sessions better for you, more more valuable for you. So it's gonna be very short one, maybe five, six questions. Please share your feedback. This is how you help us with the webinars. And then about the forum. So we have a dedicated space for everything regarding AcuCobal. I invite you to join our Rocket AcuCobal community. There you can stay in the know, be informed about the product updates and community updates every week. You can learn about AcuCobal tricks and tips and in-depth guides on how to maximize the use of Rocket AcuCobal products. You can also connect to fellow Acucobal enthusiasts and share your experiences. And, of course, it's gonna be connected to these today's sessions. We're gonna share the presentation that you see today on the forum, and we're gonna answer all the questions from you on the forum in upcoming weeks. At the end of, today webinar, we're gonna have a short quiz based on the content of today's session, and we're gonna announce quiz winners on the forum as well. So overall, it's a place for you to go for any questions or any kind of advice for AcuCobal and AcuCobal modernization projects. So I encourage you to join. You can see QR code on the screen, and you can see the link in the chat. That's it for housekeeping. If you have any questions, please feel free to ask in a chat or in the q and a section. And I would like to continue with Rocket Software. So, actually, next month, we are turning thirty six years. Thirty six years of software modernization all over the globe with leading solutions for our customers. We have more than 3,000 Rocket shares, and we are very proud that more than two thousands of them are software engineers. So this is something we are extremely proud of to provide tools dedicated and made by engineers themselves. We have 18 global offices, 700 plus partners, and more than 12,000 customers. This is how we help to modernize software all over the world. Our goal is to provide our customers with the tools so they can modernize without disruption. We understand that mission critical systems that are covered by our customers are cannot face any disruption at all, and this is where we help with our solutions and our products. At the same time, we understand that every modernization journey is unique, and we aim to meet our customers wherever they are in their path to modernization. When we talk about COBOL and AccuCOBOL, we had more than 5,000 successful modernization projects across countries and across industries. So if you are in the middle or thinking about modernization, let's talk, and we can share our experience and our tools with you. What we have for you today. As you can see, we have a packed agenda for today. We will be joined by Dominique Sacre and Gustavo Fajana, and we will be talking about first chance modernization and how to analyze your AcuCobalt applications. We're gonna talk about Visual Studio code extension updates and capabilities. And at the end, we will see AcuCobalt XGen AI demo and Rocket AcuCobalt. To make the session engaging, we will finish it with a quiz based on the today's session content. So please, feel free to, participate and win some rocket software prizes. On that note, I want to pass to Dominique Sacre, our product management director, and he will walk you through the first challenge of modernization and how we address that with Rocket Global products. Dominique? Thanks a lot, Sala. Good morning, good afternoon, good evening, everyone. Welcome to this webinar. Before we talk about tools and our technology, it's important to pause on the first real challenge of modernization. That challenge is not choosing a technology or moving to the cloud. It's understanding the application you are already depending on. When organization think about modernization, the first big question is often very simple. Do we rewrite everything or do we build on what we already have? Many core applications have been running the business reliably for years, some time, decades. They contain valuable business logic that is or are stable, proven, deeply embedded in daily operation. The goal of modernization should not be to throw that away. It should be to extend, improve and prepare it for what next. The number make this very clear. On the right side, we see that more than 50 of rewrite projects end up with major cost overruns or long delays. Rewrites are complex, expensive and often riskier than expected. In contrast, 71% of modernization initiatives succeed when organizations modernize incrementally without major disruption. The report shown on the left highlights something important. Projects that focus on modernization flow, interfaces rather than replacing the entire application are far more successful. That is exactly the approach enabled by Rocket Accuables solution. You can modernize your application while protecting existing investments, integrating with modern tools, improving user experience, and unlocking new value, all without the cost and risk of a full rewrite. When organization talks about modernization, the first challenge they run into is not rewriting code. It's understanding what they already have. Many core system represent millions of line of code build out of decades. Documentation is often a complete, outdated and critical dependency are hidden. That complexity becomes the biggest barrier to change. The visualization on the right show that it looks like, in reality, what appear to be simple business domains. Cards, consumer banking, core banking, are actually deeply interconnected. Without clear visibility, even small change, these cannot reduce risk, delay or unexpected failures. This lack of visibility make modernization expensive and unpredictable. Teams hesitate to act because they don't fully trust what will be impacted. Changes take longer than expected, and technical debt continue to grow instead of shrinking. That is why the first step in any successful modernization is application intelligence. This tool makes complex system understandable. They map structure, visualize dependency, and give teams confidence to modernize safety and incrementally. You don't modernize by guessing. You modernize once you can see, you can understand and trust your applications. To modernize safely, organization need more than good intentions. They need visibility. For many teams, global applications are mission critical, but they are also complex, deeply interconnected and difficult to fully understand at scale. Without clear insight, modernization decision becomes slow and risky. The visual on the left shows that real code visibility looks like in practice. Instead of reading thousands of lines of code, teams can see application structure, program flow, data usage and dependencies, all synchronized across multiple views. This level of insight change how modernization happens. With Rocket Global Analyzer, teams can get the full picture faster so they can understand what they are working on with, access risk upfront by clearly seeing dependency and impacts and move forward with confidence rather than guessing. Importantly, this is not just for Cobol Expert. The tool empowers every engineer, including those new to the code base, to navigate, understand and work safety with a global application that directly helps reduce bottleneck and knowledge. You can't modernize what you can see. Full visibility turns modernization from a risky exercise into a controlled, predictable process, and that is what allows organizations to move faster without disrupting what already works. Now I will pass over to Gustavo, who is going to show you how Kabbal Analyzer works. Gustavo? Hello, everyone. I'm Gustavo Foyana, and I'm going to do a demo about Cover Analyzer. What is Cover Analyzer? Cover Analyzer is a tool that helps developer analyst better understand the impact of application changes and make better decisions. The tool, it has, like, two different motives. One of them is all the relationships between objects, and the second part is all the relationships inside objects. So for example, when we come into the tool, first of all, what do we see? The number of files that we have, for example, five hundred and and eighteen. Copybook files that we have, a little bit more than 4,000. We see, for example, the diplomatic complexity. You can see this is actually quite funny, but the application is divided in more or less five parts, more or less equal, being from the most simple one to the most difficult one. Now on the left side, we have a repository. In here, we have all elements. In this case, I just have a standard COBOL, a COBOL GT application. If I choose any element if I choose, I can open the file and look at the code. I can as well look at all the relationships that he has, all the elements that call him, all the calls he makes, the copy books he's using. If he's accessing data with tables or files. This is an application that use only files, so fairly simple. If it has screens, all these kind of of information. If I, for example, want to see this line of code where he's calling another program, vSUTIVE, I can just double click, and you see it opens the line of the code where that's been done so I know what's happening and where it is. It may seem silly, but the tool works the following way. You have a workspace. In this workspace, you have all the elements that you can work with, and then we have projects. In this case, I only have one project with all the elements. So any analysis I'm going to do is going to be done to all the programs. But you can, if you want to, choose, for example, an element. I don't know. Let's choose one of them. Maybe, for example, ParFD. In here, if I want, I can create a new project. I'm going to call it par or file par because and this is going to contain all the programs that, you see 278 objects on the project. So now I have a new project with 278 programs, and these are all the programs that are using the PowerFD file. It does not mean that all of them are going to to access the data. Most likely, I would imagine, yes. If I wanted to have all the programs that access the data, I would come in here, add it, and then do a crude receipt or so there's different ways of accessing the same data. But in this case, I'm going to modify bar file, and then I create a project. And from here, I can keep going on. And the tool allow us a very, very simple way to create project that are going to contain very important information. I come back to my main project, so everything I do works for the 518 programs. We have a whole lot of reports that come by default. You can create your own ones, but the ones that come here, for example, inventory report, the number of programs we have, number of lines, number of files. In this case, you can see that most of the code is on the on the copy books. So in total, 1,000,000 and a half lines of code. So it's not a huge application, but it's not a very small one. We have tried to do a demo that uses more than just five programs or 10 programs so you see the tool working. We have the crude report. So, not in the background. I just want to execute it. It's quite fast. As you can see, here, for example, I have all the information of all the programs and all the files there. You see, if there were tables with embedded SQL code, we would have them here too. And then I'm just going to export this data into Excel because it's easier to access. It's going to say that I have to replace it because I have already created it in the past. I want to see it. Yes. This is a way sometimes it's better to actually export information, maybe easier to use. It all depends if you want to share it with other people. In this case, something fairly fairly silly is if I come here, I don't know, I pick up hub which one I'm going to pick up par, for example, that we have seen. And here I have all the programs that I use in par and how they are using it. Okay? So in certain cases, I'm creating it, reading it, updating it. It's a normal. I save the report. I leave it there. I put always a filter because it's easier to work with filters for information. Then we have reference report. This report, it has, like, four reports inside, unreferred all the elements that have no links towards them. That means copy books that are never used or programs that are never called, unresolved. It's just a way around. I have a copy total, and the copybook total is not in my workspace, so it's unresolved. Or I'm calling a program, and I cannot find the definition of the program. And then a cross reference report, this one contains all the reference across the program. So for every program, all the files they are using, all the copy books they are using, all the calls they are making, it's usually a very interesting file. I used to export it as well on Excel sometimes to work with it, just to have all the relationships, it has quite a lot of the info that I have already show you. Just one part. You don't need to export it, but sometimes people want to support you so they can show it, so they can use Excel to to access it. Fairly simple. Now complexity is just calimetry metric metrics. We have quite a lot of them. Not going here. For example, I have already chosen I I have in columns, you see, I have a lot of them. I have just chosen three of them just to see the number of lines of code, the complexity, so diplomatic complexity, and then the number of data statements. You need to be careful with the statements because it can be, for example, undefined variables. It has very precise definitions from the documentation, and you need to check to know exactly what you're looking for. I would say that the elements that we have there, they they serve to guide us. But in reality, what we would do is go to interactive analysis. This tool goes inside a couple program, and it creates yeah. Or it give us a whole lot of information. For example, here, I'm on a program visu indica. I don't like it. I'm going to go to a program. I know I have already worked with AIF Planum. This program, for example, if I click in procedure division, it's going to create a graph for me. This graph, it has a certain depth. It cannot go further because I have a parameter that allows me to choose how much depth I want to have. I could put 10, and then I would get a bigger graphic. It all depends. And the colors that you see on the graph, they indicate things. Red one is what we call a form a a fall through, so it keeps rolling. When it's blue, it's a call. So we are calling external elements. When we have brown, that means it's a perform. When it's green, it means it's a go to. If I click on an element here, it's a go to from cat plans to I haven't checked where it goes. So I have it here. Do you see? I have it here to go to if I click on a paragraph, it just goes to the paragraph. If I pick up a line, it goes to the line where the perform is being done. So it allows me to navigate and to better understand the program fairly easily. If I open the view, I can as well have a flowchart, and this one is a big one. So it's a huge paragraph. Here, we have it comes. It does an open input. There is a few lines more of code. That's what we have a plus. I can click and then get the information that's in there. And then he's going to do here, he's going to look at link link type In this case, you can see here is an evaluate if it was an if. We will have only two branches like here. So if s w plan equals one, it goes this way. On the else branch, it goes this other way. Whenever we have blue, what it means, upper forms, is going away from the program. And if I click somewhere in here, I don't know, I want to see what happens here. So I click, and you see it's going to the line of code that that I have chosen. And if I click on the perform, it's going to show me the perform. I can do a lot more things with the tool in reality. In here, for example, I can go to the call paragraph and see how it is defined and how it works, the call paragraph. But I can as well perform call statements. So I have the list of all the perform or call statements that we have for that paragraph. And if I click in one of them or to the other, it's going to the different places on the code and show me what it is doing. I'm not going to go through a lot of other things, but we can do impact analysis of our variable and follow it through. We can slice code. So and that's going to be important. I'm going to show you the next best thing that we have, and it's this code search. On the code search, what we have is a whole lot of groups. You can create your own. They are fairly simple to do. It's we bring, like, 200 and something queries that are done by default and that you can check, copy, or modify as you need to. In here, in particular, one of the most used ones are these two ones, that code. And why I say it's important? Remember, I say we can slice code, so we can cut code out, and we can, if we are careful, slice the ZIP code of the application. Now in here, I can execute all my program on all the objects or on something else. Those are queries that I have already executed and where I have results, and then I can execute a query on the results of a query. It's a way of sometimes when things are a little bit too difficult, you can do you can do that. In this case, for example, I want to check if in my program, I have paragraphs that are unreachable and that are not in copy books. So I'm going to check. He's going to say he has none. If I wanted to do a bigger check, now my 500 programs, he's going to check unreachable paragraphs, in copy books, and we are going to see if he's going to find anything. You see that he's quite fast. So it has it has found 98 paragraphs in five seconds, and now he's going to create here an element. You have seen that it has gone to the program, so I don't have the graph anymore. If I want the graph, I need to choose an element that's going to generate the graph, and then he's going to do it automatically. So he's going to take a little bit of time. You see these are not a small program. So I'm doing a demo with a real real application. And here you can see all the links of the of the different elements. You can very easily make the graph bigger. Click on the different elements to move. It will go inside a copy books. If it needs to, it it it does everything that you can imagine. And if I double click here on an element, it's going to show me the paragraph. This paragraph is on the main source of the program. You see? And we never it it is never called. If I do what I did before, you see I don't have to perform call statement. But if I go to this one, okay, I do have it because there is okay. Now it has gone directly there. What it means is that there is only one call, this one. I can always go back to whatever I want. I can pick up variables and go on okay. I want to see the declaration, so I go to the declaration. I want to go back, or I want to see all the places where this variable is being used on the program. I'm not going to spend a lot of time around this. Okay? You can see that it is a very powerful tool. And with all of these, I'm going to stop because this is a very long demo. Thanks a lot, Gustavo. One of the biggest additions in version 11 was the ROCCAT AccuCable GT extension for Visual Studio Code. This brings Equitable development directly into modern industry standard IDE without sourcing teams to change all their application work. First, this extension empowers any engineer, not just global specialists, to work confidently with a global code using an interface they already know, that reduce onboarding time, remove knowledge silos, and make teams more flexible. Second, it helps teams to move faster. Modern editing, navigation, and development work flow allow you to accelerate changes, reduce friction and keep your executable application competitive without rewriting them. Version 11 also improves how you work hard the user interface. With the new screen designer, team can more easily create and modernize graphical interface, making user interface evolution part of the normal development flow instead of a separate project. You can quickly install and set up the extension on Windows, and we are working on Linux support in the future so your executable development team can align with modern development environments. Version 11 brings AccuCable development to the modern tooling ecosystem, making it more accessible, more productive, and better aligned with how software teams work today. You keep the strength of AccuCable while gaining the speed and flexibility of a modern development tool. We continue to announce it regularly on the marketplace, and you will see some nice feature we are working on for version 11.1. Now Gustavo will show you some Visual Studio Code demo. Gustavo. Hello, everyone. I'm Gustavo Fujana, and I'm doing a demo on Visual Studio Code Rocket, a Google GT GT plug in extension. If you remember, we did a presentation of it quite a while ago. The product has been out for nine months. We update it regularly. The last update was two weeks ago. In the last update, if you check-in the documentation, you can see that we added the project settings, super runtime settings. We are adding new features slowly version by version. So you can be sure that we will be adding all the features that or most of the features that we have in Acubench and some new ones as well. You will see that on another demo afterwards. Right now, in here, just to remind everyone, we can read, update, and work with projects that came from Acubench. So we have the screen designer as we have it in Acubench with the same elements, the properties. We can modify the information. We can add new elements. We can execute programs. We can debug. You can see that we have colorization on the code. You can get help. We have to walk in the street sex section. It's everything pretty standard. It's a very, very good step forward. If you like Visual Studio Code, this is the lightest thing that we can use to work with and Acubench project. We can execute programs. So first, it's going to build, then we have the application that is executing. I can check that everything is okay. For example, just to check the screen that we have seen, see if the configuration I hope you remember that these are some features that we have been adding so you can programmatically modify the grid, but we are not talking about CUI today. In in any case, we can execute applications. We can debug. We can code. You can choose the WYSIWYG screen designer. There are going to be some new things that we can do or well, nothing new things we can do, but mostly things that you can do inside Visual Studio Code that are going to to add more power to this development environment. Just as a reminder, if I pick up I don't know. If I pick up no source code, two PSF sorry. Not PSF, but couple programs, I can compare selected, and the Visual Studio Code is going to show me the difference between the two programs. It could be books that are missing one side or the other. The information such are different. In this case, I have chosen files that are pretty similar. All this is part of Visual Studio Code, so nothing to do with that, which which you take advantage. You can connect yourself with source control like Git or SVN, and you get all the advantages. Then in the next demo, I'm going to show a few things that you can do in Visual Studio Code that are mostly related with GenAI. I hope you have enjoyed this demo, and see you in a little bit. Thanks, Dominique. Thanks, Gustavo, for all the insightful information and for the demos. Before we proceed with the demo of AcuCobalt development with GenAI, something that Gustavo is preparing for us, I would like to dedicate some time to discuss big topic for the last few weeks. We all have seen that COBOL is in the spotlight again. Few weeks ago, GenAI service provider called Entropic shared their blog post with the title how AI help breaks the cause barrier to COBOL modernization. And as a software modernization pioneer, Rocket Software is, and as someone as a leader in Rocket COBOL and RocketAcu COBOL modernization projects, we would like to provide our perspective on this topic and share our thoughts where we see LLMs and GenAI tools helping enterprises today and where we see that they bring risks at the moment. At Rocket Software, we embrace AI in our solutions, in our processes, but at the same time, we understand its limitation. And we under we think it's important when we work and when we talk about mission critical systems that we understand both benefits and risks that JetAI brings today. So let's talk about where LLMs are helping enterprises today. Something we see in our customer experience and also with talking with analysts and partners. Something that LM's helped today is application understanding, making code maps, data flows, documentation generation. The second thing is onboarding and skill simplification. For example, Copilot style q and a and code explanation is something that help every developer regardless of their COBL or AcuCobal experience to navigate the code, understand code bases, and see applications with all the integrations and data flows, for example. Something that Dominique mentioned before that the first challenge of modernization is to understand the system that you're working with, and we see how JetAI incrementally help with that for developers. The next thing is quality and safety. Unit testing, impact analysis, code hygiene, making sure that applications are operating as supposed to. And last but not least is developer Velocity, assisted refactoring, code understanding, and coding support, something we embrace with our own tools for COBOL and active COBOL modernization as well. But at the same time, there are some areas where LLMs bring risk today, and we think it's important to distinguish syntax translation that Entropic and other AI code converters tools are focusing on and big large scale modernization projects that we are talking about today. So where LLMs are fall falling short for full conversion? When we talk about modernization projects, we're talking about modernizing the whole estate that application is operating in. We're talking about million sites of code, multiple languages, and utilities. We talk about tightly coupled data. And so this is where COBOL is only friction and all only part of the whole system. And when we talk about modernization projects, we're talking about modernizing and refining the whole estate that we are working with. The second thing is process and integration dependencies. So COBOL applications sit into end to end processes with dozens of upstream and downstream touch points, like APIs, batch file ex exchanges, schedulers, additional programs like ERP and CRM systems. And code conversion, something that current tools are doubling down on with their press releases and blog posts and stories, doesn't remap data contract, SLAs, exceptions, and human processes. All of that must be rediscovered, redesigned, and recertified. And this is something we want you to know and be aware of when you're thinking about bringing LMs and GenAI tools to your modernization projects. There's definitely there are areas where it can help you streamline and accelerate your modernization, but at the same time, it doesn't replace modernization projects because COBOL is only part of this whole picture. And another thing we would like to discuss today is actually skill shortage because, we see from talking with our customers and analyzing the market that skill shortage is the real challenge. Retiring specialists, limited documentation, hiring challenges, all of that brings up conversation whether companies should rewrite their applications or modernize. And with this GenAI trend that we see on the market with GenAI tools and also GenAI features in tools, we see how potentially development is gonna change for next years. So as Dominic mentioned, 50% of our writing projects are going over budget or overestimated timeline, and we expect skill shortage be a less of a challenge in the next few years with GenAI development because we can see how GenAI helps onboard, cross train, and also simplify, working with large, cold cobble and active cobble systems. So to sum up, we can see how skill shortage that might be leading rewriting conversations in our customer companies, might be not a big of a problem within next few years with GenAI development. And at the same time, we kinda find it ironic in some way that COBOL was ahead of its time because it's English like syntax was introduced sixty seven years ago, and now we see how development is focused on providing clear prompts to JetAI tools and how results and, basically, the quality of work depends on clear prompts written in natural language. So we see this trend in skill shortage conversation and wanted to share with you our observation here. From our perspective, we are enriching LLMs with, application wide context, product documentation, custom prompts for specifically COBOL and AccuCOBOL, all of that to provide you with hallucination free results and making sure that you can actually trust output that you receive from Rocket Cobble tools and GenAI features that we have. On that note, I would like to hand it to Gustavo so he can show you how you can use GenAI tools with archicable applications. Gustavo? Hello, everyone. I'm Gusto Ofoyana, and now we are on a demo on GenAI. I'm not going to show a lot of things. I'm just going to show you, like, three different themes, things that you can do right now with GenAI. First of all, I am connected to two different things. I'm connected to Copilot. You can see it here. Copilot for usage with cloud. Okay? And then I'm connected to Gemini for code assist as well. Then I'm going as well to talk a little bit about new integrations that we are adding ourselves. But in here, for example, remember that you can just pick up any program. This is an Aguco GT program. Okay? You can ask Claude to explain it, and he's going to pick up the program. He's going to look at it. He's going to say what it does. Hopefully, he's going to explain. Uh-huh. Program focus on displaying plans and the mantleatures. It is this program, it pickups a file, a graphic file, and it's going to show it in the in the in the screen. So it is really what he's doing. Feature plan nomenclature in French. So he understands what he's what it's doing. Now, obviously, if I do exactly the same thing with Gemini, say in the Gemini codexist, add file to Gemini context, then I come to Gemini. And I say, can you explain what's the program on the context test? Hopefully, I have given the right query. He's investigating the EcuCobalt program. So he knows we are with EcuCobalt. He's looking at the logic. Now you need to be a little bit careful with all of this. It can do a lot of work. But remember, this is AI, so it's based on statistics. Resource can be particular. Okay. It's a utility designed to search for and display technical documents, specifically plants, blueprints, or nomenclatures, builds, or materials. So it's very good. It has understood exactly what it does. Then he's going to give me a detail functionality of how it works. The search logic, password retrieval, recursive search, file name matching, output action, server handling, and now code quality observations. The programs you see see list directory to handle dynamic directory structures. So it's giving me quite quite a lot of information about this. I can ask, for example well, is giving me prompts to try. But in certain cases and this is one of the things you can ask the same thing, like, three times and get different information. One of the times I was doing the test for this demo, it was giving me tips of how to improve the code. So pick up a piece of code and actually gave me what consider a better version of the code. Obviously, you need to check that the changes he's doing is not modifying the way the program works. But as you can see, we can do quite a few things with with this. Okay. You can if you want to come in here as well and choose bit of code and then say I'm not completely sure. Add to selection chat and then explain. So it has picked up this past construction with conditional file naming, and it's explaining everything that is using here. A gotcha here. It says that the limited by spaces assumes that your true path is shorter than the fill width, and is pated with the spaces. If the path contains embedded spaces or is exactly filled with long, these will truncate unexpectedly. So as you can see, can be it can be interesting. These are just public elements that you can use. You need I mean, they are interesting. They help. You can as well do something else. If you want to, you can open as well call analyzer web. So so now to watch call analyzer, we go to show all commands. We go to browser. We are entering the URL, a little bit of resizing. Okay. Web user. Password. It's coming. Okay. And now we have enter call analyzer web interface. We can see on the left now. Repository, the same interface we had before. Yeah. Okay. Here it is, Koval. What can we do in here? We can execute queries. If you remember, the only ones I have shown so far is the dev code ones, which we can execute it and select programs or on the whole workspace if we decide to. In this case, for example, we say recent programs not included in reachable paragraphs. I'm going to come here. Said I want to search. He's coming, and he's doing for the whole environment. So he's giving me here all the unreachable paragraphs, not in copy books. Okay? This is if I want, I can click on any one of the programs and see the line of code is telling me that in this program, this paragraph cannot be reached. Okay? We have an AI in here. You can ask questions. Here, you have above. Just a simple one, but you can ask more questions, be a little bit more precise. You have to understand that the queries are a little bit restricted to to what we can do with this. It will be added. We we will be modifying that new queries when it's through the new releases of the tool. Not going to show everything that we can do, but mostly I hope you are getting an idea. You can access the queries. You can access the the information from who's calling who to whom. You can create new queries that will appear here. You have the possibility to talk with the AI. I am connected to OpenAI, so you need to have a connection to an LLM to be able to use it. And then at the moment, I believe that the queries have to be in English. That's something that it may change in the future. And now there is one other thing that is very interesting that we are adding in one of the new versions that's coming later this year, and that is this. The sample demo that you are seeing here has been written by development. They have added a chat. We are in the visual studio code plug in. We have a chat where you are going to be able to say that you want to execute certain queries that are going to modify the scene generator, the CSS that she generated for Accu2Web on the application. So in here, you see they change the color on the primary elements. They change the labels, then they apply the new theme directly on the WYSIWYG. So we see how it would look when we execute it in Accu2Web. This is something that is going to have quite a lot of usage. Now, for example, they want all the borders round for the frame and the buttons, so it applies them, then it creates another prompt and giving them more information. So we're thinking, working on it. So this is, for example, one of the new features where we are picking up AI, adding the theme generator on top of that, and trying to make Visual Studio Code a lot more helpful for our customers so they can see how their screens would look when they apply the CSS on a web, when we have when we work with a more modern UI, this is going to be very interesting for our customers. In here, for example, we have a new prompt to change the checkboxes. So if if want them a little bit round, a purple check-in the center is giving is spacing the elements a little bit more. As as you can see, this is this is this is really interesting. You can see with the theme on and with the theme off. One of the new great features that is coming in the next version of Visual Studio Code, not just next week, but in in a few months whenever we release, I believe, it's going to be 11 dot one. That's going to have this feature, but it will be announced by product management in any case. I hope you have enjoyed the demo. Thanks a lot, Gustavo. Before we go into the detail about the applicable road map, it's important to note that what you will see reflects our current plans and strategic direction. As always, the roadmap should be viewed as a guidance, not a commitment to final future implementation. As you may be aware, we have released Extend version 11 in July 2025. One of the major theme of this release is developer productivity, especially through tighter integration with Visual Studio Code, enabling faster development cycles and a more modern IDE experience. We also introduced simplified cloud deployment with AccutuWeb, making it easier to deploy and manage applications in modern environments. On the application side, we have enhanced user interface capabilities by adding new graphical features, helping our customers to modernize the look and feel of their existing application without rewriting them. Finally, we continue expanding platform support, ensuring applicable runs consistently across more environments. In parallel, we are making continuous investments in the Akiko BOL extension for Visual Studio Code. Other than big disruptive releases, the extension followed an incremental and predictable cadence focused on maintenance and enhancements. We started 2026 with Xtend 11 Patch Update one, which is a maintenance release following the Extend 11 major version. The focus here is on fixing issue identified after the initial adoption of version 11, improving robustness and ensuring a smooth experience for customers who move to this version. Mid year Extend 11 patch update to continue this maintenance approach. In parallel, we continue to actively maintain extend 10.5.1, with patch update four in June and patch update five in December. Customers who remain on this 10.5 line benefit from ongoing maintenance and support. The bottom timeline shows our plan for the extension for Visual Studio Code during 2026. We follow a frequent incremental release model, starting with version 1.3 in January, 1.4 in February, and we will release version 1.5.0 in April, followed by additional releases later in the year. This slide looks ahead to 2027 and outlines our planned direction for Equitable Extend. It's important to note that this road map show intent and direction, not final delivery commitments, especially for the more innovative capability shown here. We will start 2027 with a RocketXtend 11 patch update three, which is planned as a maintenance release. As with previous maintenance updates, the focus is on stability, defect fixes and quality improvement, ensuring a solid and reliable base for customer before introducing new capability later in the year. The key milestone on this slide is Extend 11.1.0, scheduled for the end of the 2027. This release is intended to represent a significant step forward in developer experience to lingual alignment and modernization. An important point here is that Extern 11.1 is planned to align with version two point zero of the AcuCobalt extension for Visual Studio Code. This alignment allows us to introduce deeper integration between the runtime and the tooling and to take advantage of a new major extension baseline designed for future capabilities. The feature list shown here represents area of investments, but I want to be very clear. Some of those capabilities are still to be defined, and the final scope may evolve based on customer feedback, technical validation and prioritization. What is stable today is the direction, improving usability, deployment tooling and operational efficiency. You will also notice reference to JNI related capabilities such as code explanation and program summaries. The previews and demo we previously showed in this area were exploratory and work in progress. Those demos were intended to illustrate potential use cases, not final product behavior, and the look and user experience will not be the same as you may have seen in early demonstration. This is an area where we are deliberately moving carefully to ensure the right balance between value, usability and trust. Other planned themes around this release include tooling unification, expanded Versus Code editor features, improved IQ2Web and IQ Connect integration, greater scalability for concurrent connection and broader platform support, such as ARM. Again, the key message here is direction and intent rather than finalize specification. In parallel, we continue to maintain 10.5 line with 10.5.1 patch of date six scheduled for October 2027. Customers who are not ready to move to the newer version still benefit from ongoing maintenance and support. The bottom line the bottom timeline, sorry, reflects on the ongoing evolution of the Visual Studio Code extension beyond version two point zero. While specific version number and feature are still to be finalized, the strategy remains consistent. Frequent incremental improvement focused on maintenance and enhancement closely aligned with the run time road map. The overall message for 2027 is balance and transparency. We continue to invest in stability and long term support while carefully evolving the platform to support more modern development workflows. What you see here is our strategic direction, and we expect it to continue evolving in close collaboration with you, our customers. Thanks a lot. Now I will pass over to Sava. Sava? Hi, everyone. Thank you so much, Gustavo, for showing us the capabilities of integration with GenAI, and thank you, Dominique, for covering the road map. I know that we are going slightly over time, but I thought maybe we can do quiz really, really quick. We have we're gonna have five questions. We're gonna turn on the chat back so you can answer the questions. The questions will be based on the content you've heard today, and we're gonna calculate all the answers and identify the winners in upcoming days and share them on the forum. So in the chat, you will be able to find the forum link, and we will start, we will start the quiz shortly. At the same time, we are receiving the questions from you for road map and for GenAI capabilities. So this is something we will address on the forum as well in upcoming days, so please stay tuned and check the forum. If you open Rocket AcuCobal community, you can actually press on the subscribe button. This way, you will get notification when there are updates, and this is will help you to get to stay in the loop on everything that happens with AcuCobal. Just a second. I don't see the chat yet. Okay. There there is an update. Unfortunately, there's something with the chat happening. So let's use q and a, I think. Yeah. Let's let's use q and a to answer the questions, and then we can identify the winners this way. And it will help us also to bring to have some kinda intrigue because, you know, usually, we have all the right answers from the get go. So this way, we can see who is answering what. Final thing before we start the quiz. There's gonna be post event survey at the end. Please share your feedback, and this is how you help us to increase the quality of these sessions and make sure that it's brings you value and brings value to your businesses as well. So the first question is, how many engineers are working at Rocket Software? Is it 200? Is it, 21 hundreds? Is it 710, or is it 100, 1,350? I see some answers going through q and a. Thank you so much. We're gonna have thirty seconds per question to keep it to keep it fast because I can imagine there are other meetings waiting for you. So we will keep it short. Let's wait for five more seconds, and then we can continue to the question number two. And the correct answer is 2,100 plus engineers are working at Rocket Software and helping building software modernization products. The next question is, what is the first challenge of modernization? Is is the challenge to find time for regular meetings? Is it to name the project? Is it to get visibility into large and complex systems, or is it edit the code that we are working with? No. I can see the answers. Some of you are really, really quick. Even quicker than I'm reading the answers. Let's wait for ten more seconds, and then we can proceed to the question number three. Also, we're gonna be sharing the recording tomorrow, and you can find the link to the forum in the email as well. So this is where you will find quiz winners and then answer the questions and the presentation from today. And the correct answer is number three, get visibility into large and complex systems. The question number three is what can you do with Rocket Cobo Analyzer? Can you visualize a cubo application, slice a cubo code, identify duplicated, and that cubo code, or all the above? Something that Gustavo showed us today, how can we work with application intelligence tool in order to understand and get visibility into AcuCobalt applications of any size and any complexity. Let's wait for five more seconds. I see a lot of correct answers in the chat I mean, q and a, and the correct answer is all the above. We're also gonna share the demo on the forum so you can rewatch it or share it with your team. The number question number four is where does Jenny I not drive enterprise level value today? Is it onboarding and skills amplification? Is it quality and safety, like unit testing, for example? Is it full modernization projects or application understanding? Where is the challenge with GenAI currently? I see some of the answers. Let's wait for ten more seconds, and then it will be time for the final question of the evening or of the morning depending on your location. So the correct answer is, number three, full modernization projects. And the last question for today is what is the current version of RocketAcocobal Extend? Is it 11? Is it 11, Dot0Dot1? Is it 11Dot1, or is 10Dot5Dot1? What is the current version that you can use with RocketAccu Global Extend solutions? Let's wait for few more seconds. And please fill in the survey. That's gonna pop up very, very soon, and we will share the quiz winners, in a few days. And the correct answer is Number 211Dot0Dot1. This is the answer for today. That's pretty much it. Thanks everyone for joining us today. I hope it was insightful for you. We will address all the questions from the q and a section on the forum. We will share the recording tomorrow, and we will stay in touch for the further, for the future sessions in the upcoming months this year. Thanks, everyone. I hope you enjoyed it. Please share your feedback, and see you very, very soon. Thanks.