Rational Unified Course and Extreme Programming

Abstract: The IBM Rational Unified System (RUP ) is a complete software-development action framework that comes with indefinite out-of-the-box instances. Processes derived from RUP vary from lightweight addressing the needs of small projects with short product cycles-to more comprehensive processes addressing the broader needs of large, possibly distributed project teams. Projects of all types and sizes have successfully used RUP. This white paper describes how to apply RUP in a lightweight manner to small projects. We describe how to effectively apply extreme Programming (XP) techniques within the broader context of a complete project. Inception Inception is significant for contemporary development efforts, where you must direction relevant business and requirement risks before the project can proceed. For projects focused on enhancements to an existing system, the Inception phase is shorter, however is still focused on ensuring that the project is both worth doing and p
ossible. During Inception, you build the business condition for building the software. The Vision is a key artifact produced during Inception. It is a high-level description of the system. It tells everyone what the system is, and may also tell who will application it, why it will be used, what features must be present and what constraints 1 XP defines three phases: Exploration, Commitment, and Steering. These do not map well to RUP phases so we choose to employ the four RUP phases to describe the manner exist. The Vision may be very short, perhaps only a paragraph or two. Often the Vision contains the critical features the software must provide to the customer. Four essential Inception activities specified in RUP are: Formulate the scope of the project. Plan and prepare the business case. Synthesize candidate architecture. Prepare the project environment. Elaboration The goal of the Elaboration phase is to baseline the architecture of the system to provide a stable b
asis for the bulk of the design and implementation effort in the Construction phase. The architecture evolves away of a consideration of the most significant requirements (those that have a great impact on the architecture of the system) and an assessment of risk. The stability of the architecture is evaluated through one or more architectural prototypes. In RUP, design activities focus on the notion of system architecture and, for software-intensive systems, software architecture. Using component architectures is one of the six best practices of software development embodied in RUP, which recommends spending age developing and maintaining the architecture. The period spent on this effort mitigates the risks associated with a brittle and inflexible system. XP replaces the notion of architecture by "metaphor." The metaphor captures part of the architecture, whereas the rest of the architecture evolves as a natural result of code development. XP assumes that architecture
emerges from producing the simplest design and continually refactoring the code. Full text: http://computerandtechnologies.com/technology/news_2008-06-03-01-00-04-550.html