Business Analyst Community & Resources | Modern Analyst

Career Forums

Modern Analyst Forums Business and Sy... Agile Analysis ... RUP Methodology

11/12/2013 1:52 AM

	suraj123
1 posts

RUP Methodology

Hi,

Can anyone please let me know how do we divide a large project into key identical subsystems to perform RUP Methodology.

Example - If I need to create an airline reservation system, how to get to know the key subsystems so that I can create iteration cycles?

To get to know the subsystems, should we not create a high level use case document initially? If yes, what is this phase called?

As I have seen in different materials, it says each iteration has 4 phases (Inception, Elaboration, Construction, Transition), but no where it mentions how are the iterations identified, what goes behind planning of the iterations.

Thanks!!

11/13/2013 8:17 AM

	dldelancey
61 posts

Re: RUP Methodology

Disclaimer: I've only used variations and hybridizations of RUP.

I think you may have it backward. Each iteration does not have 4 phases. Rather, the project has 4 phases and each phase has iterations. You do your initial iteration planning in the Inception phase. If you google something like "RUP iteration planning," you should get some results that describes the formal methods and will probably find some iteration plan templates.

11/14/2013 3:04 AM

	Kimbo
456 posts

Re: RUP Methodology

Modified By Kimbo on 11/14/2013 5:05:02 AM)

There is good information on wikipedia about RUP.

Back in the day I used this book as a learning tool:

http://www.amazon.com/Rational-Unified-Process-Introduction-3rd/dp/0321197704/ref=sr_1_1?s=books&ie=UTF8&qid=1384426887&sr=1-1&keywords=rational+unified+process

Remember when all else fails, use common sense. How you partition should make sense, don't do it because it seems like what you should do, to fit into some methodology.

Kimbo

11/14/2013 9:08 AM

	Sandy
74 posts

Re: RUP Methodology

Your iterations should be based on a few considerations:

Use cases or components with highest architectural risk are ususally included in the first iteration, so that any challenges or problems can be identified and addressed as early as possible
Each iteration builds upon the development of the previous iteration(s). If 'Function B' is dependent upon 'Function A', then 'Function A' should be developed first and 'Function B' should be assigned to a later iteration. For example, presumably flights need to be scheduled before a passenger can make a reservation. So you would probably want to build the scheduling components first (if in-scope). Then when the booking component is built and tested, there will be working functionality to setup and maintain the schedules - which makes it much easier to test the booking functionality.
Core and common functions should be developed first, so they can be refined and finalized early in the project. This minimizes impact and re-work if there are errors in requirements or development for this pieces.

Note that it's probably not possible or desirable for all iterations to be 'identical subsystems'. In fact, the essence of RUP iteration is that early development gets elaborated and refined. So each iteration carries forward some re-work and refinement of previous development. Therefore the scope of new development often gets gradually smaller over each iteration, to allow for carried forward refinements and bug-fixes from prior iterations.

Sandy