Rational Software Architect - A mini review
Saturday, May 12, 2007 by Shreyas
J2EE development is going strong and it will certainly in the future. In most places. So, no wonder products aimed at easing stuff up for developers is destined to thrive. So is RSA - http://www-306.ibm.com/software/awdtools/architect/swarchitect/index.html.On thinking what makes RSA tick(read RSA 6 or 7)..the following points spring up in that order:
1. All under one roof - do every deliverable with RSA.
2. Don't sweat it out - It's fairly simple to learn and get acquainted with.
3. Performance - Will talk about this soon.
Now with RSA, you can do/deliver most of your J2EE artifacts and it provides a very good usable IDE to do so. One of the noteworthy things is UML modelling/design. We all know how important is design in any project and a good design cuts cost/rework and adds to the bottom line and so on. But design seldom is stable and it evolves/changes during development. So syncing up the developed code and design is always a challenge and doing it well is very useful for everyone. RSA accommodates this with alacrity.Now the advantage here is that, you can have the design model and development code in the same workspace and it allows for easy referring to the design during development and vice versa. Forward engineering and reverse engineering have never been so easy. Applying design patterns can also be done but I haven't tried it out myself.
As its built on Eclipse, development ease is also taken care of. Further it supports And to use RSA, the tutorials are fairly good and the time to learn it will be minimal, provided the user knows what he wants.In any system, the wait time experienced promotes a feeling of added complexity. And this factor is less in RSA. Since there is no need of a separate designing software, it will be easy on the system resources as most of good UML design softwares tend to eat up more resources.
Ofcourse, there's a lot more in RSA than what's mentioned here which haven't been discussed like JSF/Junits/Change management linking/Code review tools/Plugins etc. Overall the experience with RSA for J2EE development is good.
1. All under one roof - do every deliverable with RSA.
2. Don't sweat it out - It's fairly simple to learn and get acquainted with.
3. Performance - Will talk about this soon.
Now with RSA, you can do/deliver most of your J2EE artifacts and it provides a very good usable IDE to do so. One of the noteworthy things is UML modelling/design. We all know how important is design in any project and a good design cuts cost/rework and adds to the bottom line and so on. But design seldom is stable and it evolves/changes during development. So syncing up the developed code and design is always a challenge and doing it well is very useful for everyone. RSA accommodates this with alacrity.Now the advantage here is that, you can have the design model and development code in the same workspace and it allows for easy referring to the design during development and vice versa. Forward engineering and reverse engineering have never been so easy. Applying design patterns can also be done but I haven't tried it out myself.
As its built on Eclipse, development ease is also taken care of. Further it supports And to use RSA, the tutorials are fairly good and the time to learn it will be minimal, provided the user knows what he wants.In any system, the wait time experienced promotes a feeling of added complexity. And this factor is less in RSA. Since there is no need of a separate designing software, it will be easy on the system resources as most of good UML design softwares tend to eat up more resources.
Ofcourse, there's a lot more in RSA than what's mentioned here which haven't been discussed like JSF/Junits/Change management linking/Code review tools/Plugins etc. Overall the experience with RSA for J2EE development is good.
Posted in:
PonderWrite
|
|
|
