diff options
| author | Joey Hess <joey@gnu.kitenet.net> | 2009-09-04 17:15:11 -0400 |
|---|---|---|
| committer | Joey Hess <joey@gnu.kitenet.net> | 2009-09-04 17:15:11 -0400 |
| commit | fc2bd0afe17a235a0ddfad0a5656c3683d8d180a (patch) | |
| tree | fe870015a89c3720d54921aa942e24b89c6eaa25 /doc/tips/ikiwiki_as_a_requirements_management_tool | |
| parent | de7c3aa16ba46adbc3d26e4a5a06e1dcc321fa6c (diff) | |
| parent | 127ed4d6c7a7d2cc518102757b7b4be49d20fce8 (diff) | |
Merge branch 'master' into cvs
Diffstat (limited to 'doc/tips/ikiwiki_as_a_requirements_management_tool')
| -rw-r--r-- | doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn b/doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn new file mode 100644 index 000000000..94f0f8b4b --- /dev/null +++ b/doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn @@ -0,0 +1,18 @@ +How about using tags/links to associate attributes with requirements? +This could be as simple as adding a link, fo e.g. : + + * If it is traceable or not + + \[[attributes/traceable]] + + \[[attributes/untraceable]] + * Its criticality level + + \[[attributes/level/critical]] + + \[[attributes/level/important]] + + etc. + * Its priority + + \[[attributes/priority/low]] + + \[[attributes/priority/high]] + * If it is functional or not + + \[[attributes/functional]] + + \[[attributes/non-functional]] + +You just have to create pages for each attribute you want and then pagespec could be used to filter requirements by attributes. I think something similar is used to trac bug with ikiwiki (linking to a \[[done]] page, etc.). |