Monday, February 26, 2007

Visual studio 2005 Class Designer

I am not a big fan of UML, or any diagram in the development process.  The biggest issue I found is the inconsistency between those nice diagrams and the actual codes.  I just found it's too difficult to think over every possible situations at the beginning stage of the project, not just the developers. The clients also have the same issue, they are not very clear what they want too at the beginning. I find out unless you are a real guru in making those nice diagrams, and you can always make changes to those diagrams very fast ( I am NOT), it's so hard to keep those diagrams consistent with your code when the project requirements change.

 

The visual studio class design is a different story. The changes you made to the designer can be applied to the code instantly, on the other hand, the changes you made to the code can be applied to the designer instantly too. You don't have to worry about two pieces any more, you can just worry about one piece.

 

There is a power toy for the enhancement here too.

No comments: