Hello Claus,
as you are currently in charge of keeping the project alive and for managing the trackers and so on, I have a few requests, based actually on behalf of some wishes on the wish list, which actually hint into that direction, and, also taking into account here my own requirements and analysis's from the past for a similar solution. And, furthermore, I don't see any point in not including such functionality from the start - the qa component is fine but we need to consolidate the existing issues into a real requirements analysis - we would require a ra (requirements analysis) top level component, where we then further elaborate on the wishes issued against the qa component, and where we can add additional sub components (talking about a domain based analysis here) non functional components - data mining, evaluation, comparison - planning (project, tasks, milestones) - calendaring (personnel, machine etc. resource in general) - scheduling (project, tasks, milestones) - accounting (work time, machine time etc.) - pooling (of resources) - work packages - kinds of projects - software development projects - hardware development projects - ... - utility projects /aka brainstorming sessions etc. - tasks and sub tasks - projects and sub projects - dependency management (tasks, projects etc.) - and so on, any further ideas on your behalf here? - methologies /e.g. ITIL, V-MODELL etc. - security /e.g. role based security model >From the non functional components, we then can analyse and create the actual issues for the functional components functional components - client - client::editors /e.g. task editor, project properties editor and so on - client::viewers /e.g. task viewer (for roles with limited access) - client::browsers /e.g. project browser - client::navigators /e.g. multi project navigator etc. - client::visualizations (gantt and other reports etc) - client::communication::protocols /e.g. client to server communication protocol - client::apis - client::architecture - client::scripting /aka macros - client::extension /aka scripting engine extensions etc. and, on my behalf, I would rather see the whole of the solution, and, in accordance to some of the wishes in qa, divided into both a headless server component and a client - server - server::apis - server::architecture - server::communication::protocols - server::scripting - server::extension - server::reporting additionally, I would like OOPM to support workflows, and, by that also, a processing engine in the backend of the server. - server::processingengine Additional components we require are - project - project::workflows /e.g. govern create project, edit task and so on - project::activities /e.g. create project, edit task and so on for capturing requirements for the multiple project methodologies that were proposed to be supported by the oopm. We should defininetly get into touch about this and presumably also establish some kind of work/review group for the proposals in both the wish list, the design/architecture proposals made herein, and, also, for figuring out the actual components we require for the requirements analysis in order to actually achieve a domain based analysis of some kind or the other. I mean, we are not just the sole two participants in this project, or are we? If so, we need to elevate the people who contributed to the qa component so far, based on their personal interest. I for myself would like to be elevated to chief architect ;) Best Regards, Carsten -- abstraXion.de. Carsten Klein Staatl. gepr. Informatiker Wipperfürther Str. 278 51515 Kürten Deutschland Mobil +49 157 766 625 65 Email carsten.kl...@abstraxion.de. Steuernummer 5230/5182/1399 Bankverbindung Sparkasse Leverkusen BLZ 37551440 Konto 213054448 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@oopm.openoffice.org For additional commands, e-mail: dev-h...@oopm.openoffice.org
