Changes between Version 71 and Version 72 of ProjectManagementIdeas


Ignore:
Timestamp:
May 21, 2009, 5:14:35 PM (15 years ago)
Author:
Chris Nelson
Comment:

Add to IProjectCalendar and IProjectSchedule

Legend:

Unmodified
Added
Removed
Modified
  • ProjectManagementIdeas

    v71 v72  
    403403A slightly more sophisticated implementation would track individual resource availability so that the schedule can account for vacations and such.
    404404
     405An IProjectCalendar should provide the following methods:
     406
     407  startFromFinish(task,finish):: return the date on which ''task'' must begin to complete by ''finish''.  If ''task's'' work is more than a day, this accounts for weekends, etc. so ''finish'' - ''start'' may be more than ''task.work''.
     408
     409  startFromFinish(task,finish,resource):: return the date on which ''task'' must begin for ''resource'' to complete it by ''finish''.  If ''task's'' work is more than a day, this accounts for weekends, etc. so ''finish'' - ''start'' may be more than ''task.work''.  May account for ''resource's'' vacation, etc. in addition to the general work calendar.
     410
     411  finishFromStart(task,start):: return the date on which ''task'' will complete if started on ''start''.  If ''task's'' work is more than a day, this accounts for weekends, etc. so ''finish'' - ''start'' may be more than ''task.work''.
     412
     413  finishFromStart(task,start,resource):: return the date on which ''task'' will complete if ''resource'' started it on ''start''.  If ''task's'' work is more than a day, this accounts for weekends, etc. so ''finish'' - ''start'' may be more than ''task.work''.  May account for ''resource's'' vacation, etc. in addition to the general work calendar.
     414
     415
    405416== IProjectResource ==
    406417
     
    409420
    410421== IProjectSchedule ==
     422
     423Computing a schedule involves determining the ''computedStart'' and ''computedFinish'' for a set of tasks taking into account the dependencies between tasks and the resources assigned to those tasks.  Where the tasks do not have assignedStart or assignedFinish, the computed schedule prioritizes tasks to keep resources at or below 100% utilization.  However, assigned dates may force overloaded resources.  These overloads can then be reported and either manually resolved or resolved with a resource leveling module apart from the scheduler.
    411424
    412425Random algorithm notes.