The web design team is proposing that the current website be revamped if not completely redone. In order for them to do this they have decided to go with the RUP or rational unified process. This will allow them to be able to suit the requirements of the organization where it is implemented. This type of process will allow them to be able to modify the website as issues come in and they will be able to better connect with the customers who use the website. The RUP process uses six best practices or methodologies, which compared to other processes, are more modern in the approach and are used to develop a variety of software applications. The six are iterative development, manage requirements, component based architecture, visual software model, software quality verification and control changes. If the company follows these best practices the company will be successful in the RUP process for this project.
The RUP life cycle
RUP's life cycle consists of four consecutive phases: inception, elaboration, construction, and transition. In the inception phase, the concept behind the process is reiterated and the boundaries of the project are defined. In the elaboration phase, the problem domain is identified and architecture established. In the construction phase, the software is developed. Finally, in the transition phase, the product is sent to the user domain.
Inception Phase
The first phase of the process reiterates the concept of what they web design departments want. It defines the boundary or the project. Some of the things that will be determined in this phase include external factors, risk analysis as well as cost and budget. The final product of this phase is that a vision document detailing the project requirements, features and constraints. Phases and iterations are incorporated into the project plan. A forecast of the initial business case, risks, and success criteria are also created, as well as a use case model and business model.
Elaboration phase This is a vital stage in the process where issues identified in the inception phase like the main requirements and constraints of the project are dealt with at this time. When looking at the entire scope of the project architectural decisions as well as functional and nonfunctional requirements are discussed. Most of the time it is generally within this phase that the project evolves from a small, low risk and lost cost initiative to a complex, high risk, and high cost involved project.
The elaboration phase ensures that the project plan and architecture developed in the end are stable enough for the system to enter the construction phase. Checks are conducted to ensure that the second project milestone, the Life Cycle Architecture milestone, is met. Based on the outcome, a decision on continuing with the project is made.
Construction phase It is within this phase that we start to see the actual features of the software being developed, integrated as well as tested. It is here where the product will undergo the transition from being a concept to becoming a functional product within this phase. It is within this phase that the construction of the product can be done on a parallel platform and by doing this smooth’s the delivery of resources. The end of this phase ensures a product developed on standard platforms with a user manual, and a detailed description of its release.
Transition phase Within this phase of the process there are various activities which could range from very complex to very simple are carried out as to ensure that a product of the highest quality reaches the user domain. Some of these activities include iterations, beta releases, the fixing of bugs and development and enhancement releases. It is within this phase that training and supporting users as they begin to become familiar with the product. This allows for feedback to be gathered. The feedback is able to raise issues such as particular features of the product, defects or further releases.
Generally, before a product is sent to the user domain, a sample or model of the system that meets standard specifications is sent for user evaluation. This prior evaluation ensures that there will be minimum chances for errors when the actual product is sent. This will facilitate a positive understanding on the sides of both the developer and the user. The transition phase must aim at providing support to users to operate the system on their own, collaborate with the stakeholder's perception of the project, effectively develop the project within the given period of time, meet all requirements, and be cost effective. The Project Release milestone, which is the fourth milestone, reiterates the objectives that must be achieved at the end of this phase. Evaluation of the success of the transition phase is based on the user's satisfaction. It is also dependent on whether the product's projected expenditure and actual expenditure are within agreeable limits.

Benefits
RUP has been credited with being one of the first iterative software development processes to establish UML as a common language for process oriented protocols. It also reduces scrap or rework by using an iterative process. Also, potential risks are identified and removed effectively in early development stages. It has a unique list of six best practices which detail the best methods to follow to facilitate effective software development.
However, RUP has certain limitations too. It is development centric and focuses mainly on the development aspect of software. As a result, it neither extends beyond development nor tackles issues at enterprise and management levels.

Conclusion The RUP Software Development Life Cycle is the best option when speaking about the implementation of this web design. If the IT department uses this RUP it will prove to be a successful venture and one that will bring value and pride to the company.

References
Dennis, A. (2009). Systems Analysis and DesignSystems Analysis and Design (4th ed.). Retrieved from The University of Phoenix eBook Collection database. The University of Phoenix eBook Collection database..
Valacich, J.S., & Hoffer, J.A. (2009). Essentials of Systems Analysis and Design (4th ed.). Retrieved from The University of Phoenix eBook Collection database.

University of Phoenix. (2012). Element K Tutorials IT Pro Courses IT vLabs. Retrieved from

University of Phoenix, BSA/375 Fundamentals of Business Systems Development website