The Rational Unified Process (RUP) and the IBM Tivoli Unified Process (ITUP) are process frameworks that emerged from
different perspectives. These process frameworks are related in a number of ways but serve different
purposes.
The IBM Service Management Adoption Model, depicted in
Figure 1, provides insight into the impact of each IT Management Domain. RUP primarily addresses IT Development,
whereas ITUP provides most of its content in the areas of IT Operations, IT Business Management, and IT
Governance. IT Development can be implemented by a variety of different SDLCs (system development life
cycles). RUP is a very prominent SDLC, although there are other SDLCs that are used by IT
organizations.
Figure 1 - High-level Model of Information Technology
RUP was created to describe the processes involved in a software or system development project. It emerged as a
unification of various object-oriented software development processes. Software development projects occur as
part of an IT organization, but may also occur in the product development side of a software development
business. Within the scope of software development, RUP identifies all of the disciplines that are needed, which
does not include a consideration of IT operations.
ITUP was created to describe an IT organization implementing IT Service Management. The focus of ITUP is IT
operations, but also includes processes for development (called Solution Development). In general, RUP can be used
in place of some ITUP processes, but not others.
The ITUP processes for Solution Development are: Solution Requirements, Solution Analysis and Design, Solution Build,
Solution Test, and Solution Acceptance. The RUP Requirements, Analysis & Design, Implementation, and Test disciplines may be used in place of the related ITUP Solution
Development processes.
However, there are other RUP disciplines (like Configuration & Change Management, Deployment, and Project Management) that at first seem to relate directly to the ITUP
processes:
But Configuration & Change Management, Deployment, and Project Management are more accurately portrayed as indirect
relationships. In general, RUP can be used in place of the ITUP processes that are designated as having a
direct relationship (see Figure2). But because of the difference in scope and context between the RUP process
framework and the ITUP process framework the ITUP processes that are designated as having an indirect relationship can
not be replaced by RUP. Fundamentally, this is because the RUP and ITUP were created to address the needs of
different communities. RUP addresses primarily an IT software development community, whereas ITUP primarily addresses
an IT operations community.
Figure 2 - ITUP and RUP Relationship
Table1 - RUP to ITUP Relationship contains a mapping to content that begins
to describe the relationship between RUP and ITUP.
Table 1 - RUP to ITUP Relationship
|