Automatically creating a crashing-based schedule plan as countermeasures against process delay

  • Authors:
  • Daisuke Kinoshita;Hiroaki Hashiura;Rihito Yaegashi;Hiroki Uchikawa;Kazuhiro Uenosono;Seiichi Komiya

  • Affiliations:
  • Shibaura Institute of Technology, Graduate School of Engineering, Tokyo, Japan;Shibaura Institute of Technology, Graduate School of Engineering, Tokyo, Japan;Shibaura Institute of Technology, Center for Information Science, Tokyo, Japan;Shibaura Institute of Technology, Graduate School of Engineering, Tokyo, Japan;Shibaura Institute of Technology, Graduate School of Engineering, Tokyo, Japan;Shibaura Institute of Technology, Graduate School of Engineering, Tokyo, Japan

  • Venue:
  • DIWEB'08 Proceedings of the 8th WSEAS international conference on Distance learning and web engineering
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

Development of large-scale software is usually conducted through a project to unite a work force. In addition, no matter what kind of life cycle model is employed, a development plan is required for a software development project in order for the united work force to perform effectively. Therefore for the successful project, it is necessary to set management objectives to manage plan, and confirm if they are achieved. This method is considered to be effective, but actually making a software development plan and following-up the achievement of the management objectives at each step is not easy. Because since all the work for software development is done in side of human brain, other people can not measure how much each worker exanimate each work. Therefore it is necessary to secure the time for measuring the depth of a work's examination by project manager's talk with the worker in charge, through automating as many parts as possible by means of mechanizing. It is difficult to make a software development plan itself, because predicting the necessary work amount and risks that the project involves is difficult in software development. Therefore, the authors are developing an automatic schedule planning system for software development so that the project manager can manage the entire project and the work load of the manager is reduced. This paper proposes a method to create automatically such a successful schedule plan that a project, which was behind schedule, will be completed on schedule by means of 'crashing'. And the paper proves that the method is effective in software project management through an example of system.