Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  RUP Methodology
Previous Previous
Next Next
New Post 11/12/2013 12:52 AM
User is offline suraj123
1 posts
No Ranking

RUP Methodology 


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. 




New Post 11/13/2013 7:17 AM
User is offline dldelancey
61 posts
8th Level Poster

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.

New Post 11/14/2013 2:04 AM
User is offline Kimbo
438 posts
5th Level Poster

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:

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.


New Post 11/14/2013 8:08 AM
User is offline Sandy
74 posts
8th Level Poster

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.


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

Community Blog - Latest Posts

With the advent of modern-day cloud infrastructure, many business-critical applications like databases, ERPs, Marketing applications have all moved to the cloud. With this, most of the business-critical data now reside in the cloud. Now that all the business data resides on the cloud, companies need a data warehouse that can seamlessly store the da...
2 Responses
Bpm'online, a global business software company leading in the space of low-code, process automation, and CRM, will be soon announcing their new company name. The new name will be launched in the sky via a breathtaking skydiving performance involving 160 bpm’online employees, including the CEO. The new name of bpm’online is to be fo...
0 Responses
Heta Raval
Heta Raval
In a current scenario, when you are eliciting software service-based requirements then, you may be able to derive requirements in certain varieties. In the beginning, they can be just functional or non-functional requirements. But when you come across many other requirements as time goes, you can conclude requirements into several categories and wi...
0 Responses

Latest Articles

What’s Missing from Agile?
Oct 20, 2019
John Seddon launches an attack on the value of Agile as practiced and charts a better way to analyse and design for improvement, making information te...
Copyright 2006-2019 by Modern Analyst Media LLC