L
la.rodriguezcastro
Hi,
I'm starting a new project in VS.NET 2005 and I've found that Rational
XDE is not working with VS.NET 2005. I think XDE is a very good UML
desing tool, but I think IBM is droping it's VS.NET 2005.
So, my question is, what Modeling tool are you using with VS.NET 2005?
Here are some things I've tried.
· Rational XDE: The best in VS.NET 2003. Doesn't work in 2005.
· Visio: Good to start a high level UML modeling, but useless once the
development team starts to code because of the no-integration with the
IDE.
· Visual-Paradigm SDE: I've not been able to make it run properly with
VS.NET 2005. It works well with VS.NET 2003. Not as good as Rational
XDE, but good enought.
· MDG - www.sparxsystems.com/vsip/: It hasn't a good IDE integration.
....
Here is what I think is essential in a modeling tool:
· Support for the basic diagrams: Class diagrams, Secuence Diagrams,
Use Case Diagrams
· On-demand Code synchronization: Without it any desing, no matters
what good it is, will be useless once the development starts. VS.NET
has a no-so-bad class designer, but it works real-time only, so the
architect can not design anything while a developer is working
(check-out) with the implied classes.
What are you using? Could someone point me to a decent Modeling tool?
Thanks in advance.
I'm starting a new project in VS.NET 2005 and I've found that Rational
XDE is not working with VS.NET 2005. I think XDE is a very good UML
desing tool, but I think IBM is droping it's VS.NET 2005.
So, my question is, what Modeling tool are you using with VS.NET 2005?
Here are some things I've tried.
· Rational XDE: The best in VS.NET 2003. Doesn't work in 2005.
· Visio: Good to start a high level UML modeling, but useless once the
development team starts to code because of the no-integration with the
IDE.
· Visual-Paradigm SDE: I've not been able to make it run properly with
VS.NET 2005. It works well with VS.NET 2003. Not as good as Rational
XDE, but good enought.
· MDG - www.sparxsystems.com/vsip/: It hasn't a good IDE integration.
....
Here is what I think is essential in a modeling tool:
· Support for the basic diagrams: Class diagrams, Secuence Diagrams,
Use Case Diagrams
· On-demand Code synchronization: Without it any desing, no matters
what good it is, will be useless once the development starts. VS.NET
has a no-so-bad class designer, but it works real-time only, so the
architect can not design anything while a developer is working
(check-out) with the implied classes.
What are you using? Could someone point me to a decent Modeling tool?
Thanks in advance.