RUP has 4 phases and each phase is divided into number of iterations, now I want to know whether we pass through all the phases of RUP in each of the iterations(format1 mentioned below) or the iterations moves in progressive in each of the phases (format2, mentioned below). For e.g Format 1:
Iteration1 , we have inception,elaboration,construction and transition Iteration2 , again we will have inception,elaboration,construction and transition Format 2: Inception phase: we have iteration 1 and iteration 2 Elaboration phase: we have iteration 3 and iteration 4 Construction phase: we have iteration 5 and iteration 6 Transition phase: we have iteration 7 and iteration 8
I feel the structure should be in the format1 mentioned above. Any clarification is appreciated. Hari
It's format 2. You need to understand that in *every* iteration, regardless of the current phase, there is some amount of analysis, design, coding and testing to be done. It's just the *focus* which differs between the phases (and therefore *how much* of each activity you will do). Iterations are ideally time boxed. That is, every iteration lasts the same amount of time - a week, two weeks or something. You start in the inception phase. The focus is on deciding wether it makes sense to invest in the project. You will mainly analyse the idea for the system and the possible ROI, but may also want to think about rough ideas for the implementation and might even try out some critical architectural ideas. (This phase might be shorter than an iteration.) Once you are sure that you want to invest more in the project, you are in the elaboration phase. Here you want to get a feel of the necessary budget for the project, make an initial rough plan and adress possible risks. You enter the construction phase when you are sure that you can do the project with reasonable resources and have addressed the most important risks. Here is where focus is on designing, coding and testing the system, while still refining your understanding about the problem domain. The transition phase is where you concentrate on getting the system to the users (if I remember correctly). As the users will give you feedback about the system, you will still need to make changes to the system, though. Does that compute?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
It's perfectly legal to hammer the RUP into a shape where your construction phase uses agile methods. The other "up front" phases will probably be a lot smaller if you do this. The main thing that RUP will push back on is the agile notion of "emergent architecture" evolving during construction. Grady Booch & co. would still like to see more architecture up front.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Joined: Jul 11, 2001
Originally posted by Stan James: It's perfectly legal to hammer the RUP into a shape where your construction phase uses agile methods. The other "up front" phases will probably be a lot smaller if you do this.
Why only the construction phase? Doesn't XP's Exploration phase perfectly match to RUP's Elaboration phase, for example?
The main thing that RUP will push back on is the agile notion of "emergent architecture" evolving during construction. Grady Booch & co. would still like to see more architecture up front.
Interesting. Where do you get this from?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com