[kplato] Functional Breakdown

[Jim Sabatke]

The breakdown on the website looks great!  Now I think we need to refine 
the list until we have all of the requirements listed.  I think we 
should visit each functional area and discuss functionality.  Here are 
some of my suggestions for 2.2.2 Schedule Planning:

1.     Create WBS (Work Breakdown Structure) belongs under 2.2.2 
Schedule Planning.
            WBS Codes should reflect the structure:

                    Task 1 - 1
                        Subtask 1 - 1.1
                        Subtask 2 - 1.2
                            Sub-Subtask 1 - 1.2.1
                       Etc.

2.    Assign Task Duration Type to tasks.  Example Task Types:
           Start On Date (Earliest Start)
           Finish By Date (Latest Finish)
           Work Between Dates (Earliest Start - Latest Finish)
           Milestone
           Percent of Project - Usefull for tasks like management hours 
which are a function of the duration of the entire project.

The Task Type can be taken from context.  Manually entered dates could 
be considered constraints.  Where dates are not manually entered, the 
program would be free to assign start/finish dates.


** Important Note ** As a general rule, manually entered data should 
take precedence over calculated data.  The program should not change 
manually entered data.  One of the most annoying things about M$ Project 
is that entered data are often changed.

3.    Assign an unchanging Task ID to each task.  The Task ID would be 
assigned in sequence starting with 1.  The Task ID for a task would not 
change if the task order is changed in any way.  This is especially 
useful for external programs that might be expecting task IDs related to 
certain tasks.

4.    Assign task dependencies - a list of Task IDs that must be 
completed before the current task begins.

5.    Allow task durations to be calculated from the following columns:

        "Optimistic Hours"    "Pessimistic Hours"  "Expected Hours"   
"Risk"    "Duration"

        The "Duration" would be calculated like:

        "Risk" = Low        Duration = (OH + 4EH +PH) / 6
        "Risk" = High      Duration = (OH + 4EH + 2PH) / 7
        "Risk" = None      OH = EH = PH = "Duration"  

        If Duration is entered, then OH, PH, EH all will be set to 
"Duration" and "Risk = None"

6.    Durations should only be enterable for WBS terminal nodes.
     
                                                       

-- 
Jim Sabatke
SuSE 7.1 Linux
Kernel - 2.4.0
http://www.execpc.com/~jsabatke

"People tell me that I'm fading fast, that I can't last the whole night through" Janis Ian