RUP vs SDLC

hello..
can anyone tlel me what's the pros and cons of choosing RUP over the tradition SDLC method in developing a system?

Hi Kingston,
When you say "traditional SDLC", which one are you referring to exactly? Would it be the "Waterfall" method? Structured Systems Analysis and Design using DFDs, ERDs, Flowcharts, etc.? Or perhaps even Object-Oriented Analysis and Design?
From what I know about RUP (which isn't really a whole lot, honestly) it is based largely on OO analysis and design, UML, Use Cases, and Iterative/Incremental development. A comparison with another methodology would probably have to start with comparing these aspects with their equivalent in the "traditional" SDLC.
Junilu

I strongly recommend you read UML Distilled. Talks about benefits of using RUP against traditional structured approach.
But main pros for RUP are 1. Iterative development 2. Use case driven approach 3. Architecture centric. Would need to go into too much detail to explain...read the book
Aftab

Traditional "SDLC " , Do you mean Waterfall Method ? or it is something else ?

Systems Development Life Cycle
us customs uses it

(R)UP is just another type of the SDLC. People often associate Waterfall only with the SDLC. The main difference is that Unified Process is a very modern, very forward looking iterative type of the SDLC.
Go to www.therationaledge.com and read all about it, or pay me big bucks for consulting services on it (just kidding).