Rational Unified Process And Extreme Programming
Abstract: The IBM Rational Unified Process (r) (RUP(r),) is a comprehensive software-development process framework. It includes a range of standard examples. The methods that come from RUP differ from simple processes that address the needs of smaller projects with short product cycles-to more extensive processes that address the broader needs of large and possibly distributed teams. RUP is used successfully in projects of all sizes and kinds. This whitepaper describes the ways in which RUP can be applied in a light-weight manner to small-scale projects. This white paper explains how to apply extreme programming (XP) in the overall framework of a project. Inception Inception is essential for the development of new products, and you need to address critical requirements and business risks before you can move forward with the project. The Inception phase for projects that are enhancing an existing system is less time-consuming however, it is still focused on making sure the project is worthwhile and feasible. Inception is the moment when you provide the IT outsourcing business case to the creation of the software. Inception is the time when you design the vision. It's a comprehensive description of the system. It explains to everyone what the system does and could also describe those who use it, how it is being used, what features must be included and what restrictions must be met. are placed on it. XP defines three phases: Exploration, Commitment, and steering. These phases do not correspond to the RUP phases, so we will use the RUP phases to describe the process. The Vision could be extremely brief, perhaps only a paragraph or two. The Vision typically has the most crucial attributes that software should offer to the customer. Four essential Inception activities specified in RUP are: Describe the scope of your project. Plan and prepare your business plan. o Synthesize candidate architecture. o Create the project's environment. Explanation The purpose of the Elaboration stage is to establish the baseline for the architecture of the system in order to establish a stable basis for the majority of the design and development effort during the construction phase. After assessing the risks and taking into consideration the most critical needs, the structure is designed. The architecture's stability is assessed through an architectural prototype or two. In RUP design, the focus is on the notion of system architecture and, for software-intensive systems, software architecture. RUP suggests that components be utilized. This is one of six best practices for software development. The RUP also recommends that you spend time maintaining and developing the architecture. The time put into this effort mitigates the risks associated with a brittle and rigid system. XP is a "metaphor" of architecture. This metaphor represents a part of the architecture while the rest develops organically as code is written. XP believes architecture is created from simple designs and constant refining of code. You should complete at least three of these activities in the course of preparing for any project: o Define, validate and establish the baseline of the architecture o To improve the vision. o Create and keep a baseline of iteration plans for the Construction phase. Construction Construction is the final stage of development of a system. In some ways, the construction phase is a manufacturing procedure. The focus is on managing resources and controlling processes to increase the efficiency, cost, and schedule. In this way, the management's mindset changes from Inception and Elaboration to Construction and Transition, where intellectual property is created. Every Construction version has three fundamental activities: Manage resources and control process. Develop and test the components. Check the iteration. Transition The goal of the Transition phase is to ensure that software is available for its end users. The transition phase involves testing the product before it is released and minor adjustments based upon user feedback. At this point in the development process it is essential to collect feedback from the users. be focused on fine-tuning of the product installation, configuration, and usability issues. The essential Transition activities are the following: o Finalize end-user support material. o To test the product within a client environment. o We fine tune our products based on customer feedback. o Deliver the final product to the user who will be using it. In the Transition phase you'll be able to make a variety of artifacts. If your product will be released in the future (and which ones don't? You'll be able to pinpoint features and correct problems for the next release. The most crucial artifacts to every project include: o Deployment Plan o Release Notes Training Materials and Documentation. Digest Software development is more than writing code. Software development must encompass all the steps that are required to offer quality for customers. A complete process does not require a huge amount of effort. We've shown you how you can create a small, yet complete process by focusing on the key tasks and objects to your project. If it helps to reduce risk, then you should complete an activity or make an artifact. You can use as much or as little process and formality in your project team as you want. RUP and XP are not required to be used separately. When you combine techniques from both it is possible to create an approach that allows you to develop better quality software faster than you do today. Robert Martin describes the dX process.8 This is an example of a RUP-compliant process. A successful software development process is based on the most effective practices that have been proven in the industry. These methods have been shown to work in real software development companies. Today, XP is the most popular method. It is code-centric, and is able to provide low overhead and high productivity. Many techniques are available in XP and should be considered when appropriate. XP focuses on the story, test, and code. It discusses plans in a certain amount and treats the capture of plans as lightly. XP implies that you may create other items, such as "do CRC designs with some cards or draw out some UML ..." or "Don't produce documents or other objects which aren't in use ...", but treats these items in passing. RUP encourages you to produce only what is essential and required as you create and modify your plan of development. It also highlights the possible items. RUP is a procedure that covers the entire software development lifecycle. It is based on the best practices developed on thousands of projects. We encourage innovation and the exploration of new techniques that could lead to better practices. We look forward to the incorporation of the latest best practices in RUP as they become available.

Leave a Reply

Your email address will not be published.