Don’t waste your time RUP and Rose.



RUP is not good even for a mega-company like IBM, everyone’s switching to different levels of XP methodology (or as Alistair Cockburn calls it Crystal Clear, Crystal blabla). Read XP explained or http://www.extremeprogramming.org/ and http://www.xprogramming.com/.

If you really want to become a senior developer/architect you SHOULD be completely familiar with concepts expressed in these books:

- Refactoring by Martin Fowler

- Design Patterns by Erich Gamma/…

- XP explained by Kent Beck/… or anything related to XP

If you don’t then just don’t call yourself a senior developer. Period.



Rose is indeed a piece of shit, try TogetherJ (www.togethersoft.com). Just see this thread for fun: www.theserverside.com/.../thread.jsp :o)



I also strongly suggest you to use IntelliJ IDEA as your development environment (www.intellij.com/eap).

I 'v heard that XP is not accepted yet.I think that this is a new good idea in in software developing methodologies.And It should be tested before we can use it in critical projects.
As a developer who want's to be on the market,I should learn to use the most widely accepted tools and methods to reach my goals.I also khows that together is a greate developing tool I tested it but I could not find it in Iran.

Again I don't say that XP is not good.But it is still in it's first steps but RUP came at 1998 and it is a branch of unified process which is developed by jacobson,booch,rambough who are respectively the founder of OOSE,BOOCH & OMT methodologies.
These guys are the gods of OO.

I will appreciate you if you can give me those book that you listed to take a copy of them.

Please feel free to start a discussion about these kind of things I will learn many things from your advices.

XP is new but it’s proven. RUP is a product and that’s why those gods stick to it! Anyway, just search and study and you’ll see that all others gods accept it, read Alistair Cockburn’s book for example. I’m not going to start a religious war here at j2EE list, but if you analyze XP you’ll see that most of its practices are doable, unlike other heavyweight methodologies that offer you non-doable stuff. The important thing IMHO is to keep the *intent* of its practices in mind, while other heavyweight methodologies drawn you in details, you just blindly follow.

I personally prefer XP for small projects, RUP is not
a software development process.
It is a frame work you can build your own methodology
on it, it needs a lot of effort and exprience for a
fresh person to learn how to use it. you can also
learn USDP (Universal Software Development Process)
which is also made by 3 amigos.

I think you know RUP well.Aren't you?

Please tell me if I can have a copy of your book & if possible together 5.5 .
I'll appreciate your help if you say yes.

of course you can have them both, why not?
does any body else want books about RUP and USDP ?
any way USDP book is teached to us in Sharif
University, since RUP is continue of the USDP effor,
it may be very useful for any one who wants to learn
RUP to first read the book OOAD of grady booch and
USDP of 3 amigos before reading RUP if s/he has enough
time. other wise reading the RUP book will no take
much time.

thanks for your reply.I 'll study XP to find out why you say XP is better.