Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Our team is fairly new to domain driven design. We have a new project that just moved from design phase into coding phase. In the design phase, some team members created UML design models in Visio, while others just started coding. Also, with the pressures of build releases, many of our models are becoming out of date quickly.
Is it important to keep the object models up to date? Is it important to have them for all/most sub-systems?
I guess the answer is “it depends”, no?
If the project is small, changing at a rapid pace, etc etc, the ROI of models is probably pretty bad, and in the end all that matters is the working code.
On the other hand, for multi-year multi-phase projects with a high degree of ceremony, a changing development team, etc etc, you’ll have great benefit from some sort of documentation. The object models can be one such documentation.
There is no silver bullet after all, so, depending on which end of the scale your project lies, you may find the models to be very valuable or just costly to maintain.