[kplato] Summary of Data Discussion

[Thomas Zander]

On Tue, Jun 19, 2001 at 01:27:48PM -0700, Chris Clarke wrote:
> On Tuesday 19 June 2001 11:46, Thomas Zander wrote:

> > > 4.1.3. Task Type
> > >
> > > Task Type ::=
> > >   ConstraintType ::= [Start On Date | Finish By Date |  Work Between
> > > Dates | Milestone | Percent of Project] +
> > >   Constraint ::= [Entered Date | Calculate]
> > >
> > > (Jim: this was what I got out of your email.  Were all 5 items supposed
> > > to be a task type?  I'm not sure how the last two fit in)
> >
> > Well, it seems logical to have them here.
> > But from a data-modeling POV those are not tasks, those are points in time
> > (where a task would always be a length of time). So they can not take
> > resources, they have no relationships or subtasks.
> > Therefor, again from a data-modeling POV, the "Milestone" and "Percent of
> > Project" types should be something like 'CheckMarks'.
> 
> Both of these things I see as objects in the PERT chart, with relationships 
> to other tasks.  For instance I might define Milestone1 as a block on the 
> chart that depends on the completion of tasks A, C, and E (i.e. when A, C, 
> and E complete we declare Milestone 1 achieved).  There may also be tasks 
> that contractually I cannot begin until Milestone 1 is achieved.
> 
> Given that from the programming point of view I now see Milestone as a 
> seperate object that derives from the same base class as a task, because they 
> do share a lot.  Something like:
> 
> Item ::=
>   ID +
>   Name +
>   {Relationship}
> 
> Task ::=
>   (inherits) Item +
>   Task Type +
>   Duration +
>   Status +
>   {Task} +
>   {Resource}
> 
> Milestone ::=
>   (inherits) Item +
>   Milestone specific data (e.g. payment!)

Hmm, task type should be here as well..
To differentiate between Milestones and PercentOfProject, right?

-- 
Thomas Zander                                            zander@earthling.net
The only thing worse than failure is the fear of trying something new