Difference between revisions of "User:Carsten.klein"
From Apache OpenOffice Wiki
| Line 1: | Line 1: | ||
| + | == Current Work == | ||
Currently I am working on getting the OOPM project up to speed by | Currently I am working on getting the OOPM project up to speed by | ||
| Line 8: | Line 9: | ||
: based on processes/workflows, utilizing a processing engine in the backend, like for example the JBPM | : based on processes/workflows, utilizing a processing engine in the backend, like for example the JBPM | ||
* defining a basis for getting the real requirements analysis, based on a domain based analysis, up and running | * defining a basis for getting the real requirements analysis, based on a domain based analysis, up and running | ||
| + | |||
| + | == TODO == | ||
| + | |||
| + | * add missing templates for | ||
| + | ** release categories | ||
| + | ** arbitrary documents | ||
| + | *** e.g. requirements analysis document, architecture and design documents, specifications, end user documentation etc. | ||
| + | *** header: meta | ||
| + | *** sections: chapter, paragraph | ||
| + | * add missing documentation/howtos on how to establish a working per release documentation basis | ||
| + | * add missing documentation/howtos on how to establish a working document management system using the wiki | ||
| + | ** incl. versioned documentation regardless of wiki defined versioning (i.e. page revisions) | ||
| + | * continue with the initial requirements analysis based on the available wish list | ||
| + | * continue with the initial architecture proposal | ||
| + | * continue defining the initial iteration for starting the whole shebang of actual software development | ||
Revision as of 20:48, 8 April 2009
Current Work
Currently I am working on getting the OOPM project up to speed by
- developing an infrastructure incl. templating in the wiki for future documentation purposes
- making up an initial architecture proposal for the OOPM application, or rather "the solution", based on former research done for a similar project
- of mine, called the hpm, a hierarchical, multi project management solution, featuring inter-project dependencies and so on, which is inherently
- based on processes/workflows, utilizing a processing engine in the backend, like for example the JBPM
- defining a basis for getting the real requirements analysis, based on a domain based analysis, up and running
TODO
- add missing templates for
- release categories
- arbitrary documents
- e.g. requirements analysis document, architecture and design documents, specifications, end user documentation etc.
- header: meta
- sections: chapter, paragraph
- add missing documentation/howtos on how to establish a working per release documentation basis
- add missing documentation/howtos on how to establish a working document management system using the wiki
- incl. versioned documentation regardless of wiki defined versioning (i.e. page revisions)
- continue with the initial requirements analysis based on the available wish list
- continue with the initial architecture proposal
- continue defining the initial iteration for starting the whole shebang of actual software development
