Both RUP and ITUP have a well-defined approach to deploying a software application or system. This includes
everything from roll-out and installation to training end users.
-
RUP describes not only the development project, but also what is involved in deploying developed software.
This involves the RUP Deployment Discipline.
-
ITUP describes how a developed solution is installed and rolled out into the infrastructure as a "release".
This is performed by the Release Management Process, which is essentially the ITIL Release Management
Process.
Commonality
Deployment in RUP and ITUP are essentially the same. It involves the following aspects:
-
Planning deployment
-
Creating deployment communications, training, and other related materials
-
Creating the deployment scripts and mechanisms
-
Deployment
RUP and ITUP approach this differently at the detailed level, but the differences are not considered significantly
different.
Variability
The primary difference between the RUP Deployment discipline and the ITUP Release Management process is the context in
which they both work. To explain the contextual differences, it is important to understand two different
perspectives on development and deployment.
-
Software Vendor Perspective – In this perspective, the software vendor develops custom or shrinkwrapped software
and provides that software either directly to a customer or via third-party channels. Once that software is
acquired by the customer, it is typically deployed internally by the customer’s IT organization. To the
software vendor, development means development of the software developed by the vendor, and deployment means
deploying the software to the market or to a specific customer’s IT organization.
-
IT Organization Perspective – In this perspective, the IT organization either develops its own software or acquires
software from a vendor. Once that software is deemed acceptable for internal deployment, the IT organization
must develop installation and deployment mechanisms and procedures. The software is then deployed within the
organization. To the IT organization, development typically means either 3rd-party development or internal
development, and may also mean development of deployment mechanisms. Deployment means rolling out the
software to the entire company.
The following figure depicts these two perspectives.
RUP primarily describes deployment from the vendor perspective, whereas ITUP primarily describes deployment from the IT
organization perspective. This explains a number of other differences found between RUP and ITUP, including the
following:
-
ITUP strictly adheres to ITIL concepts such as changes and releases, whereas RUP uses terminology and activities
that are not specifically related to ITIL. For instance, the term "release" is used differently between ITUP
and RUP.
-
In addition, the activities performed by ITUP and RUP are somewhat different. ITUP has greater focus on the
development of the deployment mechanism. Here is how RUP and ITUP approach the deployment aspects mentioned
in the previous section:
Deployment Aspect
|
RUP Activity
|
ITUP Activity
|
Planning
|
Plan Deployment
|
Plan Release
Plan Release Roll-out
|
Creating related material
|
Develop Support Material
|
Communicate, Prepare, and Train for Release
|
Creating deployment scripts and mechanisms
|
Produce Deployment Unit
|
Design and Build Release
|
Deployment
|
Provide Access to Download Site
|
Distribute and Install Release
|
Other
|
Manage Acceptance Test
|
Perform Solution Acceptance Review (Solution Acceptance process)
|
|
Beta Test Product
|
IT organizations view beta products as just another type of deployment, although to a smaller number of
users.
|
|
Manage Acceptance for Custom Install
|
Does not apply. This applies to a software provider's perspective
|
|
Package Product
|
Does not apply. This comes from a software provider's perspective.
|
Deployment aspect RUP activity ITUP activity
Planning Plan Deployment Plan Release
Plan Release Roll-out
Creating related material Develop Support Material Communicate, Prepare, and Train for Release
Creating deployment scripts and mechanisms Produce Deployment Unit Design and Build Release
Accept Release
Deployment Provide Access to Download Site Distribute and Install Release
Other Manage Acceptance Test
Perform Solution Acceptance Review (Solution Acceptance process)
Beta Test Product Does not apply, since IT organizations view beta products as just another type of deployment,
although to a smaller number of users.
Manage Acceptance for Custom Install Does not apply. This comes from the Vendor Perspective.
Package Product Does not apply. This comes from the Vendor Perspective.
Mapping Between RUP and ITUP
RUP Discipline ITUP Process
Deployment (roll-out of a system) Release Management
Potential common work products include:
-
RUP Work Product ITUP Work Product
-
Deployment Plan Release Plan and Definition
-
Roll-Out Plan
-
Build Release Package
Summary
Thus, the RUP Deployment Discipline and the ITUP Release Management Process are somewhat similar, but they view
deployment from two different perspectives. It
|