Forum OpenACS Development: Re: Preliminary vision statement open for discussion

Collapse
Posted by Malte Sussdorff on
Let's talk about dependencies:

Project Repository is needed by:
-- Project Scheduling
-- Project based todo list
-- Resource Allocation Management
-- Timekeeping
-- Expenses (at least in most cases it makes sense to link them to a project)

Scheduling is needed by:
-- Project Scheduling
-- Task / Todo List (for keeping track of due dates)

Resource Management is needed by:
-- Time Keeping
-- Holiday Booking
-- Expenses
-- Todo List

If you agree with this aproach, we could have a closer look what we need, which tasks need to be done first and then find the people to work on the tasks in a given order. My assumption is, once we have the project repository and the resource management ready in the basics, other packages could be developed in parallel.

Makes a lot of sense.

BTW - I think there're actually more dependencies:

Project scheduling requires:
  -- timekeeping ('already used' time can impact the schedule, especially if it is more than planned :(
  -- task/todolist (and phasing - lets not forget that! Very important for projects)
  -- resource allocation
  -- holiday booking

If you add it all up then the workorder would likely look like this:
1) project rep (indeed the most fundamental)
2) resource manager
3) scheduling
4) phased/categorized task/todolist (a normal tasklist simply has one phase)
5) timekeeping, holidaybooking, expenses
6) project scheduling
7) project reporting