aboutsummaryrefslogtreecommitdiff
path: root/doc/tips/ikiwiki_as_a_requirements_management_tool
diff options
context:
space:
mode:
authorAlexandreDupas <AlexandreDupas@web>2009-09-03 04:56:35 -0400
committerJoey Hess <joey@kitenet.net>2009-09-03 04:56:35 -0400
commit70c9d175b56c3d7a878b8bd47eeaef5cec876c8b (patch)
treea689aa1e4625a506c3b539e2b29a47a63cf66078 /doc/tips/ikiwiki_as_a_requirements_management_tool
parentdd96853fe36102e512dea69d06514786cd9a96df (diff)
downloadikiwiki-70c9d175b56c3d7a878b8bd47eeaef5cec876c8b.tar
ikiwiki-70c9d175b56c3d7a878b8bd47eeaef5cec876c8b.tar.gz
Using tags or links to represent attributes
Diffstat (limited to 'doc/tips/ikiwiki_as_a_requirements_management_tool')
-rw-r--r--doc/tips/ikiwiki_as_a_requirements_management_tool/discussion.mdwn18
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.).