Episode 6: Model-Driven Software Development Pt. 2

Skill Set

Model-Driven Software Development (MDSD) demands a unique set of skills from developers, particularly in meta-modeling and domain architecture. Marcus Blankenship explains that there are two distinct roles: those who formalize architecture and build generators, and those who use these tools to create applications 1. The latter group doesn't need to grasp the intricate details of meta-models but must understand how to operate the generators and document the programming model 1. Blankenship emphasizes the importance of starting MDSD in a familiar environment to avoid overwhelming developers with new technologies 2.

Using model-driven development is a shift from traditional development, not just because you have to know and understand all those buzzwords, also because you know not all projects think well and extensively about their architecture.

--- Marcus Blankenship

This approach ensures a smoother transition and better integration of MDSD into existing workflows.

   

Expertise

Incorporating external expertise in MDSD projects can significantly enhance their success. Priyanka Raghavan notes that having experienced practitioners can help navigate the complexities of MDSD and avoid common pitfalls 3. Marcus Blankenship supports this by highlighting the value of guidance from those who have previously implemented MDSD, which can prevent missteps and ensure effective use of tools 1.

It helps at the beginning of a project to have somebody that has done it before, giving you some advice, avoiding the basic pitfalls, and maybe also showing you how to work with the tool you want to use.

--- Marcus Blankenship

This strategic involvement of experts can streamline the adoption process and enhance project outcomes.