[pmwiki-users] PmWiki as requirements management tool?
unfies at gmail.com
Wed Aug 26 13:43:59 CDT 2015
I've been thinking about something like this about once a month. More
as a checklist system for projects / things.
Never get very far with the thoughts, though.
include's, page variables, etc should make it all possible.
I'd prolly suggest a couple different versions of the thing though.
A 'simple' one where each project gets it's own group and is fully self
contained. Creating a new project is then a matter of copying a
template group. The "model" and the "data" are all self contained.
This lets you customize "widgets" (ie: an 'accounting card') without
affecting other projects. This is prolly the easiest to implement.
Then later a more complex one that lets you specify 'common widgets'
that are prolly their own group (or all exist in a singular separate
group) that you can include in your project. IE: each type of widget has
only one 'model' that all projects reference, but you store the 'data'
independently. This lets you update a common "widget" (ie: an
'accounting card') which then auto updates all the projects (then
requiring more data to be entered).
Hell, I'm sure Fox can be used to make this entire system.
On 8/26/2015 1:58 AM, Oliver Betz wrote:
> Hi All,
> anybody using PmWiki as a requirements management tool?
> For example, using wiki pages like snow cards, even with semantics
> (page variables).
> Backlinks can show dependencies at least one level deep.
> Maybe one could even implement a recursive method to mark affected
> requirements for review after changing a linking requirement.
> It will be difficult to get "base lines". Copy the whole tree to
> another group?
More information about the pmwiki-users