Home | Technology | Model-based development | Model Driven Engineering: the next step in software development
Model Driven Engineering: the next step in software development
The biggest challenge in developing software for systems is communication and coordination between all disciplines and everyone involved in the process.Model Driven Engineering(MDE) is a relatively new methodology that allows for complete synergy between all parties. A next step in software development that is not entirely new, but for which the time now seems ripe. Operations Manager atICT Group, Ronald Wiericx and Senior Software Designer, Olaf Donk are pioneers with MDE.
"The original approach to developing systems is to create a design in which the customers specify the requirements," Olaf explains. "The designer creates a design of the requirements and the programmer develops the code. But each discipline speaks a different language and often the result is not what other stakeholders are focused on. In this process, all parties involved make a lot of assumptions that may ultimately prove to be incorrect."
"This so-calledwaterfall method is a very linear way of developing software and takes a lot of time," Olaf continues. "Right now, many companies are already working in a much more agile way. There are more delivery and testing moments. But it is still a very traditional way of developing systems".
Working on a central model
The market seems to be ready to apply Model Driven Engineering ...
Different skills required for Model Driven Engineering
Invest in refining the central model
Thinking about the essentials during a team effort
Olaf regularly puts this new way of working into practice. For example, he recently worked on an MDE project for a large company in the Brainport Eindhoven region that aimed to make some of the machine the company produces more sustainable. "At the moment I spend 1.5 days of my time enthusing others and spend about two days developing models, the rest of my time is spent on research. What I like about the way the MDE approach has changed my role is that you work more intensely with other roles. It has really become a team effort, interaction is key and you work closely together. On top of that, I like puzzles. When you use MDE, you really think about the essentials."
"A long time ago, I learned to develop in the traditional way," he says. "But somewhere along the way I realized that it's just not efficient and it's time for a change. You have to align the process and everyone involved. And that's what you do with MDE."
A real transition in the market is yet to come
"In my role as operations manager, I am less involved in technology than Olaf," continues Ronald. "ICT is building its network with companies that are also interested in the MDE methodology. You have to work together. Software engineers with the right profile are scarce and need to be trained. At ICT Groep, I hire developers who work with MDE and make sure they are properly trained. Something that is not easy for MDE because there are currently only a few parties that are properly trained. MDE education is still in its infancy".
"The ICT Group is investing a lot in Model Driven Engineering," says Ronald, "but it is still nascent; the real transition in the market is yet to come. That's why you see companies starting with small pilot projects alongside their regular processes and gradually expanding the approach. Nevertheless, I believe that MDE will be the future methodology for software development."