Data Structures and Algorithms


A Unit Based Crashing Pert Network for Optimization of Software Project Cost

Authors: Priti Singh, Florentin Smarandache, Dipti Chauhan, Amit Bhaghel

Crashing is a process of expediting project schedule by compressing the total project duration. It is helpful when managers want to avoid incoming bad weather season. However, the downside is that more resources are needed to speed-up a part of a project, even if resources may be withdrawn from one facet of the project and used to speed-up the section that is lagging behind. Moreover, that may also depend on what slack is available in a non-critical activity, thus resources can be reassigned to critical project activity. Hence, utmost care should be taken to make sure that appropriate activities are being crashed and that diverted resources are not causing needless risk and project scope integrity. In this paper we want to present a technique called "Unit Crashing" to reduce the total cost of project. Unit Crashing means to crash the project duration by one unit (day) instead of crashing it completely. This technique uses an iterative approach to perform unit crashing until all activities along the critical path are crashed by desired amount. The output of this method will reduce the cost of project, and is useful at places where cost is of major consideration. Crashing PERT networks can save a significant amount of money in crashing and overrun costs of a company. Even if there are no direct costs in the form of penalties for late completion of projects, there is likely to be intangible costs because of reputation damage.

Comments: 10 pages

Download: PDF

Submission history

[v1] 11 Aug 2010

Unique-IP document downloads: 12366 times is a pre-print repository rather than a journal. Articles hosted may not yet have been verified by peer-review and should be treated as preliminary. In particular, anything that appears to include financial or legal advice or proposed medical treatments should be treated with due caution. will not be responsible for any consequences of actions that result from any form of use of any documents on this website.

Add your own feedback and questions here:
You are equally welcome to be positive or negative about any paper but please be polite. If you are being critical you must mention at least one specific error, otherwise your comment will be deleted as unhelpful.

comments powered by Disqus