|
From: Jamey S. <ja...@sh...> - 2002-08-19 01:47:33
|
Thanks for checking other project management software, Deren. That's really useful information. I'm not sure why you only mailed me, but I think I've covered all your points here. I'm not sure I understood what it would mean to have resource and constraint information on groups. Please tell me if this sounds right. Constraining a group is like adding that constraint to all tasks in the group. If a group must start after June 1st, and a task must start after May 1st, then the task must really start after June 1st. If another task in that group must start before April 1st, the constraints conflict and the project can't be scheduled. When a group uses a resource, effectively all tasks in the group use that resource with the same amount. If a group uses 1 hammer, and a task uses 2 hammers, that task really uses 3 hammers. Do those sound about right? You said duration can't be set on groups, because it's implicit from the tasks in the group; how about precedence? As far as implementation goes, I expect there to be a translation step between the DOM structure we use internally and the view that a scheduler sees. So if we want to do this, we can store group constraints and resource usage in obvious ways, and push that data down to tasks only when a scheduler asks for it. -- Jamey Sharp <ja...@sh...> - http://jamey.is.dreaming.org/ |