[kplato] Functional Breakdown (comments)

Chris Clarke kplato@kde.org
Mon, 18 Jun 2001 16:42:55 -0700


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.

Project C can now be added as a subproject to both A and B, indicating the 
dependency in their schedules.

Am I close?

Chris C.
-- 
Chris Clarke
security@cfourconsulting.com
http://cfourconsulting.com