Page 17 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Unit 1: Introduction to Software Project Management

variety of tools can be used to report the performance of the project such as PERT Charts, Notes
GANTT charts, Logical Bar Charts, Histograms, Pie Charts, etc.
12. Planning Change Management: Study of project performance can demand certain aspects
of the project be changed. The Requests for Changes need to be analyzed cautiously and its
impact on the project should be analyzed. Considering all these aspects the Project Plan
may be customized to accommodate this request for Change. Change Management is also
essential to accommodate the implementation of the project at present under development
in the production environment. When the novel product is implemented in the production
environment it should not negatively impact the environment or the presentation of
other applications sharing the same hosting environment.
13. Project Rollout Planning: In Enterprise environments, the achievement of the Project depends
a huge deal on the success of its rollout and implementations. Whenever a Project is rolled
out it may influence the technical systems, business systems and sometimes even the way
business is run. For an application to be effectively implemented not only the technical
environment should be ready but the users should accept it and use it efficiently. For this to
happen the users may have to be trained on the new system. All this requires planning.
1.3.2 Methodologies

In this section, we emphasize a number of commonly used Software development methodologies.
We consider both thick and thin (also called ‘lightweight’) methodologies. The thick
methodologies we consider are RUP, SSADM and PRINCE2. XP, SCRUM and Crystal Clear are
measured as thin methodologies. When discussing each methodology, we will focus on the
management and business features of the methodology.

Rational Unified Process (RUP)

The Rational Unified Process (RUP) is a software design methodology formed by the Rational
Software Company. The Rational Software Company was obtained by IBM in 2003. RUP is a
thick methodology; the entire software design process is explained with high detail. RUP is
hence particularly applicable on larger software projects. The RUP methodology is common
enough to be used out of the box, but the modular nature of RUP-it is designed and documented
utilizing Unified Modeling Language (UML)–also makes it easy to adapt the methodology to
the particular needs of a single project or company. One of the main differences between RUP
and other methodologies like SSADM is that RUP doesn’t use a waterfall approach for software
development. The phases of requirements, analysis, design, implementation, integration and
testing are not done in strict sequence. In RUP, an iterative approach is used: a software product
is designed and built in a series of incremental iterations. Figure 1.1 shows one iteration of a
RUP project in a graphical way.

Application Area

Due to the modular nature of RUP, it can be employed for all sorts of software projects. It is even
possible to use RUP for non-software projects. Though, because of the complexity of the RUP
methodology, it is used mostly for larger software projects.

Advantages

 The iterative approach leads to higher effectiveness. Testing takes place in each iteration,
not just at the end of the project life cycle. This way, problems are noticed earlier, and are
therefore easier and cheaper to determine. When using a waterfall approach, it can happen

LOVELY PROFESSIONAL UNIVERSITY 11