International Journal of Scientific & Engineering Research, Volume 5, Issue 1, January-2014 207

ISSN 2229-5518

Software Project Management Models

Dr. Abdul Rauf, Meshal Alshahrani

Department of Computer Science, College of Computer Sciences and Information

Al-Imam Mohammad Ibn Saud University

Abstract— Project management is a process tasks and activities are planned, organized, assigned resources and executed within a given budget and period. There are several software management models that are used in the process of managing a software project. Since there are many of the techniques and models, this articles selects and analyzes some of them. This is to help managers in making a decision which tool to use depending on their needs. Model in software project management means a standard practice that sometimes with guides and procedures on how to carry out activities. Models are sometimes diagrammed to illustrate procedures that project team members will use.

Index Terms— Rational Unified Process (RUP), Structured Systems Analysis and Design Methodology (SSADM), eXtreme Programming

(XP).optimally characterize the paper.

1 INTRODUCTION

——————————  ——————————

roject management is a process tasks and activities are planned, organized, assigned resources and executed within a given budget and period. There are several soft- ware management models that are used in the process of managing a software project. Since there are many of the tech- niques and models, this articles selects and analyzes some of
where a software product is produced during the succession incremental iterations. The iterations have the phases of soft- ware development as illustrated in Figure 1.
them. This is to help managers in making a decision which tool to use depending on their needs. The main reason for looking at the software models is the limited information on the usage of the models.
Purpose of This paper seeks to research on the most used software project management models. The models that will be reviewed are the currently being used. General information on each of the selected models will be discussed with emphasis on their key points, advantages and disadvantages.
There are several software development models that will be highlighted in this section. The models that will be dis- cussed to software project management include; Rational Uni- fied Process (RUP), Structured Systems Analysis and Design Methodology (SSADM) and eXtreme Programming (XP).

2 SOFTWARE PROJECT MANAGEMENT MODELS

2.1 Rational Unified Process (RUP)

This is a model that was designed by Rational Software Com- pany which was acquired by IBM in 2003. This is a model that involves large amount data and formal processes. This is the reason why software designed with this model has high level of details. RUP is easy to adapt because it is documented using Unified Modeling Language UML. This model has a bigger difference with other major software model because it does not use waterfall approach.
The phases of RUP are not strictly followed in the devel- opment cycle of software. The main phases in RUP are re- quirement, analysis, design, implementation, integration and testing. Interactive approach is instead implemented in RUP
There are several application areas of RUP because of its modular nature. This model is applicable in all types of soft- ware project regardless of the size, cost and time period. How- ever, because this model is very complex, it is recommended for large projects where there is enough time to follow all the documented procedures.
Rational unified process is efficient because of the itera- tive approach. It is easy to test the project product during each cycle instead of testing at the end of the whole project cycle. These ensure that the end product is successful and meets all the requirements with minimal errors. Efficiency also occurs in the RUP because it is not mandatory that one phase is com- pleted before starting the next one like in waterfall approach. It is possible to work on the next phase while the first phase is not yet complete. Given that the first phase and subsequent phases deliver a software product implementation can be done at the same time while the software moves into the next iteration cycle.

International Journal of Scientific & Engineering Research, Volume 5, Issue 1, January-2014 208

ISSN 2229-5518

It is not possible to define all the software requirements espe- cially of the project is large. RUP gives the project team an opportunity to introduce new requirements during develop- ment. This approach takes care of the creep requirements which in other approaches are difficult to add. This software development model is distributed to team members in a softcopy hence all the requirements that the team members may need are readily available. There is no need for members to go out in search of RUP information. Softcopy also ensures that team members have a synchronized copy or version of RUP.
RUP is commercially available hence one must purchase to have a copy. There is no shareware or open source software. RUP is only found in an electronic format hence having lim- ited use. This model is also complex because of detailed pro- cedures of software design. This makes it unsuitable for small projects. The software program also requires the team mem- bers to learn how to use it before they can apply RUP in a pro- ject.

2.2 Structured Systems Analysis and Design

Methodology (SSADM)

The first step is feasibility study which entails analysis of the business area and determine if the software project if fea- sible or doable. The second step is requirement analysis where the current business environment and business systems op- tions are evaluated. Requirement specification and logical sys- tem options are the third and fourth steps respectively while project design is the last step or phase in SSADM. SSADM is a model that uses three techniques; Logical data modeling, data flow modeling and entry or event modeling.
SSADM can be used in all projects of all sizes small, me- dium or large. It can be used to new projects starting from scratch or existing ones that need maintenance or upgrade.
Given that SSADM is standard, it can be freely acquired. This has enabled many company to offer training materials and Aided tools. The SSADM approach of splitting the project tasks into modules, stages, task and steps which are easy to manage. The management team is able to easily execute pro- ject tasks. If the project manager is in control of the project tasks, it becomes effective and delivers quality products. There are clear steps in requirement analysis hence the chances of adding new requirement are minimal.

IJSER

SSADM is a software project development model that is wide-
ly used. In UK for instance, it is one of the requirements for
computing projects of the government and it has been largely
adopted in Europe. SSADM was launched in 1981 with further
improvement up the stable version delivered on the market in
1990. SSADM unlike RUP it is standard open software imply-
ing that it is free for use. This has enabled it to stabilize be-
cause many companies have supported it.

SSADM take an approach of waterfall systems develop- ment where there are sequences of steps which are to be ac- complished one after another. The Figure 2 illustrates SSADM’s phases.
This model assumes that requirements will not change or
misunderstood at the initial stages of the project which is im-
possible in a dynamic project environment.

2.3 eXtreme Programming (XP)

This is a software engineering model that was developed by Kent Beck in 1996. Software project management can use this model in designing their software project. This model is aimed at reducing risks in the software development and manage- ment process.
In project management, delays in making decisions can result into huge losses. XP is aimed at reducing the cost as a result of delaying decisions. This model pays attention to the cost and revenues of design decisions. Delaying decisions on whether to implement options in software development is very risky. This is because implementing options later be- comes more expensive at a later date.
XP model is made of releases just like iterations of RUP where the first release gives a working version. Further releases just build up on the initial release where additional features are made and errors from the previous version are fixed. This model allows the stakeholders to add requirements since the requirements are not fixed. Before the commencement of the project, customer requirements are grouped into stories. The customers select the story with highest priority during the start of a next iteration.
This model is applicable for small and medium size pro- jects. It is also most suitable in situations where requirements are not very clear and there are chances of additional require- ments later in the development of the software. Some of the

International Journal of Scientific & Engineering Research, Volume 5, Issue 1, January-2014 209

ISSN 2229-5518

advantages of this model are that an earlier working version is produced after first release. This reduces the chances of final product failing to meet the user requirements because they are improved based on user feedback. And the biggest challenge in the application of this model is the customer since he should be participates in development team.

3 CONCLUSION

Software models are very important in software project man- agement. Project managers should select a project model that they are familiar with and is most suitable for the project. The size of the project and the duration for the development of a project should be considered in software development model. This paper has only looked at three software development models with much emphasis on the management part. There are many other software models that can be selected in a pro- ject. It is also possible to combine two or more models in a single project.

REFERENCES

[1] Kent Beck, extreme programming explained 2nd edition book

[2] [RUP-IMG] RUP – Software Component Architecture http://www.casoft.com.au/tag/rup

[3] [SSADM-WEB]Mike Goodland / Karel Riha | SSADM - An Intro- duction http://www.dcs.bbk.ac.uk/~steve/1/sld013.htm

[4] ITC Infotech, Structured systems analysis and design methodology.

[5] Rational Unified Process Software White Paper (2010).

[6] Sambasivam, G. (2004). Extreme Programming (XP). Agile Alliance, [7] John Smith, A Comparison of the IBM Rational Unified Process and

eXtreme Programming 2003

[8] The Government of the Hong Kong Special Administrative Region , an Introduction to Structured systems analysis and design method- ology 2012