O
Olav - Remove T99T
Started a new project where Rational XDE is used with VS.NET.
Though it seems its not really used consequently at developer level.
Some VS projects have models, some don't.
So my question is. What would me "economical" things to use it for,
and how do I get there? By economical I mean that I do not have to
spend a lot of time before I increase my productivity.
People ive talked to don't think its a good idea to use it for reverse-
engineering to understand existing code.
...If not I think the main use of UML is to communicate your design to
others.
If I'm not required to do that, - I don't think its much point in doing
diagrams before I code?
So I think the best would be to code first and then reverse-engineer
so that I have diagram ready to discuss with others?
About mining existing code...does it have any advantages over VS.NET?
VS.NET has some weaknesses. For example go to reference doesn't work
very well when there are many methods with a similar signature.
(So its very difficult to figure out where something is called from).
Lastly, what are good resources for getting into what I need?
The only .NET XDE book seems to have bad critics.
Is there for example a good resource which just explains how
to reverse-engineer from scratch?
I have previously done class- and sequence-diagrams with Magicdraw.
(I'm posting this in a Visio-group. Really the best place I could find)
Thanks
Olav
Though it seems its not really used consequently at developer level.
Some VS projects have models, some don't.
So my question is. What would me "economical" things to use it for,
and how do I get there? By economical I mean that I do not have to
spend a lot of time before I increase my productivity.
People ive talked to don't think its a good idea to use it for reverse-
engineering to understand existing code.
...If not I think the main use of UML is to communicate your design to
others.
If I'm not required to do that, - I don't think its much point in doing
diagrams before I code?
So I think the best would be to code first and then reverse-engineer
so that I have diagram ready to discuss with others?
About mining existing code...does it have any advantages over VS.NET?
VS.NET has some weaknesses. For example go to reference doesn't work
very well when there are many methods with a similar signature.
(So its very difficult to figure out where something is called from).
Lastly, what are good resources for getting into what I need?
The only .NET XDE book seems to have bad critics.
Is there for example a good resource which just explains how
to reverse-engineer from scratch?
I have previously done class- and sequence-diagrams with Magicdraw.
(I'm posting this in a Visio-group. Really the best place I could find)
Thanks
Olav