Is defining every method/state per object in a series of UML diagrams representative of MDA in general?
- by Max
I am currently working on a project where we use a framework that combines code generation and ORM together with UML to develop software. Methods are added to UML classes and are generated into partial classes where "stuff happens". For example, an UML class "Content" could have the method DeleteFromFileSystem(void). Which could be implemented like this:
public partial class Content
{
public void DeleteFromFileSystem()
{
File.Delete(...);
}
}
All methods are designed like this. Everything happens in these gargantuan logic-bomb domain classes.
Is this how MDA or DDD or similar usually is done? For now my impression of MDA/DDD (which this has been called by higherups) is that it severely stunts my productivity (everything must be done The Way) and that it hinders maintenance work since all logic are roped, entrenched, interspersed into the mentioned gargantuan bombs.
Please refrain from interpreting this as a rant - I am merely curious if this is typical MDA or some sort of extreme MDA
UPDATE
Concerning the example above, in my opinion Content shouldn't handle deleting itself as such. What if we change from local storage to Amazon S3, in that case we would have to reimplement this functionality scattered over multiple places instead of one single interface which we can provide a second implementation for.
