[kplato] Functional Breakdown (comments)

[Chris Herrnberger]

On Monday 18 June 2001 19:42, Chris Clarke wrote:
> On Monday 18 June 2001 16:18, Chris Herrnberger wrote:
> > Thanks for the clarification but from a user perspective the later
> > definition does not make hay at this end. Can you expand on this a
> > little.
>
> Here's my take on what's going on with the difference between subtasks and
> subprojects (if I understand the discussion correctly).
>
> Let's say we have two projects being developed:  project A and project B.
>
> Both projects rely on the completion of a certain set of tasks in their
> schedule.
>
> Since a task cannot belong to two projects, we define these tasks as a new
> project called project C. 

While this may make sense from a programming perspective, the logic breaks 
down at this point from a user perspecitve. Why cannot a task belong to two 
projects as long as there is no relationship between the task the two 
projects remain as two projects. IF they are related then they are part of 
the same project effort. 

Example 1

Project 1
Build car (red) 
task one----install left front tire

Project 2
Build car (blue)
task one--install left front tire.

Example Two

Project
 --order tires
 --order paint
 -- build car a (red)
	|--install front left tire
 -- build car b (blue)
 	|--install front left tire.
--etc/.
>
> Project C can now be added as a subproject to both A and B, indicating the
> dependency in their schedules.

Im thinking you are talking programming logic here and not user level logic. 


chris h.