What software development model do you know, wich have you really used? I work in Software Development…?

I want to compare the model we use, with other models, in order to improve my team productivity.

We commonly use "model driven development" as our method of choice. The basic premise is to devise a model for what the software will do and how you plan for it to perform that task. The idea is to stay away from implementation and specific algorithms in favor of modeling the processes for how the software will function (in our case with UML). After a UML is formed, many MANY IDEs are capable of generating code stubs and even full code to create a working model of the software.

Imagine you are building a house: in a typical programming environment, you’d have a few people to assemble the simple wooden structure together, a few to wire it with electricity, and few to add the visual elements. Without a preexisting image of what the house should look like, you have the electrical depending on how the assembly team located their outlet holes, and you have the visual team depending on the electrical team for where to install the lighting.

With model driven development, a smaller version of the house would have been made out of lighter materials, then those developers would know immediately where to begin with their work instead of depending on each implementation.

One Response to “What software development model do you know, wich have you really used? I work in Software Development…?”

  • Russ the Red Husky says:

    We commonly use "model driven development" as our method of choice. The basic premise is to devise a model for what the software will do and how you plan for it to perform that task. The idea is to stay away from implementation and specific algorithms in favor of modeling the processes for how the software will function (in our case with UML). After a UML is formed, many MANY IDEs are capable of generating code stubs and even full code to create a working model of the software.

    Imagine you are building a house: in a typical programming environment, you’d have a few people to assemble the simple wooden structure together, a few to wire it with electricity, and few to add the visual elements. Without a preexisting image of what the house should look like, you have the electrical depending on how the assembly team located their outlet holes, and you have the visual team depending on the electrical team for where to install the lighting.

    With model driven development, a smaller version of the house would have been made out of lighter materials, then those developers would know immediately where to begin with their work instead of depending on each implementation.
    References :
    Methods of a small development group

    http://en.wikipedia.org/wiki/Model-driven_engineering

    http://en.wikipedia.org/wiki/Unified_Modeling_Language

Leave a Reply